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!
BTC mining fees lost: .......... eg 0.00005 BTC
Trade fees lost, please state if BSQ or BTC: .......... eg 5.43 BSQ or 0.000088 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:
bc1ququ3s0y264lzju9n50wms0hz7pnnxjyya3jhhn
Provide the Bisq client version to help developers identify the causing issue.
Bisq version: 1.9.10-1
The text was updated successfully, but these errors were encountered:
Jantje35
changed the title
Fee reimbursement for trade NZoJz-182b6951-1607-4dd1-baa7-103bfff19104-1910
Fee reimbursement for trade NZoJz
Oct 25, 2023
Maker: ..........
624d588a553952574c817051730cd0dcd50746ba1eef64664a1accd5c0a747c1
Taker: ...........
13bc36f50b9878b340527f007a4ceaca0db98723e5dd9b71c2e20371f7bd81ff
Deposit: ..........
"buyerSecurityDeposit": 364500,
"sellerSecurityDeposit": 364500,
BTC mining fees lost: .......... eg 0.00005 BTC
Trade fees lost, please state if BSQ or BTC: .......... eg 5.43 BSQ or 0.000088 BTC
BTC address for reimbursement:
bc1ququ3s0y264lzju9n50wms0hz7pnnxjyya3jhhn
The text was updated successfully, but these errors were encountered: