[bisq-network/bisq] Lost ~0.02159616 BTC during 0.01 BTC trade (#5661)
notifications at github.com
Fri Aug 13 03:01:40 CEST 2021
Thanks for the detailed issue report, much better than the average.
Notable points from your message:
- Balances not recognized usually means the wallet is in a bad state. Unfortunately that happens quite a bit, along with the frequent advice to "SPV resync" whenever wallet issues pop up. The underlying wallet library while nice in some respects unfortunately is quite fragile.
- Your missing 0.02159616 is not showing up in the wallet UI, but ultimately you still own the private key and can recover the balance by restoring from seed phrase.
- Bisq never knowingly re-uses an address, the fact that it happened could be related to the wallet being in a bad state or a bug - this is something I can look into by trying to reproduce it in a test environment.
- 1.7.0 was mostly a protocol change to close a potential privacy loophole, so I don't think it is the inflection point which caused your problems. There have not been any core wallet changes since the segwit upgrade last year.
In the mean time I would strongly recommend you [export your accounts](https://bisq.wiki/Backing_up_application_data#Back_up_payment_accounts), make a [backup](https://bisq.wiki/Backing_up_application_data), and start from a [fresh data directory](https://bisq.wiki/Switching_to_a_new_data_directory). Restore your wallet balances from the [recovery seed word](https://bisq.wiki/Restoring_your_wallet_from_seed). Re-import your accounts. That way you are starting from a solid foundation with all balances accounted for and the wallet corruption would not be there to cause further problems.
Any other issues or concerns feel free to reach out to me on keybase (same username).
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bisq-github