bisq-network / bisq-network/support

Fee reimbursement for trade hzgmhiq

Open
#2,149 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
19
Forks
13
PR merge metrics
No merged PRs in 30d

Description

>_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: 1b94901bdddc62a6b6abbf3c7ba77806eacf379af5eb3ce382c758a4f4911d41
Taker: d9f45aad8a6b54dfb5dd850f36a8857c070aced48d5a7d76ec380bb65e10aafb
Deposit: N/A
BTC mining fees lost: 0.00002330 BTC
Trade fees lost, please state if BSQ or BTC: 0.00007500 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.10.7
BTC address for reimbursement: bc1qmh6kfyjy22xqpmx38esv0qapa3kawt8f6cft2t

>_Provide the Bisq client version to help developers identify the causing issue._

Other notes: Other notes: Trade failed with BuyerVerifiesPreparedDelayedPayoutTx:
TxIds of myPreparedDelayedPayoutTx and peersPreparedDelayedPayoutTx must be the same.

The deposit transaction was not created.

>_Issue [#197](https://github.com/bisq-network/support/issues/197) can be used as a good example of a correct reimbursement request._

Contributor guide

No contributing guide indexed for this repository

Research direction

This is a Bisq support reimbursement request and the payload names no repository files, tests, or code entry points to investigate. Review the listed trade identifiers, fee amounts, client version, and failure note; done would be maintainer handling of the reimbursement request rather than a code contribution.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, payments
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.