nervosnetwork / nervosnetwork/ckb
Cache header validation point (in case of crash)
Open
m:sync
stale
t:enhancement
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 266
- Avg merge
- 10d 5h
- Merged PRs (30d)
- 4
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
Contributor guide
Assessment
This issue has not been assessed yet.