Bound how far Beacon API requests can advance a state before validating them

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

Mantenedores costumam responder em até 6 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
52/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust

Direção de pesquisa

Read the implementations and related PRs #663, #671, and #646 for the attester and proposer duties, sync duties, and block publication paths. Trace where each path calls process_slots and how it determines the head, then inspect the relevant tests. Done means each path rejects requests that would advance too far when the head lags, while preserving the stated late or missing boundary block cases.

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

Descrição

Several Beacon API paths advance a stored state with process_slots to answer a request, bounded only by the wall clock, not by the head. With the head lagging the clock (syncing, stalled, or behind after downtime) — or with an attacker choosing an old parent — one request can run hundreds of epoch transitions (~0.7–0.9 s each on mainnet, per #632/#633) on a blocking thread. The cache doesn't save it: its key includes the head root, which moves while syncing.

The existing 503 while-syncing guards don't cover this: SyncStatusController reports synced during a beacon catch-up (#636, "still open" #1).

Path PR Advance Status
POST /eth/v1/validator/duties/attester/{epoch}, GET /eth/v{1,2}/validator/duties/proposer/{epoch} #663 head → wall_epoch + 1 merged without a cap ("fix in another PR")
POST /eth/v1/validator/duties/sync/{epoch} #671 head → first epoch of clock_period (a period is 256 epochs) approved, cap requested
POST /eth/v2/beacon/blocks #646 any known parent → block slot, before the signature check cap requested

Proposal

  • Duties (#663): 503 when epoch > head_epoch + 2.
  • Sync duties (#671): only advance when first_epoch(requested_period - 1) <= head_epoch + 1, else 503. This also avoids answering a committee the chain may not produce: sync duties carry no dependent_root, so a VC can't detect a wrong answer.
  • Block publication (#646): 400 when the parent is below the finalized checkpoint or more than a couple of epochs behind the block's slot.

Each keeps the honest case these PRs were written for (a late or missing boundary block) and refuses the expensive, speculative ones. A test per path with the head several epochs behind the clock should assert the refusal.

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.