validator: revisit CLI defaults, starting with --builder-proposals at gloas
Maintainer antworten meist innerhalb von 6 Tagen
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 18/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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-proposalson by default, or split it. Before gloas the flag means relay registrations and blinded blocks, which need a beacon node with a builder (--builderon 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's90) and--builder-min-bid(0). While ethlambda's own local payloads come back empty (getPayloadright afterforkchoiceUpdated, seen on the #707 devnet), any bid beats a local build at a boost of100. - 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
executiononlyshape,min_bid2^64-1plus a client-side refusal of a block whose bid is notBUILDER_INDEX_SELF_BUILD. - The other defaults, in the same pass:
--gas-limit's fixed60000000(#795) first.
Raised while addressing the review of #707.
- Vorherrschende Sprache
- Rust
- Sterne
- 86
- Forks
- 34
- Ø Merge
- 9 T. 20 Std.
- Gemergte PRs (30 T.)
- 77
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus lambdaclass/ethlambda
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
lambdaclass/ethlambda#850 ·
Maintainer antworten meist innerhalb von 6 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
lambdaclass/ethlambda#777 · 1 Reaktion ·
Maintainer antworten meist innerhalb von 6 Tagen
-
Run all gossip validation testsEvtl. wieder frei @dicethedev hat das vor 9 Tagen übernommen, und es ist kein Pull Request offen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
lambdaclass/ethlambda#725 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 6 Tagen
-
Handle malformed DB dataEvtl. wieder frei @dicethedev hat das vor 115 Tagen übernommen, und es ist kein Pull Request offen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
lambdaclass/ethlambda#529 · 4 Kommentare ·
Maintainer antworten meist innerhalb von 6 Tagen
-
Document architectural choicesEvtl. wieder frei @dicethedev hat das vor 115 Tagen übernommen, und es ist kein Pull Request offen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
lambdaclass/ethlambda#521 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 6 Tagen
Alle Issues in lambdaclass/ethlambda
Ähnliche Issues
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
bytecodealliance/wrpc#1785 ·
Maintainer antworten meist innerhalb von 1 Tag
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)Offen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 85/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
longbridge/nsh#2758 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
antithesishq/bombadil#473 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
bench/api.sh exec test fails with curl exit 52, and --ignore-failure still records the timingsOffenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
libracoder/kiri#669 ·
Maintainer antworten meist innerhalb von 1 Tag