bitcoind RPC: Skip validating header chain for newly setup nodes#414
Closed
tnull wants to merge 1 commit intolightningdevkit:mainfrom
Closed
bitcoind RPC: Skip validating header chain for newly setup nodes#414tnull wants to merge 1 commit intolightningdevkit:mainfrom
tnull wants to merge 1 commit intolightningdevkit:mainfrom
Conversation
When we just setup a new node, all chain listeners will still be synced up to the genesis hash. In order to allow for faster startup, we skip validating the entirety of the header chain by continuing with the current best block polled from `bitcoind`. Note that this doesn't noticeably change our security model as we're trusting the chain data source, for example to not censor us, anyways. And, we're of course still validating the PoW for the best block we're polling.
Collaborator
Author
|
Hmm, nevermind. I think this currently doesn't work. At least AFAICT there is no way to skip header validation after the fact, i.e., once the One way to consider shortening the header validation would be to eventually introducing checkpoints, i.e., initialize the listeners with a more recent best block on mainnet. |
This file contains hidden or 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
1 participant
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.
When we just setup a new node, all chain listeners will still be synced up to the genesis hash. In order to allow for faster startup, we skip validating the entirety of the header chain by continuing with the current best block polled from
bitcoind.Note that this doesn't noticeably change our security model as we're trusting the chain data source, for example to not censor us, anyways. And, we're of course still validating the PoW for the best block we're polling.