Skip to content

Fee reimbursement for trade 15563122 #2032

@gRB8gef4ld6UpqxX

Description

@gRB8gef4ld6UpqxX

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

Image

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: d7cdee2549b6be73f832d7121fbaa4089c4a1eae7be6303b0abd8507154859ad
Taker: cc937796f29e5ba429487167a79995a24bda8e1893c430086b03498f1fed8d3c
Deposit: Buyer: 0.00045030 BTC
BTC mining fees lost: I am not sure how much I lost
Trade fees lost, please state if BSQ or BTC: 0.11 BSQ

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.22
BTC address for reimbursement: bc1q85mru75k0v62qth79870asa60pxs306ujw3szf

Provide the Bisq client version to help developers identify the causing issue.

Other notes:

I apologise, but I am not clear on how much is lost. The maker transaction: http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/d7cdee2549b6be73f832d7121fbaa4089c4a1eae7be6303b0abd8507154859ad

Issue #197 can be used as a good example of a correct reimbursement request.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions