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 xjmlxd #1775

Open
luis3672 opened this issue Feb 11, 2025 · 1 comment
Open

Fee reimbursement for trade xjmlxd #1775

luis3672 opened this issue Feb 11, 2025 · 1 comment

Comments

@luis3672
Copy link

luis3672 commented Feb 11, 2025

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: bc3eadd826ff76a42decffed797b082c907141b230012b72d6b1e4efc29d2a03
Taker: ...........
Deposit: ..........
BTC mining fees lost: .......... 0.00002450 BTC
Trade fees lost, please state if BSQ or BTC: .......... 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:
BTC address for reimbursement: bc1qa4pnrpm6hh8n8ztrmg2hvc9pg95mz9kwcn0fcp

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: 0e295330d6e3ae755811cd4ca6a0b3dd038705d98fc25bdb2b0e9e123b5fbed5
Taker: ...........
Deposit: ..........
BTC mining fees lost: .......... 0.0000649 BTC
Trade fees lost, please state if BSQ or BTC: .......... BTC

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.

@luis3672
Copy link
Author

This is a fee reimbursement issue on behalf of a user who wants to keep their privacy

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