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

Ouverte
#794 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 6 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
22/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
networking

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
86
Forks
34
Merge moyen
9 j 20 h
PR mergées (30 j)
77

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de lambdaclass/ethlambda

Toutes les issues de lambdaclass/ethlambda

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.