Skip to content

bug: node does not sync on latest #36

@ClaytonNorthey92

Description

@ClaytonNorthey92

When running the latest op-geth and op-node:

ghcr.io/hemilabs/op-geth:e92aa4e@sha256:8fae1da6c091733a37e0830f70c70ef07b98d18816fab2fa7e05a5000e57fa24
ghcr.io/hemilabs/op-node:6ca664e@sha256:aecdd7009e908838b470c8a0d844e2492d1ef1beeae1797599a46553d1fcae95

the node does not sync, error here:

t=2026-02-16T15:08:35+0000 lvl=warn msg="Engine temporary error" err="derivation failed: temp: failed to retrieve L2 parent block: failed to determine block-hash of hash 0xb86e64b32b5ebcbaa04c3e7ddfe888af12e80c41f8afdb1d79e97e8e943accda, could not get payload: not found"

this likely means that something was missed in the derivation pipeline when pulling

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions