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 0A6I6u #780

Closed
Johannas333 opened this issue Jan 20, 2021 · 1 comment
Closed

Fee reimbursement for trade 0A6I6u #780

Johannas333 opened this issue Jan 20, 2021 · 1 comment

Comments

@Johannas333
Copy link

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

SCREENSHOT HERE
Knipsel

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: fd69064d95ac04fffe5a4f40d02d603da7764ecf842be13cf6ea7c12ea5365f4
Taker: c9cdacf893e609dfa81930dd8eeb57cffd302d87870b17f2c6898d3f783876c2
Deposit: 664bc839a594a3018a8a163f41fd19c1f25275b628aa2b1e65f1c9f295d23476

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: 1.5.4

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

Other notes: Transaction failed with v1.5.0 or later

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

@huey735
Copy link
Member

huey735 commented Jan 20, 2021

Duplicate #687

@huey735 huey735 closed this as completed Jan 20, 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