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

未關閉
#796 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 6 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
18/100
Issue 類型
重構
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
rust
領域
backend

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
Rust
星號
86
分支
34
平均合併
9 天 20 小時
30 天內合併 PR
77

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

lambdaclass/ethlambda 的其他 Issue

查看 lambdaclass/ethlambda 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。