bisq-network / bisq-network/support
Fee reimbursement for trade dzkmvhp
- Dominant language
- HTML
- Stars
- 19
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
>_The dzkmvhp part in the issue title are the first characters of the Trade ID before the "-" (dash)._
>_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: 15107ab0852b2b2f63a694c717a55e5cbd71c9ac7a346409661ea3c4e9119ff8
Taker: e39319bc1af1b3f3be984fab599dbb91e4cf2c5b35dd2fb52713e43874f6301d
Deposit: ..........
BTC mining fees lost: 0.00002389
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
This is a Bisq reimbursement request for trade dzkmvhp, with a BuyerVerifiesPreparedDelayedPayoutTx error and missing Deposit transaction ID. Start by checking the Bisq client trade details and the reimbursement requirements in the issue; it is done when the transaction evidence is complete and the support team can assess the reimbursement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100