Skip to content

bug: If genesis block have an extra event the sanity check fails #154

@joanestebanr

Description

@joanestebanr

Version: v0.6.4+cdk.7

The node check that genesis block provider have the expected event: a ForkID but It assume that must be the first event. In case that an L1InfoTreeUpdate is the first one the check fails!

trace:

{"level":"error","ts":1724428936.925428,"caller":"synchronizer/synchronizer.go:594","msg":"error getting rollupInfoByBlockRange after set the genesis. Expected ForkIDsOrder, got L1InfoTreeOrder","pid":1,"version":"0.6.4+cdk.7","stacktrace":"github.com/0xPolygonHermez/zkevm-node/synchronizer.sanityCheckForGenesisBlockRollupInfo\n\t/home/runner/work/cdk-validium-node/cdk-validium-node/synchronizer/synchronizer.go:594\ngithub.com/0xPolygonHermez/zkevm-node/synchronizer.(*ClientSynchronizer).RequestAndProcessRollupGenesisBlock\n\t/home/runner/work/cdk-validium-node/cdk-validium-node/synchronizer/synchronizer.go:566\ngithub.com/0xPolygonHermez/zkevm-node/synchronizer.(*ClientSynchronizer).processGenesis\n\t/home/runner/work/cdk-validium-node/cdk-validium-node/synchronizer/synchronizer.go:374\ngithub.com/0xPolygonHermez/zkevm-node/synchronizer.(*ClientSynchronizer).Sync\n\t/home/runner/work/cdk-validium-node/cdk-validium-node/synchronizer/synchronizer.go:412\nmain.runSynchronizer\n\t/home/runner/work/cdk-validium-node/cdk-validium-node/cmd/run.go:402"}

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions