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

Aberta
#861 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 6 dias

@MegaRedHand já está trabalhando nisso.

Desde 20/11/2026.

  • #862 de @MegaRedHand — aberto

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
api

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Rust
Estrelas
86
Forks
34
Merge médio
9d 20h
PRs com merge (30d)
77

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de lambdaclass/ethlambda

Todas as issues de lambdaclass/ethlambda

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.