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

Fee Reimbursement XWBFAQ #143

Closed
BisqAndGravy opened this issue Oct 12, 2018 · 8 comments
Closed

Fee Reimbursement XWBFAQ #143

BisqAndGravy opened this issue Oct 12, 2018 · 8 comments

Comments

@BisqAndGravy
Copy link

Trade ID: XWBFAQ-55edf217-9ee4-431b-b033-1bd0f222e84e-080
Maker Fee: 64289d3a22d96bfb877b5b0a3d77da8dae3f01e1c3400d3219961181def5ddc1
Taker Fee ID: 18b6bc3de24f26c742633ece5e1d295e50fe78c96c0ec56c577e8b421d898c9d

This trade failed because a connection was lost or the seller went off line.

Bisq version Aug 22, 2018
0.8.0

@KanoczTomas KanoczTomas moved this from Todo to In progress in Lost fee reimbursements Oct 18, 2018
@KanoczTomas
Copy link
Member

@BisqAndGravy please upload a screenshot from the failed trade here. Go to Portfolio -> Failed -> and click on the TradeID. A popup window with the details will appear. I just need the TradeID/Maker tx ID/Taker tx ID/Deposit tx ID/Error message/Trade state fields visible on the screenshot. Please crop the image so other parts are not visible, not good for privacy ...

@KanoczTomas KanoczTomas moved this from In progress to Waiting for info in Lost fee reimbursements Oct 18, 2018
@cbeams
Copy link
Member

cbeams commented Oct 19, 2018

@KanoczTomas, even if @BisqAndGravy doesn't respond with a screenshot, I'd still go ahead and process this reimbursement. It's clear from analyzing the transactions that (a) they're Bisq maker / taker transactions and (b) that they never came together into a deposit transaction. This is the signature of a trade that failed due to the deposit tx not being broadcast.

@BisqAndGravy
Copy link
Author

I'll upload a screen shot in a few minutes

@KanoczTomas
Copy link
Member

@cbeams ok, cool. Could you explain how can I find out they did not go into a deposit tx? I would like to know so I can verify it myself next time. To my understanding the maker creates the deposit tx (maker reimbursements have that info), on reimbursements for takers I did not see the deposit tx on any screenshot. A screenshot from @BisqAndGravy would have just confirmed that for me ...

@BisqAndGravy
Copy link
Author

bisq1

@cbeams
Copy link
Member

cbeams commented Oct 19, 2018

Could you explain how can I find out they did not go into a deposit tx?

Bring up maker and/or taker tx in a block explorer. There will always be 2 or 3 outputs for such transactions. One paying the trading fee to an arbitrator address, one transferring the trading amount (in the case of the seller) and security deposit, and possibly one transferring any change to a change address.

Follow the output that's transferring the trading amount / security deposit. Then follow any transaction from that address. Does it feed into a multisig deposit transaction (to a 3* BTC address and an OP_RETURN output)? If so, then everything was OK. If not, then the trade failed due to the deposit tx never being broadcast.

@BisqAndGravy
Copy link
Author

I didn't understand a word you said.

@cbeams cbeams moved this from Waiting for info to Todo in Lost fee reimbursements Oct 19, 2018
@KanoczTomas KanoczTomas moved this from Todo to In progress in Lost fee reimbursements Oct 20, 2018
KanoczTomas added a commit that referenced this issue Oct 20, 2018
@KanoczTomas KanoczTomas moved this from In progress to Staged in Lost fee reimbursements Oct 20, 2018
@cbeams
Copy link
Member

cbeams commented Oct 20, 2018

Closing as reimbursed via the batch transaction documented at #101 (comment).

@cbeams cbeams closed this as completed Oct 20, 2018
Lost fee reimbursements automation moved this from Staged to Closed Oct 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants