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 64423 #590

Closed
helleaven-lab opened this issue Dec 8, 2020 · 2 comments
Closed

Fee reimbursement for trade 64423 #590

helleaven-lab opened this issue Dec 8, 2020 · 2 comments
Assignees
@leo816
Projects
Lost fee reimbursements

Comments

@helleaven-lab
Copy link

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

image

TradeID: 64423-f2a4239d-1ae2-4b26-b2bf-ce4e4bcd908f-150
Maker: b2e0d4da39c3a5fbda63f61ab070bd0c292c73d833f9104ee80d2f5ff15e1e34

An error occurred at task: TakerProcessesInputsForDepositTxResponse
Exception message: Lock time of maker is more than 3 blocks different to the lockTime I calculated. Makers lockTime= 663356, myLockTime=659942

Bisq version: 1.5.0 Windows

Other notes:
I have security deposit block with funds
btc address: bc1qkn3pey3c8vwuj8nhpk5ru085k9tt7nv9d05pn7
Thanks in advance!
@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 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 @helleaven-lab