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

オープン
#794 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 6 日以内に返信

まだ誰も着手していません。

評価

難易度
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時間
マージ済み PR(30日)
77

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

lambdaclass/ethlambda のほかの issue

lambdaclass/ethlambda の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。