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

Abierto
#794 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 6 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
networking

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
86
Forks
34
Merge medio
9 d 20 h
PR fusionados (30 d)
77

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de lambdaclass/ethlambda

Todos los issues de lambdaclass/ethlambda

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.