support for running a node from a state snapshot (BFT-418) #75
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
pompon0
changed the title
brunoffranca
approved these changes
Mar 15, 2024
Co-authored-by: Bruno França <[email protected]>
…-consensus into gprusak-snapshot
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.
Support for a situation in which a node is started with a blockchain state at block X > 0. Such a node doesn't want to fetch and store blocks <X. I've adjusted syncing logic and validator logic (since validator also might start from state snapshot).
Added tests for the new cases.
I've removed
parentfrom the block struct, because the cost of maintaining it exceeds the gains at this point (in zksync-era payload implementation we have a commitment to the chain history anyway).