Implement warp syncing for the full node #1538
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
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.
Close #1483
Close #131
This PR finishes implementing warp syncing for the full node.
The full node now starts by performing a warp sync. Once finished, it immediately starts syncing new blocks. If the database doesn't contain enough information to sync new blocks, a call proof is downloaded from the network.
In parallel of syncing new blocks, the missing storage items of new blocks are downloaded.
There seems to be quite a few bugs at the moment, but I'm going to merge this PR anyway in order to unlock further changes such as removing the optimistic syncing.