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 for trade YfhmuL #144

Closed
cbeams opened this issue Oct 12, 2018 · 4 comments
Closed

Fee reimbursement for trade YfhmuL #144

cbeams opened this issue Oct 12, 2018 · 4 comments

Comments

@cbeams
Copy link
Contributor

cbeams commented Oct 12, 2018

image

Maker: 926ef3f40baba8730816f3b35551ae0cc624a84a9c8ab96ac4f61149b1660e32
Taker: 43b63ee8d1eb33171e89e53c4e0e79e760da28a6092cb64fa20bf6c29caccd15
Deposit: 3cee76f563a28b6caec093960bc9fd09b3851a9f4b1289614ac813c4193c3d18

This trade failed because the deposit transaction was never broadcast. Lost maker and taker fees will be reimbursed with #101.

@a123b
Copy link

a123b commented Oct 12, 2018

I'm the maker and I was using bisq version v0.8.0.
Will the reimbursement include transaction/trading fees or just the security deposit?

@cbeams
Copy link
Contributor Author

cbeams commented Oct 13, 2018

Will the reimbursement include transaction fees or just the security deposit?

This reimbursement will cover lost trading and mining fees. You are still in control of your security deposit. Assuming you have resynced your SPV file as instructed in my closing arbitration comments, you should see that amount reflected in your Bisq wallet balance.

@a123b
Copy link

a123b commented Oct 16, 2018

That's what I originally thought, thanks for clarifying. I just got confused by the dispute summary. I already got the security deposit back before the ticket was closed, so I thought the "Payout amount for BTC buyer" in the summary referred to the reimbursement.

KanoczTomas added a commit that referenced this issue Oct 18, 2018
@cbeams
Copy link
Contributor Author

cbeams commented Oct 20, 2018

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

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

2 participants