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 5595799 #1685

Open
pprvggc6um opened this issue Oct 4, 2024 · 0 comments
Open

Fee reimbursement for trade 5595799 #1685

pprvggc6um opened this issue Oct 4, 2024 · 0 comments

Comments

@pprvggc6um
Copy link

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

Screenshot_2024-10-04_07-26-55

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: 72d8bb9473caef141c9470052d93e849be0d3061d1279a65aafcb43d21ac2881
Taker: 6622e116b6eb40edfe7e25d969c1cdc99b53dbd4089fcafa1b271b5d73b924c7
Deposit: N/A
BTC mining fees lost: N/A

Trade fees lost, please state if BSQ or BTC: maker fee 0.00002450 BTC

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: 1.9.17
BTC address for reimbursement: bc1qwka4s53566y96f8wqhsnhl4nucfhycvkwdjxkr

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.

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

1 participant