Fee reimbursement for trade dpxevmh9

[Scoop193]

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

SCREENSHOT HERE

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: 0.00015225 BTC
Taker: 0.00057318 BTC
Deposit: 0.0010 BTC
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
615849bf746cf7e558e541322e7fc32f6891dcb150a40696120210842735d72d
9770c62e60cdefb8b22b6e4a215a7d65146b69b534f58eaeb15eb6a4643cd548
72f73cacb75157ebf28fd1e4e803cb0dcc05bf20ec0be43cdea8a851ec60fb75
981a1d8c9316e7663b34b2d94377eabc3e078949dcfa64eb43a91e114b20f45b

Bisq version: v1.9.17
BTC address for reimbursement:
bc1qwa2ccnqqddhmqqeddl7td035eanamjse3zj7h9

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.