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 4523348 #589

Closed
cryptopayserver opened this issue Dec 7, 2020 · 2 comments
Closed

Fee reimbursement for trade 4523348 #589

cryptopayserver opened this issue Dec 7, 2020 · 2 comments
Assignees
@leo816
Projects
Lost fee reimbursements

Comments

@cryptopayserver
Copy link

cryptopayserver commented Dec 7, 2020 •
edited

2020-12-07 20_03_18-QEMU (BTCWKS01) - noVNC

Maker: 7be2e86eaae1e73f8d9f069df741d67a0a4a14049f3831d8070b0088dcd039bf
Taker: 26234457d2ccb38d7ab19c921d8fc04a826292342ffc357f717249f535f61c9b
Deposit: N/A
delayed payout transaction:3de911d44ae7d7b884e36dc83294a4c54a9e566064fa81db39575bba26396e3f

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.0 Linux Mint

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

Other notes:
I have security deposit blocked with funds
my btc address: bc1qtk73ejq9dxzssnlet3f3uc49xml5jxg0nr0flq
thanks.
@leo816 leo816 self-assigned this Dec 22, 2020
@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Dec 22, 2020
@leo816 leo816 moved this from Todo to In progress in Lost fee reimbursements Dec 22, 2020
@leo816 leo816 moved this from In progress to Waiting for info in Lost fee reimbursements Dec 26, 2020
@leo816 leo816 moved this from Waiting for info to In progress in Lost fee reimbursements Dec 26, 2020
@leo816 leo816 moved this from In progress to Staged in Lost fee reimbursements Jan 2, 2021
@leo816
Copy link
Contributor

leo816 commented Jan 2, 2021

Will be reimbursed with #703

@leo816
Copy link
Contributor

leo816 commented Jan 2, 2021

Closing as reimbursed via the batch transaction documented at #703 (comment)

@leo816 leo816 closed this as completed Jan 2, 2021
Lost fee reimbursements automation moved this from Staged to Closed Jan 2, 2021
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
2 participants
@leo816 @cryptopayserver