-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fee reimbursement for trade myfmqqy #150
Comments
Reporting in as suggested by bisq. Everything seemed to go fine until my offer didn't show up in main market view. Difference to above screenshot is that taker fee doesn't show any kind of confirmation information (but it did have > 6 confirmations according to blockhair). Also there was some exception when I started bisq but it didn't give me another opportunity to copy it after it tried to launch a browser I've never used which also failed... Using bisq-0.8.0 with github.com/bitcoin/bitcoin node both compiled and running locally. Connectivity seemed fine, 4 tor connections I think. And btc node had 8 connections as usual. |
Deleted SPV stuff and restarted before and after sync, still getting exception(s) when starting bisq:
|
@ManfredKarrer, see the |
I think if the user deletes the PendingTrades database file (if he has no other open trades) the exception will not get triggered anymore. Best if the user starts over with new data directory and carry over account age witness. In the forum are 2 instruction postings. |
If I start over with new data dir, will reimbursement be sent to lost address? If yes then please use this one: 16f3ufhDMRK6CPmZcYjnYsZDn2iizuUww7 |
@iljah I added the addresses visible on the block explorer to the csv file. I can change it, will change the maker reimbursememt address to 16f3ufhDMRK6CPmZcYjnYsZDn2iizuUww7 as you requested. |
Closing as reimbursed via the batch transaction documented at #147 (comment). |
Maker: 17fa7276c28e58030ae7bde257d43dece005491c2e4d320ce9b719c7619cef26
Taker: a295b89ef042750e54c1c55295cdec018ca7f9461f03a5cd360f3aea73d8ef84
Deposit: b6704c3a89274795a8fea70e2849a05cdeb66b02e8f3841698938b60ad69b562
Deposit transaction was not broadcast (deposit tx shown above is valid but for a different, earlier trade). Lost maker and taker fees will be reimbursed in #147.
The text was updated successfully, but these errors were encountered: