Validator client: support Electra, Fulu and Gloas only; drop Lean and pre-Electra fork handling
Mantenedores costumam responder em até 6 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 35/100
Direção de pesquisa
Start with the listed fork handling in crates/validator, especially beacon_node/block_contents.rs, beacon_node/http.rs, and lib.rs, then inspect the boundary tests in attestation.rs and signing.rs. First decide whether Electra remains supported; the issue describes the tradeoff but leaves it open. Done means startup rejects unsupported schedules, client fork matches cover the chosen forks, and the boundary tests target the new supported range.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
The validator client (crates/validator) should support Electra, Fulu and Gloas only, and stop carrying code for ForkName::Lean and the pre-Electra forks.
Why
The client already only works from Electra on. It submits SingleAttestations to /eth/v2/beacon/pool/attestations at every fork. It also refuses pre-Electra blocks (ProducedBlock::from_ssz) and aggregates ("electra is the earliest supported"). Every network we run against (mainnet, Sepolia, Hoodi, Platåberget) is past Electra.
The code still handles the earlier forks anyway, and Lean shows up only because ForkName is shared with the lean chain in ethlambda-types. Config::fork_at_epoch never returns Lean. Each of these branches guards a state that can't occur, but a reviewer still has to reason about it. The review of #789 spent several comments on this: whether the Lean arm's error is retryable, and whether committee 0 is right before Electra.
Line numbers below are as of 9be2506c:
- Arms that exist only to fail.
Phase0 | Altair | Bellatrix | Capella | Deneb | Leanarms appear inbeacon_node/block_contents.rs:316andbeacon_node/http.rs:881. #789 addshighest_attestation_indexwith a pre-Electra arm and aLeanarm, which returns a retryableInconsistentResponseafter the request was already made. - Pre-Gloas attestation data is requested under the slot's own fork, as far back as Phase0.
a_pre_gloas_slot_is_asked_about_under_its_own_forkassertsForkName::Phase0.attestation_data_pathsendscommittee_index=0before Gloas, and every validator signs that same data. That would also be wrong before Electra, wheredata.indexmust be the attester's own committee. - The sync committee subscription gate checks
< ForkName::Altair(lib.rs:817). - Tests pinned to the Phase0/Altair boundary:
attestation.rs:769-818(theEth-Consensus-Versionheader test) and the boundary tests insigning.rs(around lines 461, 621 and 703).
Proposal
- Refuse to start before Electra. If the beacon node's schedule (from
/eth/v1/config/spec) puts the current epoch before Electra, stop at startup with one clear error. - Give the client its own fork type, e.g.
enum ValidatorFork { Electra, Fulu, Gloas }withTryFrom<ForkName>. Convert once, wherefork_at_epochis called, so everymatchin the client has three arms and noLeanor pre-Electra ones. A fork added after Gloas still breaks every match until someone decides what it means. - Remove the pre-Electra branches: the
< Altairsync gate, the pre-Electra andLeanarms in block and aggregate decoding and inhighest_attestation_index, and comments that describe pre-Electra semantics (e.g. the index as a committee). - Move the boundary tests from Phase0/Altair to the Electra/Fulu or Fulu/Gloas boundary, so they still check that headers and domains follow the right epoch.
Consider dropping Electra too
Every network the client targets is already past Fulu:
- mainnet: Fulu at epoch 411392, December 2025
- Sepolia: epoch 272640
- Hoodi: epoch 50688
- Platåberget and the kurtosis battery (
tooling/kurtosis-assertoor/network_params.yaml): Fulu from genesis
Supporting only Fulu and Gloas would remove the code that exists for Electra alone. That mainly means the per-blob-proof block contents (ProducedBlock::from_ssz's Electra arm and Contents::WithBlobProofs, which Fulu's cell proofs replaced) and whatever publishes them. It would also move the many tests that use Electra as their default fork over to Fulu. The startup check in step 1 would then refuse anything before Fulu, and the client's fork type would have two variants.
The cost is losing any network that is still on Electra, such as a local devnet configured with Electra at genesis and a later Fulu epoch. Worth deciding before step 2, since it changes the enum.
Out of scope
config_from_spec_responsekeeps parsing the whole fork schedule. Fork versions and epochs are configuration, not fork handling.- The
altair::sync committee containers stay. They are the containers in use today, not pre-Electra support.
- Linguagem predominante
- Rust
- Estrelas
- 86
- Forks
- 34
- Merge médio
- 9d 20h
- PRs com merge (30d)
- 77
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de lambdaclass/ethlambda
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
lambdaclass/ethlambda#850 ·
Mantenedores costumam responder em até 6 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
lambdaclass/ethlambda#777 · 1 reação ·
Mantenedores costumam responder em até 6 dias
-
Run all gossip validation testsTalvez livre de novo @dicethedev assumiu há 9 dias e não há nenhum pull request aberto. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
lambdaclass/ethlambda#725 · 2 comentários ·
Mantenedores costumam responder em até 6 dias
-
Handle malformed DB dataTalvez livre de novo @dicethedev assumiu há 115 dias e não há nenhum pull request aberto. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
lambdaclass/ethlambda#529 · 4 comentários ·
Mantenedores costumam responder em até 6 dias
-
Document architectural choicesTalvez livre de novo @dicethedev assumiu há 115 dias e não há nenhum pull request aberto. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
lambdaclass/ethlambda#521 · 2 comentários ·
Mantenedores costumam responder em até 6 dias
Todas as issues de lambdaclass/ethlambda
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
antithesishq/bombadil#473 ·
Mantenedores costumam responder em até 2 dias
-
bench/api.sh exec test fails with curl exit 52, and --ignore-failure still records the timingsAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
libracoder/kiri#669 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 5 dias
-
autofixer: follow-up
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
tursodatabase/turso#12217 ·
Mantenedores costumam responder em até 1 dia
-
Declare the CMS schema library in the optional recipients extraTalvez já em andamento Um pull request vinculado a esta issue está aberto ou já foi mesclado. Abertaarea:python in-progress
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
yhay81/pyropdf#1005 · 2 comentários ·
Mantenedores costumam responder em até 1 dia