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.

Sign up for GitHub

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

Jump to bottom

Fee reimbursement for trade ODOFCVW #1051

Closed
klnit opened this issue Jan 11, 2022 · 2 comments
Closed

Fee reimbursement for trade ODOFCVW #1051

klnit opened this issue Jan 11, 2022 · 2 comments
Assignees
@leo816
Projects
Lost fee reimbursements

Comments

@klnit
Copy link

klnit commented Jan 11, 2022

grafik

Maker: 37bf81ca5e44bc6f2283737e43bd21e97819f2949f7d3a8b12bf1272f76d288b
Taker: f1fe8699501e6678b29a40c2ea6efb65de59f315e7a45d0262d766b3a69bffb5
Deposit: ..........

Bisq version: 1.8.0
BTC address for reimbursement: bc1qqtpf9kfv4amuesk2lttdzxsa0q9pz2khgr8nxc
@pazza83
Copy link

pazza83 commented Feb 2, 2022

Hi @klnit

Thanks for posting.

As you were the taker for this trade I can see that you lost both trade fees (2.12 BSQ) and miner fees (0.00002390 BTC) on this trade.

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

@leo816 leo816 self-assigned this Feb 19, 2022
@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Feb 19, 2022
@leo816 leo816 added this to To do in Case Tracking via automation Feb 19, 2022
@leo816 leo816 removed this from To do in Case Tracking Feb 19, 2022
@leo816 leo816 moved this from Todo to Ready in Lost fee reimbursements Feb 23, 2022
@leo816
Copy link
Contributor

leo816 commented Feb 23, 2022

Paid out with batch reimbursement #1064

@leo816 leo816 closed this as completed Feb 23, 2022
Lost fee reimbursements automation moved this from Ready to Closed Feb 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leo816 leo816

Labels
None yet
Projects
Lost fee reimbursements
  
Closed
Milestone
No milestone
Development

No branches or pull requests
3 participants
@klnit @leo816 @pazza83