Skip to content
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

Closed
CoenKuij opened this issue Mar 10, 2018 · 11 comments
Closed

Failed bisq tx, deposited funds locked up in blockchain tx #82

CoenKuij opened this issue Mar 10, 2018 · 11 comments
Assignees

Comments

@CoenKuij
Copy link

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

@cbeams
Copy link
Contributor

cbeams commented Mar 13, 2018

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 Details / (i) in the failed trade. Please copy and paste the tx id values here, and please also take a paste a screenshot of them here. Thanks.

@CoenKuij
Copy link
Author

No no ticket was opened unfortunately.
Taker Id (Mine) bacf76ddb7a11747e84ecb492e118ace04231c60c5077cbebb4ea6b5b4ccd77d
Maker Id (other party) 100ea2fc5343e8152a0c945091a0bfdd6ee31c97d1b8348702374829f2a25166

image

@CoenKuij
Copy link
Author

@cbeams any news on this one?

@cbeams
Copy link
Contributor

cbeams commented Mar 22, 2018

@CoenKuij, this was @keo-bisq's arbitration case, so I'll let him weigh in about what he is doing / has done with it.

In the meantime, though, I'll get this queued up for fee reimbursement in our next batch transaction (#76).

@keo-bisq
Copy link

I don't have tradeID 9985452 in my arbitration list.

@CoenKuij
Copy link
Author

@cbeams @keo-bisq How will this now be handled?

@cbeams
Copy link
Contributor

cbeams commented May 22, 2018

@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 View contract in JSON format button.

You can send this to me securely via Keybase (I'm @cbeams), or via encrypted email at [email protected] (my PGP key is available via public keyservers). Keybase is best, so we can just continue the chat there and go through the manual payout process together.

@CoenKuij
Copy link
Author

CoenKuij commented May 22, 2018

Settled to full satisfaction. Thank you for your trouble!
The transaction shows up in the failed trades section. But it was reimbursed without me noticing it.
So in the end it was all a misunderstanding and no funds were lost.

@cbeams
Copy link
Contributor

cbeams commented May 22, 2018

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.

@CoenKuij
Copy link
Author

CoenKuij commented May 22, 2018

@cbeams Ah, I see.
Please refund the fees. 👍

@CoenKuij CoenKuij reopened this May 22, 2018
KanoczTomas added a commit that referenced this issue Oct 20, 2018
@KanoczTomas
Copy link
Contributor

Closing as reimbursed via the batch transaction documented at #101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants