Built-in networks can't start from genesis without --checkpoint-sync-url

未关闭
#823 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

  1. 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.
  2. 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.

主要语言
Rust
星标
86
派生
34
平均合并
9 天 20 小时
30 天内合并 PR
77

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

lambdaclass/ethlambda 的其他 Issue

查看 lambdaclass/ethlambda 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。