-
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
Failed bisq tx, deposited funds locked up in blockchain tx #82
Comments
Have you opened an arbitration ticket about this, @CoenKuij? If you're unable to do so (because the trade failed before it was possible to open an arbitration ticket), then you'll need to provide us with transaction IDs for Maker / Taker / Deposit transactions. You can find this information by clicking on |
@cbeams any news on this one? |
I don't have tradeID 9985452 in my arbitration list. |
@CoenKuij, I see that the transactions you pasted above have indeed ended up in a deposit transaction that was never paid out, meaning that this isn't just about a reimbursement of lost fees, but that it really is about trading funds and security deposits being locked up. It looks like we'll need to do a manual payout on this, but it'll need to be done a little differently from the usual instructions, because neither @keo-bisq nor I have this trade in our arbitration queues. The main thing I need from you is the full text of the JSON contract for this trade. Can you find that and send it to me over a secure channel? You should be able to find it by going to the trade details on the failed trade and clicking the You can send this to me securely via Keybase (I'm |
Settled to full satisfaction. Thank you for your trouble! |
Thanks, @CoenKuij. Technically, it wasn't "reimbursed", because the funds never actually left your Bisq wallet. What did get spent (and lost), though, were your taker transaction's mining and trading fees. These are minimal, but still lost, and it's our policy to reimburse them for failed trades. If you'd like to reopen the issue and get reimbursed for these fees, please do, and we'll roll it into the next batch reimbursement transaction (#101). Best regards, and thanks for following up here. |
@cbeams Ah, I see. |
Closing as reimbursed via the batch transaction documented at #101 |
Yesterday I wanted to buy some bitcoin, but after the deposit hit the block chain the tx failed.
Can you please look into this?
Bisq txid = 9985452
The text was updated successfully, but these errors were encountered: