[bisq-network/bisq] Withdrawal not propagating, funds not accessable per cmd-e (#2778)

Oscar Guindzberg notifications at github.com
Fri Apr 26 13:45:03 UTC 2019


Help to the user:
- Do a backup of your bisq data dir.
- Make sure to have a reliable connection to the btc network (I did not get what you mean by "I have 2 local nodes connected and changed this now into the default nodes"). Using the bisq provided btc nodes would be a good way to remove noise.
- Start bisq and get your seed words.
- Do a restore from seed with those words (If that does not work, empty your bisq data dir and do a restore from seed again)
- I guess you will see your expected balance at this point, you can withdraw your funds now.


Help to bisq:
- There seems to be a bug on how some edge situations are handled. Could you help us find the cause?
- What bisq version are you using?
- Could you describe in more detail what happened? e.g. I posted an offer to sell xxx, it was taken, then the arbitrator did yyyy, and I tried zzz but it did not work, so I did such and such....
- Once you move out your funds, could you send me / upload a zipped copy of your bisq data dir backup (The backup I suggested you to do as a first step)? Full disclosure: By doing this you are sharing your private keys (you should start with a fresh data dir and seed words after this) and transaction history (you are exposing private information). 




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/2778#issuecomment-487062140
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190426/81e6079e/attachment.html>


More information about the bisq-github mailing list