Skip to content

base-consensus is trying to initialize with block not present is official pruned snapshot #1076

@extradz

Description

@extradz

Ubuntu 24
base-reth v0.8.0
base-consensus v0.8.0

base-reth is normally syncing and everything looks fine, but once it finished syncing, base-consensus crash.

Logs:

May 12 01:43:19 bash[213433]: {"timestamp":"2026-05-11T23:43:19.095881Z","level":"ERROR","fields":{"message":"Failed to drain engine tasks","err":"EngineReset(SyncStart(FromBlock(MissingL1InfoDeposit(0xc710d12366805dd28afb50869e76de6e49225ecbd1d7b131941f2ac204ed85f2))))"},"target":"engine"}

Base-consensus is trying to initialize from this hash: 0xc710d12366805dd28afb50869e76de6e49225ecbd1d7b131941f2ac204ed85f2, which corresponds to Base block 44343433, around 35 days old.

But the official pruned snapshot only keeps around 1,339,200 blocks, which is about 31 days.

I previously set up and synced a Base node without any issues using the new binaries base-reth and base-consensus v0.7.6, along with the official snapshot base-mainnet-pruned-reth-1778057426 corresponding to block 45634009 (which was containing data of block 44343433 . Everything was fine and the node fully synced.

Maybe can you provide pruned snapshot with 40 days data ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions