Make stop_gap for Esplora/Electrum configurable#957
Merged
Conversation
Expose the BDK full-scan stop gap on Esplora sync config so wallet recovery can scan past the previous fixed gap when needed. Clamp out-of-range values at full-scan time and warn about the effective value, keeping the default behavior unchanged. Co-Authored-By: HAL 9000
Expose the bounded BDK full-scan stop gap for Electrum so restore behavior can be tuned consistently across remote backends. Document that the setting applies only to BDK full_scan calls and keeps incremental sync unaffected. Co-Authored-By: HAL 9000
benthecarman
approved these changes
Jul 2, 2026
|
I've assigned @tankyleo as a reviewer! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #843.
We make the
stop_gapparameter for Esplora/Electrum syncing configurable, though clamp it to [1;1000].