bisq-network / bisq-network/support
Fee reimbursement for trade POCQVAE
- Dominant language
- HTML
- Stars
- 19
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
>_The XXXXX 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: ..........
Taker: ...........
Deposit: ..........
BTC mining fees lost: .......... eg 0.00005 BTC
Trade fees lost, please state if BSQ or BTC: .......... eg 5.43 BSQ or 0.000088 BTC
>_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:
BTC address for reimbursement:
>_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._
Contributor guide
No contributing guide indexed for this repository
Research direction
No repository file or test is named. Start with the reimbursement template in this issue and compare the Maker, Taker, Deposit, fee, version, and address fields with the linked example; done means providing the requested transaction details and ensuring the screenshot contains no private information.
Written by the indexing model from the issue text.
Assessment
- Domain
- payments
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100