validator: revisit CLI defaults, starting with --builder-proposals at gloas

Ouverte
#796 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
18/100
Type d'issue
Refactorisation
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
backend

Piste de recherche

The defaults live in the validator client's CLI flag definitions, including --builder-proposals, --builder-boost-factor and --builder-min-bid, and in the gloas production path that sends builder_boost_factor to produceBlockV4. Start by comparing those defaults with the cross-client table in the issue and reading how #707 publishes proposer preferences. Done means a decision on which defaults change, with the opt-out behaviour specified; the issue itself lists that decision as open.

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

Description

The validator client's defaults were chosen before gloas, and at gloas the most consequential one now differs from every other client: --builder-proposals is off by default, and without it produceBlockV4 gets builder_boost_factor: 0. Pooled p2p bids therefore never win on value, only when the local build fails (#707 documents that case).

What the other validator clients send at gloas by default

Client Default at gloas Read at
Lighthouse boost 100, min_bid 0. The builder CLI flags do not reach gloas production; the body comes from builder_definitions.yml unstable @ 1a704e58
Prysm boost 100. --enable-builder "has no effect after the gloas fork" develop @ 844d8b8d
Teku p2p boost 100, min bid 0. The builder flag only empties the builder-API entries master @ 19b9214c
Lodestar boost 90 when no selection is set. executiononly sends boost 0 with min_bid 2^64-1 and refuses a block that is not self-built unstable @ efd56334
Nimbus boost 100. --payload-builder only adds relay entries unstable @ 31bc2459

So four of the five let p2p bids compete at par by default, the fifth at 90%, and only Lodestar has a mode that rules them out entirely. All five publish proposer preferences unconditionally, as #707 does.

The likely reason: a gloas p2p bid is paid through the protocol rather than by a relay, so taking one asks less trust of the proposer than a pre-gloas blinded block. That is an inference, not something the clients' code says.

To decide

  • Turn --builder-proposals on by default, or split it. Before gloas the flag means relay registrations and blinded blocks, which need a beacon node with a builder (--builder on ethlambda), so defaulting that half on is a separate question from letting gloas p2p bids compete. Splitting it would match Lighthouse, Teku and Nimbus, whose builder flags no longer gate p2p bids.
  • The defaults that come with it: --builder-boost-factor (100, or Lodestar's 90) and --builder-min-bid (0). While ethlambda's own local payloads come back empty (getPayload right after forkchoiceUpdated, seen on the #707 devnet), any bid beats a local build at a boost of 100.
  • An opt-out for self-build only, for an operator who must never take a builder's payload, even when the local build fails: Lodestar's executiononly shape, min_bid 2^64-1 plus a client-side refusal of a block whose bid is not BUILDER_INDEX_SELF_BUILD.
  • The other defaults, in the same pass: --gas-limit's fixed 60000000 (#795) first.

Raised while addressing the review of #707.

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.