ChainSafe / ChainSafe/lodestar

Error: No state in cache for finalized checkpoint

Open
#9,718 3 comments 0 reactions 0 assignees View on GitHub
meta-bug
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

Image

this is on public mainnet node

Image

### Expected behavior

it should be the same to other nodes persisting 128 data columns

Image

### Steps to reproduce

_No response_

### Additional context

_No response_

### Operating system

Linux

### Lodestar version or commit hash

unstable

Contributor guide

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.