Warm-up proposer preferences are gossiped before peers subscribe to the gloas topics

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

維護者通常 6 天內回覆

還沒有人認領這個 Issue。

評估

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

研究方向

The gossip path is in swarm_adapter.rs, where the publish error is logged only at debug; that is the first place to change the level to warn. The warm-up behaviour involves the gloas topic subscription timing and the pooled proposer preferences, which the payload does not locate in code. Done means failed publishes surface at warn and the fork-boundary republish or retry path is decided and covered by a test.

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

描述

From the epoch before gloas, the validator client publishes proposer preferences for the first gloas epoch (#707). On a network with Lighthouse, those warm-up preferences reach no peer:

  • ethlambda's beacon node joins the gloas topics an epoch before the fork and gossips each accepted preference at once;
  • Lighthouse subscribes to them only 2 slots before the fork.

On #707's devnet (gloas at epoch 6), no Lighthouse node and no builder saw any of the warm-up preferences. None of our validators had a preference for the first gloas epoch, so builders' bids for those slots were ignored.

Nothing sends them again

  • The validator client takes the 200 as delivered. #707's once-an-epoch re-send does not help: the node answers an identical entry with 200 and does not republish it.
  • The node logs Published proposer preferences to gossipsub at info even when the publish fails. The publish error is logged only at debug (swarm_adapter.rs).

Possible fixes

  • Republish the pooled preferences for the fork epoch at the fork boundary, or once the gloas topics have peers.
  • Have the node republish an entry it holds whose earlier publish failed, when the client re-sends it.
  • Publish the warm-up epoch's preferences closer to the fork.

Separately, log a failed gossip publish at warn rather than debug.

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