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 d5hxylx-e72f3dd6-ac4c-4c13-8a90-000a3c0c827c-162 #912

Closed
walfait opened this issue Apr 18, 2021 · 2 comments
Closed

Comments

@walfait
Copy link

walfait commented Apr 18, 2021

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

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: ..f3586e5a2f6863cf2b58b2c487d6b551ed7b57b75c76eca51b66eacd119b67ee........
Taker: ......N/A.....
Deposit: ......N/A....

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 6.1
BTC address for reimbursement: bc1q9pd4d8ux9ffnh6te7q9rqwe72jq7vegcufxfh2

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

Other notes:

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

@walfait
Copy link
Author

walfait commented Apr 20, 2021

Can someone please look at this? thank you

@leo816
Copy link
Contributor

leo816 commented Apr 28, 2021

taker fee not published, funds never left your wallet. Reimbursement is not justified

@leo816 leo816 closed this as completed Apr 28, 2021
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