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

Take Offer Error: LockTime of Maker is more than 3 blocks different to the LockTime I have #4707

Closed
mpowacht opened this issue Oct 26, 2020 · 10 comments · Fixed by #4764
Closed

Comments

@mpowacht
Copy link

mpowacht commented Oct 26, 2020

Description

Version

1.3.9 and 1.4.2

Steps to reproduce

Expected behaviour

Actual behaviour

When taking an offer for 0.01 BTC with EUR/Revolut with trade ID izxdhj-877b1ad8-1aa3-4fa1-b471-30758e64ba71-139 I get:
Take Offer Error: LockTime of Maker is more than 3 blocks different to the LockTime I calculated.
Screenshot below.
Tried several times. The same happens when I perform a local take offer in national currency THB and national bank transfer.

Screenshots

image

image

image

Device or machine

Additional info

@boring-cyborg
Copy link

boring-cyborg bot commented Oct 26, 2020

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

@ghost
Copy link

ghost commented Oct 26, 2020

What are the two lockTime numbers shown in the error message? (they are clipped out of view in the screenshot).

@mpowacht
Copy link
Author

I see them in the first screenshot above, but here they are: makers LockTime=657184, myLockTime=647999

@ghost
Copy link

ghost commented Oct 27, 2020

Maker's lock time is good, yours is not. Probably your SPV state is stalled, please resync it from the Bisq interface as described here: https://bisq.wiki/Resyncing_SPV_file

Unfortunately the trade is failed, but after resyncing any further trades should complete normally. You can request a reimbursement for lost trade fees here: https://github.com/bisq-network/support/issues

@mpowacht
Copy link
Author

Thanks, I am trying to sync the SPV state and will get back.

@chimp1984
Copy link
Contributor

@mpowacht Did you take the offer when your app was still syncing the BTC blockchain?

@mpowacht
Copy link
Author

SPV is now synced without any errors. I'll try taking an offer today. I haven't taken an offer while the blockchain was syncing.

@mpowacht
Copy link
Author

Took an offer without any problems.

@mpowacht
Copy link
Author

@mpowacht Did you take the offer when your app was still syncing the BTC blockchain?

Hi there, I now recall that the syncing process (syncing indicated in bottom status bar) was incomplete while taking the offer. I also seem to recall that syncing was actually always in progress and never completed. So deleting SPV and re-sync was a good remedy.

@chimp1984
Copy link
Contributor

I opened a issue to fix that problem: #4727

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants