ChainSafe / ChainSafe/lodestar
Error: No state in cache for finalized checkpoint
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 483
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 150
Description
### Describe the bug
this is in public hoodi node
this is on public mainnet node
### Expected behavior
it should be the same to other nodes persisting 128 data columns
### Steps to reproduce
_No response_
### Additional context
_No response_
### Operating system
Linux
### Lodestar version or commit hash
unstable
Contributor guide
Research direction
The report mentions public Hoodi and mainnet nodes, Linux, and Lodestar unstable, but no file, test, or entry point. Start by comparing the attached node output with the expected output and reproduce the finalized-checkpoint cache error on the affected networks. Done means identifying the cause and making node persistence behavior match the expected 128 data columns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100