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

Ouverte
#701 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 6 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
52/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
86
Forks
34
Merge moyen
9 j 20 h
PR mergées (30 j)
77

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de lambdaclass/ethlambda

Toutes les issues de lambdaclass/ethlambda

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.