bisq-network / bisq-network/support
Reimbursement for trade 76105493
- Dominant language
- HTML
- Stars
- 19
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
>_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!**_
Reimbursement for trade 76105493
I am BTC buyer as taker for EUR.
Trade amount and asset: 0.0020 BTC for 156 EUR
Deposit amount: 0.0003 BTC
Maker: 163f26b7a4b943c44b07c54e7bc394fd1c6ba9dfcf3ff37eeb29d530368a4f1d
Taker: 09bddb0f72f2a583c5cdd8a1e8d749c9ee63f4dd7a3e6e80fcf1260828f733d2
Deposit: 0.0003 BTC
Mining fee: 0.00002450 BTC
Delayed payout: ..........
BuyerMultiSigPubKeyHex: ..........
SellerMultiSigPubKeyHex: ..........
Reimbursement amount: 0.00032450 BTC
Reason for reimbursement: TxIds
BTC address ownership proof:
>_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
The issue names no repository files, tests, or code entry points; it is a Bisq reimbursement request rather than a development task. Review the request against the reimbursement template and linked example #197; it is complete only when the required transaction details, client version, and ownership proof are supplied.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100