Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fee reimbursement for trade 4Hf1j8-13e0c939-26dc-4972-ae0e-20d4f780c4c8-1914 #1569

Closed
JuneSites opened this issue Feb 10, 2024 · 2 comments
Closed
Assignees

Comments

@JuneSites
Copy link

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

SCREENSHOT HERE
ss 2024-02-09 at 7 53 51 PM

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: fcd10c95bb94440702c6ad4907d07d4e2f78bdac233cb0a715d96be6c0ba827e
Taker: 87453bfcdc0980018688a0809f84d0f11f38d476f04d297e77d06cdb3570694b
Deposit: n/a
BTC mining fees lost: Maker: 0.00005019 BTC / Taker: 0.00014679 BTC
Trade fees lost, please state if BSQ or BTC: 0.00011500 BTC / 0.00005000 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.14
BTC address for reimbursement: bc1qwqqk5j3a4snddv9y6p5jr7tg0x40m3844g7d8h

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

Other notes:
Timeout reached. Protocol did not complete in 120 sec. Moved to failed folder. Please reimburse mining and trading fees.

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

@darawhelan
Copy link

Hi @JuneSites

On this trade you lost:

Total: 0.00016393 BTC

@leo816 please can you add to your reimbursement list

@leo816 leo816 self-assigned this Apr 30, 2024
@leo816
Copy link
Contributor

leo816 commented Aug 5, 2024

payout made with #1663

@leo816 leo816 closed this as completed Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants