spv: Request headers from peer after initial sync #2316
Merged
Conversation
This file contains 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
This modifies the peer setup procedure to request any updated headers from a newly connected peer if the connection is made after the initial sync is completed. This speeds up re-syncing after initial sync when the local client has been offline for some time (for example, due to a flicking network connection) by ensuring any and all updated headers are requested immediately, instead of waiting until a new block is announced to begin the catchup process.
jrick
approved these changes
Dec 13, 2023
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.
This modifies the peer setup procedure to request any updated headers from a newly connected peer if the connection is made after the initial sync is completed.
This speeds up re-syncing after initial sync when the local client has been offline for some time (for example, due to a flicking network connection) by ensuring any and all updated headers are requested immediately, instead of waiting until a new block is announced to begin the catchup process.