Refactor Staged Stream Sync Long Range #4824
Open
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
Frozen
approved these changes
Jan 6, 2025
|
is it possible to write test in this PR as well ? |
done |
|
@GheisMohammadi for long range how many block behind are we talking about |
The node starts in long-range sync mode by default. Once it catches up, it switches to short-range sync. |
Also, I am currently working on a PR that dynamically switches between short-range and long-range sync based on the block gap. |
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.
Issue
This PR refactors Staged Stream Sync Long Range stage. It adds
BlockHashesstage to Staged Stream Sync. By calculating the correct hash first, this ensures data integrity and reliability in the block download process.