Built-in networks can't start from genesis without --checkpoint-sync-url
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- backend, distributed-systems
Research direction
Start with docs/checkpoint_sync.md and trace the CheckpointSyncError::BeaconGenesisSync path for built-in networks and loaded network directories. Check whether beacon nodes range-sync forward after a peer's Status, as the issue suggests, before deciding between a genesis anchor and documenting the refusal. Done means choosing and implementing a supported behavior, with validation against the built-in genesis time and validators root if an anchor is added.
Written by the indexing model from the issue text.
Description
Summary
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-ingenesis_timeandgenesis_validators_rootthe same way a checkpoint anchor is checked. - Keep refusing, and make that the documented answer. ethereum-package#1515 would then reject
checkpoint_sync_enabled: falsewith ethlambda on a public network ininput_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.
- Dominant language
- Rust
- Stars
- 86
- Forks
- 34
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 77
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lambdaclass/ethlambda
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lambdaclass/ethlambda#850 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lambdaclass/ethlambda#777 · 1 reaction ·
Maintainers usually reply within 6 days
-
Run all gossip validation testsMay be free again @dicethedev claimed this 9 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lambdaclass/ethlambda#725 · 2 comments ·
Maintainers usually reply within 6 days
-
Handle malformed DB dataMay be free again @dicethedev claimed this 115 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lambdaclass/ethlambda#529 · 4 comments ·
Maintainers usually reply within 6 days
-
Document architectural choicesMay be free again @dicethedev claimed this 115 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lambdaclass/ethlambda#521 · 2 comments ·
Maintainers usually reply within 6 days
All issues in lambdaclass/ethlambda
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
antithesishq/bombadil#473 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libracoder/kiri#669 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 5 days
-
autofixer: follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tursodatabase/turso#12217 ·
Maintainers usually reply within 1 day
-
Declare the CMS schema library in the optional recipients extraPossibly taken A pull request linked to this issue is open or already merged. Openarea:python in-progress
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yhay81/pyropdf#1005 · 2 comments ·
Maintainers usually reply within 1 day