Initialize from checkpoint #98
Closed
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.
Why start syncing from genesis if we don't have to? Block 135000 is a few months old and hopefully won't ever change. Let's start from there!
opt-in to faster sync with
-tor--checkpoint.Includes bash script used to generate
checkpoint.hwhich stores the hex encoded headers for 150 blocks starting at any given height (we need this many headers so hnsd can accurately compute target difficulty in all "new" blocks that follow in the chain). It also stores the current accumulated chainwork which is needed to insert the first hard-coded header (#135000).When active, on startup after pool and chain initialization,
daemoninjects the set of headers intochainand sync begins with block #135150.Thinking ahead: we can use this mechanism to store (and prune) headers on disk for hnsd. When we reboot, we only need to read 150 headers from disk to continue syncing. If HNS ever encounters a chain reorganization deeper than 144 blocks (!) hnsd should naturally fall back to the genesis block and attempt to resync from there. (This would be a result of sending an otherwise empty chain locator to peers to request blocks)