bisq-network / bisq-network/support

Fee reimbursement for trade UGGWZWX

Open
#2,123 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

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: ..........77f0dfe63439e3d8185b2678e293b0660455a4b120b2f9bd4783a7feb76e6e14
Taker: ...........82b4577de9fa15442fda1f0383fd894c38f670d82df6fb947d6967393899deb8
Deposit: ..........
BTC mining fees lost: 0.00002330 BTC
Trade fees lost:
Bisq version: 1.10.4
BTC address for reimbursement:

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

Other notes: An error occurred at task: BuyerVerifiesPreparedDelayedPayoutTx. Please reimburse me back my fees

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

Review the attached Bisq client screenshot and the reported error at BuyerVerifiesPreparedDelayedPayoutTx, using Bisq version 1.10.4 and the trade identifiers provided. Compare the request with support issue #197; done means a maintainer has investigated the reimbursement request and recorded the appropriate resolution.

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
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.