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 ernyrcmk #1742

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

Fee reimbursement for trade ernyrcmk #1742

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 filing this on behalf of another user that is having issues creating a ticket on github as there account keeps getting banned.

Address used for reimbursement is the funding address of the trade.

Maker: 32c087e579299ae5436e4f7c2fd1b40ece15a77e584de5e216aa515931c6c08a
Taker: bd0aaa6019be3726bfec20daf5fb97c2d9230618095c5d4b053f2c07c95ff71f
Deposit: N/A
BTC mining fees lost: 0.00001750 BTC
Trade fees lost, please state if BSQ or BTC: 0.0001500 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

BTC address for reimbursement: bc1qv9phuuw5mnsw4qttnsamfuknf0r65rzfehzfm8

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 buyer was advised the refund would be made in the next reimbursement batch.

The reimbursement will be made in bitcoin:

Total: 0.00016750 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