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 Reembolso de Negócio #1674

Open
fernandotecnologia opened this issue Aug 31, 2024 · 0 comments
Open

Fee reimbursement for trade Reembolso de Negócio #1674

fernandotecnologia opened this issue Aug 31, 2024 · 0 comments

Comments

@fernandotecnologia
Copy link

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

SCREENSHOT HERE

detalhes negociação-editado

Maker: ..........76dd2d2c4ed24c8600c2ec39024b04dde14e3f886f930efc2f4e0ccd3a1946e2
Taker: ...........023d646bd85035f4b48350b6fb742f8873947fa2b1388eabbd8f87336355a417
Deposit: ..........12dfe271289c554dfb4b5cc881d6957169ab249a11f3d9bef3f4dc35fec0f95e
BTC mining fees lost: .......... 0.00003090 BTC / Aceitador: 0.00007080 BTC
Trade fees lost, please state if BSQ or BTC: .......... 0.0012 BTC / Vendedor: 0.0012 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: V1.9.17
BTC address for reimbursement: bc1qv0jd0ppllpvns6yl2dekepsk9qed362d4g02mh

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