You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
Reimbursement for trade [TRADE ID]
I am BTC [buyer/seller] as [maker/taker] for [ASSET].
Trade amount and asset: [AMOUNT] BTC for [X ASSET]
Deposit amount: [AMOUNT] BTC
Reimbursement amount: [AMOUNT] BTC / [30 day BSQ average] BSQ = [TOTAL AMOUNT] BSQ
Reason for reimbursement: [REASON]
BTC address ownership proof:
Repeat the above for each trade you need to be reimbursed
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:
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.
trade ID #85726528
Reimbursement for trade [TRADE ID]
I am BTC [buyer/seller] as [maker/taker] for [ASSET].
Trade amount and asset: [AMOUNT] BTC for [X ASSET]
Deposit amount: [AMOUNT] BTC
Maker: ..........
Taker: ...........
Deposit: ..........
Delayed payout: ..........
BuyerMultiSigPubKeyHex: ..........
SellerMultiSigPubKeyHex: ..........
Reimbursement amount: [AMOUNT] BTC / [30 day BSQ average] BSQ = [TOTAL AMOUNT] BSQ
Reason for reimbursement: [REASON]
BTC address ownership proof:
Bisq version:
Other notes:
The text was updated successfully, but these errors were encountered: