-
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 gVBDzEd #67
Comments
Thanks, @cybairfly. Can you send me the ID (hash) of the taker fee transaction? You should be able to find this in |
It can be that the maker is using an older Bisq version and thus have caused the timeout or that it is a case where the connection just got lost in the critical moment when the trade message should got transferred. Lets observe if we get more such cases. |
TX ID: 30b79b0584ad8f86f29113d16bb7ff1b576eafc28831ff3f51d065771462fdd6 Funds were returned safely to my Bisq wallet. Thanks, @cbeams @ManfredKarrer |
Staged for reimbursement in a975981. |
Closing as reimbursed via the batch transaction documented at #70 (comment). |
@cybairfly commented on Fri Feb 02 2018
An error occurred when taking the offer.
A timeout occurred.
The taker fee is already paid. In the worst case you have lost that fee.
Please try to restart your application and check your network connection to see if you can resolve the issue.Please try to restart your application and check your network connection to see if you can resolve the issue.
bisq.log
The text was updated successfully, but these errors were encountered: