bisq-network / bisq-network/support

Fee reimbursement for trade 931438

Open
#2,131 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 931438 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: e32b475ec85f80250e4d9157b17bd40443ed36f87932b9104e821a6f91c416cd
Taker: 30273a1a8ec94ec2618c4a7f8cae7550f6e46d4bfb0ae92f9efbbe8daf5b95f2
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.16
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 by reviewing the BuyerVerifiesPreparedDelayedPayoutTx error and the reimbursement format in issue #197. No source file or test is identified; the request is complete only when the reimbursement details and required transaction IDs are resolved by the support team.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain
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.