validator: accept a JSON produceBlockV3 answer, so proposals work behind blobber

未关闭
#861 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

@MegaRedHand 已经在做这个了。

开始于 2026年11月20日。

  • #862 来自 @MegaRedHand —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
30/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
rust
领域
api

调研方向

Start in crates/validator/src/beacon_node/http.rs at produce_block, read_ssz and get_ssz, and read its doc comment about there being no JSON path for a block. Follow the produceBlockV3 response types to see where version, execution_payload_blinded and data (fork BlockContents or blinded block) would be deserialized, then add a Content-Type dispatch and the new Accept header. Done means a JSON answer from a blobber-style proxy is decoded and the proposal succeeds, with the get_ssz doc rewritten. Note pull request #862 is already open against this, so coordinate before starting.

由索引模型根据 Issue 内容生成。

描述

Problem. The validator client cannot propose behind ethereum-package's blobber.

  • Blobber sits between a validator client and its beacon node. On /eth/v2/validator/blocks/{slot} and /eth/v3/validator/blocks/{slot} it rewrites Accept to application/json before forwarding (validator_proxy/proxy.go at marioevz/blobber v1.1.0, the version the package pins).
  • produce_block (crates/validator/src/beacon_node/http.rs) asks for SSZ only, and read_ssz refuses any other content type with "asked for SSZ, node answered with application/json".
  • So every proposal by an ethlambda validator client behind blobber fails.

ethereum-package's add-ethlambda branch (ethpandaops/ethereum-package#1515) therefore refuses blobber_enabled when the validator client is ethlambda, while still allowing an ethlambda beacon node behind blobber.

get_ssz's doc says why only SSZ is named: "there is no JSON path for a block". That is the gap.

Fix.

  • Decode a JSON answer to produceBlockV3: the version field, execution_payload_blinded, the values, and data as the fork's BlockContents or blinded block. Fall back on the Eth-Consensus-Version and Eth-Execution-Payload-Blinded headers when the body's fields are missing.
  • Send Accept: application/octet-stream;q=1.0,application/json;q=0.9 and dispatch on the answer's Content-Type, so a node or proxy that answers JSON still gets the proposal through.
  • Rewrite the get_ssz doc to match. produceBlockV4 (gloas) is not intercepted by blobber and can stay SSZ-only.
  • Once this is in :unstable, the package's guard can go.
主要语言
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 摘要。