Skip to content

add integrity check: commitment files should not be ahead of block files #17911

@sudeepdino008

Description

@sudeepdino008

I hit this issue yesterday and today trying to do a minimal sync of eth mainnet.

[EROR] [11-11|12:33:29.893] Could not start execution service err="behind commitment: TxNums index is at block 23765999 and behind commitment 23767224"

I have fixed it on both occasions by removing the domain steps so they are behind the block snapshots. But it looks like we're either distributing too many state steps, ot not enough block segments.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions