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 EGJYKE #1737

Open
pazza83 opened this issue Jan 20, 2025 · 1 comment
Open

Fee reimbursement for trade EGJYKE #1737

pazza83 opened this issue Jan 20, 2025 · 1 comment

Comments

@pazza83
Copy link

pazza83 commented Jan 20, 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!

@pazza83 completing on behalf of the BTC seller (offer maker) due to their privacy concerns. Address used for reimbursement will be the same as the funding address for the trade: bc1qrl6xxx965d39qjkccmccq27yjmyy3p87cwxhqf

Maker: 2d210b33221b8893df1c67b72ea1ebcbb2115e9ef6818838bb1c6148084e3e3f
Taker: b1a5da086d8a61bf39471c50cb8664aab44454d3fbe74d50dd9507f088806e3e
Deposit: 208792247ec50d964b170a8237ee04ecf96b6e95ef402dc19220be2eb10baebf
Miner fee: 0.00002450 BTC
Trade fee: 10.87 BSQ

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

BTC address for reimbursement: bc1qrl6xxx965d39qjkccmccq27yjmyy3p87cwxhqf

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.

@pazza83
Copy link
Author

pazza83 commented Jan 20, 2025

The BTC Seller was advised the refund would be made in the next reimbursement batch.

The reimbursement will be made in bitcoin:

Total: 0.00031375 BTC

@luis3672 please can you add this reimbursement to your next payout. Thanks

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