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 E2V0RN #1073

Closed
cl0uding opened this issue Mar 21, 2022 · 2 comments
Closed

Fee reimbursement for trade E2V0RN #1073

cl0uding opened this issue Mar 21, 2022 · 2 comments
Assignees

Comments

@cl0uding
Copy link

Kazam_screenshot_00000

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: d22c5f0b56b8981c51fc325f7ddaa1febb16d3654effa33d25df22dbcbaee6f1
Taker: 7f6c1a54a63d13abbd4e86145d3d69b378ab26cd150a17a5db9d2f2686bda9ed
Deposit: N/A

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.8.4
BTC address for reimbursement: bc1qyu6v47k24s2uq8lc5z95kgz50rwfu68928re22

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.

@pazza83
Copy link

pazza83 commented Mar 21, 2022

Hi @cl0uding thanks for opening the issue.

I can see you lost trading fees and mining fees on this trade.

@leo816 please can you add to your list for reimbursement. Thanks

@leo816 leo816 self-assigned this Mar 30, 2022
@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Mar 30, 2022
@leo816 leo816 moved this from Todo to Ready in Lost fee reimbursements Apr 29, 2022
@leo816 leo816 moved this from Ready to In progress in Lost fee reimbursements Apr 29, 2022
@leo816
Copy link
Contributor

leo816 commented Apr 29, 2022

Payout with #1081

@leo816 leo816 closed this as completed Apr 29, 2022
Lost fee reimbursements automation moved this from In progress to Closed Apr 29, 2022
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

3 participants