fix(cbf): implement gap-limit scanning and wait for initial sync#8
Closed
febyeji wants to merge 1 commit intoadd-cbf-chain-sourcefrom
Closed
fix(cbf): implement gap-limit scanning and wait for initial sync#8febyeji wants to merge 1 commit intoadd-cbf-chain-sourcefrom
febyeji wants to merge 1 commit intoadd-cbf-chain-sourcefrom
Conversation
ee78940 to
a1c4556
Compare
- Iterative gap-limit scanning for wallet recovery - Auto-restart CBF node with exponential backoff on unexpected exit (e.g. NoReachablePeers), preventing stale requester channels - Retry logic with backoff for filter scans and block fetches - Partial progress preservation on scan failure or timeout - Test helpers for CBF-specific sync waiting Co-authored-by: AI Assistant (Claude)
a1c4556 to
48011cd
Compare
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
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.
stop_gapwindow.last_active_indiceswas always empty, so BDK never advanced its keychain derivation index.