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 EZLQB #1666

Open
Scoop193 opened this issue Aug 21, 2024 · 0 comments
Open

Fee reimbursement for trade EZLQB #1666

Scoop193 opened this issue Aug 21, 2024 · 0 comments
Assignees

Comments

@Scoop193
Copy link

Scoop193 commented Aug 21, 2024

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

SCREENSHOT HERE
20240821_182801
20240821_182811

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: .......... .00001750 btc
Taker: ........... .00006990btc
Deposit: .......... .003675 btc
BTC mining fees lost: .......... eg 0.00005 BTC
Trade fees lost, please state if BSQ or BTC: .......... eg 5.43 BSQ or 0.000088 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
e0b29f05887121123ed647b6ba507643f9f9057cf403a5b1ae5b1b9d9847f8d9

Bisq version: v1.9.17
BTC address for reimbursement:bc1qwa2ccnqqddhmqqeddl7td035eanamjse3zj7h9

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

Other notes:
Laptop froze up while doing the Initial trade

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

@leo816 leo816 self-assigned this Sep 9, 2024
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