Node restarted from genesis proposes on top of genesis before syncing

未關閉
#785 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 6 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
rust

研究方向

Start by tracing the startup, block production, and fork-choice paths that let a node initialized from genesis publish at slot 1001 before sync imports slot 1. Reproduce with the three-node lean devnet described in the issue and inspect the cited logs. Done when a node far behind the network no longer proposes or attests to its stale head, while a synced node can still produce normally.

由索引模型根據 Issue 內容生成。

描述

Summary

A lean node that restarts from genesis (no checkpoint sync, ~1000 slots behind the network) builds and publishes a block on top of genesis about 1 s after start, before it has synced. It reorgs away as soon as sync catches up, but its attestations to the genesis head make peers reject them.

Evidence

Local 3-node lean devnet (built from lean-quickstart genesis), node lean2 wiped and restarted while the network was at slot ~1000. Binary: branch spawned-v0.7 (#783); that branch does not change block production or fork choice, so this should reproduce on main (not yet confirmed there).

18:30:59.556 INFO ethlambda: No checkpoint sync URL provided, initializing from genesis state
18:30:59.593 INFO ethlambda: Node initialized
18:31:00.605 INFO ethlambda_blockchain: Published block slot=1001 validator_id=2
18:31:00.605 INFO ethlambda_p2p::gossipsub::handler: Published block to gossipsub slot=1001 proposer=2 block_root=71497f23 parent_root=633e24a2 attestation_count=0
18:31:00.629 INFO ethlambda_blockchain::store: Fork choice reorg detected old_head=0x71497f23… new_head=0xf9cbe592…
18:31:00.629 INFO ethlambda_blockchain::import_timing: Block import timing slot=1 … source="sync"

parent_root=633e24a2 is the genesis block. Peers then logged:

WARN ethlambda_blockchain: Failed to process gossiped attestation err=Head checkpoint 0x633e24a2… at slot 0 does not descend from finalized block 0x9e6ceb4a…

Expected

A node that is far behind the network's head should not propose (or attest to its stale head) until it is synced, or at least until its head is within some distance of the wall-clock slot.

主要語言
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 摘要。