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

Open
#861 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

@MegaRedHand is already working on this.

Since Nov 20, 2026.

  • #862 by @MegaRedHand — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
api

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Rust
Stars
86
Forks
34
Avg merge
9d 20h
Merged PRs (30d)
77

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambdaclass/ethlambda

All issues in lambdaclass/ethlambda

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.