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 63195 #1021

Closed
polygonk opened this issue Nov 8, 2021 · 1 comment
Closed

Fee reimbursement for trade 63195 #1021

polygonk opened this issue Nov 8, 2021 · 1 comment
Assignees

Comments

@polygonk
Copy link

polygonk commented Nov 8, 2021

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

image

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: 715add137578128b1482f9ca0614aa68e8fb866305dda4d773ed198b4d629918
Taker: 46f1990b00a9aea4e0616c2cac240529a16f13fd81407f234a294a2bfb52ab4c
Deposit: 6c0afb222b408ad0f9dffe978d3665c43dd11c041031510e87d57e4f14ca4e46
Delayed payout: 8d4c03217954db916e5c2d654555a84d77c60e0db3ff0a83be6bff3711ce7656

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.7.5
BTC address for reimbursement:
bc1qqw38aamhsel7h86whw60zu3gwynhc0k6gddaj4

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.

@leo816 leo816 self-assigned this Nov 12, 2021
@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Nov 12, 2021
@leo816 leo816 moved this from Todo to Ready in Lost fee reimbursements Nov 15, 2021
@leo816
Copy link
Contributor

leo816 commented Nov 15, 2021

Payout made with #1028

@leo816 leo816 closed this as completed Nov 15, 2021
Lost fee reimbursements automation moved this from Ready to Closed Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants