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
Coins not discovered within initial sync might never be found #521
Comments
Fixes #965. Seems to be an usptream bug: bitcoindevkit/bdk#521.
I think the issue might be because we always go from Line 1506 in fdb272e
Instead, what I think we should be doing is going from |
1000 is a number chosen at random that will hopefully get us through this until the upstream bug is fixed. We should revert this to `None` as soon as BDK handles this case gracefully. Fixes #965. Seems to be an upstream bug: bitcoindevkit/bdk#521.
Yes. I've noticed this as well. IMO what we should be doing is caching on-demand rather than batching some arbitrary number stuff up front. I think #461 made this easier. |
1055: Scan for the next 1000 addresses r=thomaseizinger a=thomaseizinger Fixes #965. Seems to be an usptream bug: bitcoindevkit/bdk#521. Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
Describe the bug
BDK does not seem to always find all coins on-chain if the wallet has been in use for a while and we don't have a local database.
To Reproduce
I've made a private repository here (contains the testnet coin descriptor, please don't steal them 🙃 ) and invited a few select maintainers of this repository: https://github.com/thomaseizinger/bdk-missing-coins-bug
Expected behavior
BDK to always find all coins as long as they are within a specified
stop_gap
.Build environment
Additional context
I've tested this also with the esplora-ureq backend but without luck.
The text was updated successfully, but these errors were encountered: