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

Offen
#861 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 6 Tagen

@MegaRedHand arbeitet bereits daran.

Seit 20.11.2026.

  • #862 von @MegaRedHand — offen

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
api

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Rust
Sterne
86
Forks
34
Ø Merge
9 T. 20 Std.
Gemergte PRs (30 T.)
77

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus lambdaclass/ethlambda

Alle Issues in lambdaclass/ethlambda

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.