-
Notifications
You must be signed in to change notification settings - Fork 243
Labels
m:syncmodule: ckb-syncmodule: ckb-syncstaleTo be closed due to a lack of activityTo be closed due to a lack of activityt:enhancementType: Feature, refactoring.Type: Feature, refactoring.
Description
Feature Request
Is your feature request related to a problem? Please describe.
When using CKB with assume_valid, currently the header verification always starts at block 0. In the case of a crash, header validation begins at block 0 again
Describe the solution you'd like
While header validation is ongoing, cache in the ckb node the latest header that has been verified, so in the case of a crash the node can start at the latest point
Metadata
Metadata
Assignees
Labels
m:syncmodule: ckb-syncmodule: ckb-syncstaleTo be closed due to a lack of activityTo be closed due to a lack of activityt:enhancementType: Feature, refactoring.Type: Feature, refactoring.