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

Fee reimbursement for trade 46803 #823

Closed
thrrht opened this issue Feb 11, 2021 · 1 comment
Closed

Fee reimbursement for trade 46803 #823

thrrht opened this issue Feb 11, 2021 · 1 comment

Comments

@thrrht
Copy link

thrrht commented Feb 11, 2021

The XXXXX part in the issue title are the first characters of the Trade ID before the "-" (dash).

bsq_failed

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: 3c2a59ca7cc2effa8a75e9195305a47f8386c3338c21806dede93c7d4306ee8d
Taker: 2d1c13f0c58eb59c1d0871890afe3c390ed828ce68857e0a9e82f4da19dd313d
Deposit: adbe9c4cbe73308a20e4aa13f80f3068167bc828ddc8efa78455e92dcb93a6d5

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: v1.5.5

Provide the Bisq client version to help developers identify the causing issue.

Other notes: The trade is in "Open Trades", its "Waiting of blockchain confirmation". I have opened a arbitration for the trade but it didnt help.

Issue #197 can be used as a good example of a correct reimbursement request.

@leo816
Copy link
Contributor

leo816 commented Feb 25, 2021

maker fee wasn't published, this reimbursement is not justified.

@leo816 leo816 closed this as completed Apr 7, 2021
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

2 participants