bisq-network / bisq-network/support

Fee reimbursement for trade YjkuMeEb

Open
#2,132 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 YjkuMeEb 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: 62c9823547ce0f81a81723c2f03b8e2ebccae8cdfe95398bcc1afa7b5cc783cf
Taker: dfaafe3ccedba374cac3865db62c66bea917e084294074b48b699bd27b76118a
Deposit: ..........
BTC mining fees lost: .......... eg 0.00002389 BTC
Trade fees lost, please state if BSQ or BTC: 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.10.6
BTC address for reimbursement: bc1q43yxele4aakaamp794jcv8xa4s5wjxv7spundt

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

Other notes:
An error occurred at task: BuyerVerifiesPreparedDelayedPayoutTx
Exception message: TxIds of myPreparedDelayedPayoutTx and peersPreparedDelayedPayoutTx must be the same.

>_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

Start with the Bisq client error at task BuyerVerifiesPreparedDelayedPayoutTx and compare this request with support issue #197. Verify that the required transaction IDs, fee amounts, client version, reimbursement address, and privacy precautions are complete; done means the request has enough information for reimbursement review.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, payments
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.