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 062481 #353

Closed
grahamf21 opened this issue Mar 11, 2020 · 4 comments
Closed

Fee reimbursement for trade 062481 #353

grahamf21 opened this issue Mar 11, 2020 · 4 comments
Assignees

Comments

@grahamf21
Copy link

The XXXXX part in the issue title are the first characters of the Trade ID before the "-" (dash).

Bisq trade 062481

The screenshot from the Bisq client must have the Trade ID, Deposit, Maker and Taker TXIDs visible. Of course some trades do not have all 3 types, that is ok. Make sure all private information is covered (like bank accounts, name, etc). Do not upload images where sensitive private data is visible!

Maker: 2c1d963bc4e3084e77911fa9bff665d68742b97f1392641a11c347b365a80dd6
Taker: b4f4871fa10e14664634b879b5a13474e491536e397cd40d51ce112d14f22558
Deposit: 0.017235

A reimbursement request has to contain textual representation of Maker, Taker and Deposit TXIDs (copy them from the client to the issue). All TXIDs that are visible in the screenshot must be copied to the issue in text form! Please use exact form for Maker/Taker/Deposit - no abbreviations like M:, T: or adding extra characters like "Maker TX:", etc. Leave those fields as they are and replace the "........" with the appropreate txid

Bisq version: v1.2.7

Provide the Bisq client version to help developers identify the causing issue.

Other notes:
Maker fee transaction not found, 2c1d963bc4e3084e77911fa9bff665d68742b97f1392641a11c347b365a80dd6
Taker fee transaction found, b4f4871fa10e14664634b879b5a13474e491536e397cd40d51ce112d14f22558

No blockchain confirmations received, transaction seems to have failed.

Please refund fees.

Issue #197 can be used as a good example of a correct reimbursement request.

@leo816
Copy link
Contributor

leo816 commented Apr 2, 2020

Maker: 2c1d963bc4e3084e77911fa9bff665d68742b97f1392641a11c347b365a80dd6
Taker: b4f4871fa10e14664634b879b5a13474e491536e397cd40d51ce112d14f22558

leo816 added a commit that referenced this issue Apr 2, 2020
@leo816
Copy link
Contributor

leo816 commented Apr 2, 2020

Will be reimbursed with #366

@leo816
Copy link
Contributor

leo816 commented May 7, 2020

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

@leo816 leo816 closed this as completed May 7, 2020
@grahamf21
Copy link
Author

grahamf21 commented May 10, 2020 via email

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