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 XXXXX part in the issue title are the first characters of the Trade ID before the "-" (dash).
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: 2a89cf4796022b9b2653569e4eac46bd1b5c5ae455d70da3f1c292b3cd2a894d
Taker: dd4d4b78d4455ffd0aeb16af28ac24b284930e58b4e08afe38e1e29c6a33dbca
Deposit: N/A
BTC mining fees lost: N/A
Trade fees lost, please state if BSQ or BTC: 0.00002450 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: 1.9.17
BTC address for reimbursement: bc1qc73r50xl6w60tgts00chup708nrhy2uy223njz
Provide the Bisq client version to help developers identify the causing issue.
Other notes: Lost maker fee in failed transaction
Issue #197 can be used as a good example of a correct reimbursement request.
The text was updated successfully, but these errors were encountered:
Maker: 2a89cf4796022b9b2653569e4eac46bd1b5c5ae455d70da3f1c292b3cd2a894d
Taker: dd4d4b78d4455ffd0aeb16af28ac24b284930e58b4e08afe38e1e29c6a33dbca
Deposit: N/A
BTC mining fees lost: N/A
Trade fees lost, please state if BSQ or BTC: 0.00002450 BTC
Bisq version: 1.9.17
BTC address for reimbursement: bc1qc73r50xl6w60tgts00chup708nrhy2uy223njz
Other notes: Lost maker fee in failed transaction
The text was updated successfully, but these errors were encountered: