You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Built-in networks can't start from genesis without --checkpoint-sync-url #823
On a fresh data directory, ethlambda beacon --network mainnet|sepolia|hoodi|plataberget without --checkpoint-sync-url aborts at startup with CheckpointSyncError::BeaconGenesisSync. The built-in networks have no genesis-sync path, because the binary doesn't embed their genesis states (about 5 MB for mainnet, 150 MB for Hoodi). A loaded network directory falls back to its own genesis.ssz instead. See docs/checkpoint_sync.md.
Where it shows up
ethereum-package with checkpoint_sync_enabled: false on a public network: the ethlambda node exits at startup. In that case the package passes Lighthouse --allow-insecure-genesis-sync --ignore-ws-check, so Lighthouse syncs from genesis behind an explicit opt-in. ethpandaops/ethereum-package#1515 doesn't guard against this combination yet.
Options
An opt-in genesis anchor for the built-in networks, like Lighthouse's flag: load the genesis state from a path or URL (for example --genesis-state <path|url>), and check it against the built-in genesis_time and genesis_validators_root the same way a checkpoint anchor is checked.
Keep refusing, and make that the documented answer. ethereum-package#1515 would then reject checkpoint_sync_enabled: false with ethlambda on a public network in input_parser, with a clear message.
docs/checkpoint_sync.md explains the refusal by saying the follower "imports nothing past its anchor", so a genesis anchor would stay parked at slot 0. The beacon node now range-syncs forward after a peer's Status, so that reason may be out of date. It's worth re-checking before choosing.
Activity