Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reimbursement for _trader's onion address_ #1172

Closed
georule opened this issue Nov 11, 2022 · 1 comment
Closed

Reimbursement for _trader's onion address_ #1172

georule opened this issue Nov 11, 2022 · 1 comment

Comments

@georule
Copy link

georule commented Nov 11, 2022

trade ID #85726528
bisq screenshot

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 [TRADE ID]

I am BTC [buyer/seller] as [maker/taker] for [ASSET].
Trade amount and asset: [AMOUNT] BTC for [X ASSET]
Deposit amount: [AMOUNT] BTC

Maker: ..........
Taker: ...........
Deposit: ..........
Delayed payout: ..........
BuyerMultiSigPubKeyHex: ..........
SellerMultiSigPubKeyHex: ..........

Reimbursement amount: [AMOUNT] BTC / [30 day BSQ average] BSQ = [TOTAL AMOUNT] BSQ
Reason for reimbursement: [REASON]

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 can be used as a good example of a correct reimbursement request.

Ping @refund-agent2 and your mediator

@pazza83
Copy link

pazza83 commented Nov 11, 2022

Hi @georule

As you were the taker and there is no taker transaction ID you will not have lost any mining or trade fees on this trade.

You should be able to verify this by seeing the absence of any miner fees in Funds > Transactions

@leo816 leo816 closed this as completed Dec 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants