bisq-network / bisq-network/support

Reimbursement for trade wlbmpf #2144

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

Description

Image

Maker: fce82b385df837146cde55d264df4d62bc60ceb641508cd2e671b2313b1b3490
Taker: 03d92c02d66c0ec7f598e070767116a887a76ce4c61bed7ffa130f1c1ab0d30f
Maker & Tax fee loss: 0,00009890 BTC
BISQ Version: 1.10.6
I am BTC Buyer (maker)
BTC Adress for reimbursement: bc1q8e2ezh2tagt2uxltknfztegewq8x4qt575qjqz

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

>_Repeat the above for each trade you need to be reimbursed_

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

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

Other notes:

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

>_Ping @refund-agent2 and your mediator_

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository files or tests are named. Start by reviewing the trade details, the BuyerVerifiesPreparedDelayedPayoutTx error, and the Bisq 1.10.6 context; done means the reimbursement request has been investigated and resolved by the support process.

Written by the indexing model from the issue text.

Assessment

Tech stack
blockchain
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.