Beacon API: resolve state roots and the genesis id, and serve states/{state_id}/root

Ouverte
#857 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
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
api

Piste de recherche

Start with docs/spec_deviations.md ("block_id cannot name genesis...") and docs/rpc.md to see the current contract, then read the store that keys states by block root and the Table::BlockRoots anchor logic, since the new state-root index has to be written at import and pruned alongside States/StateDiffs. Find the existing debug beacon states handler to add the 0x state-root and anchor-at-slot-0 genesis resolution, then add the GET /eth/v1/beacon/states/{state_id}/root route next to the other state routes. Done means both ids resolve for locally built devnets, the 404 stays for checkpoint-synced directories, and both docs pages and the rpc.md heading list are updated.

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

Description

Problem. Three of ethereum-package's tools load beacon states by state root or by genesis, and ethlambda refuses both. These findings come from reading each tool's source against main (b2722cfd); nothing was run.

  • checkpointz (the package runs it in full mode): it downloads the finalized bundle's state with GET /eth/v2/debug/beacon/states/0x<state_root>, gets a 404, and never serves a checkpoint. So no node can checkpoint-sync from it. It also asks for block genesis every 15 s and logs "invalid genesis block".
  • dora: it loads every state with 0x<state_root> or genesis. Blocks are indexed, but nothing derived from a state is: the validator set, the duties, epoch participation and the validator pages are all missing.
  • tracoor: it captures no states. Its first call, GET /eth/v1/beacon/states/{slot}/root, is not served. With that route it would then ask for the state by state root, which is refused too.

Both refusals are deliberate (docs/spec_deviations.md, "block_id cannot name genesis, and state_id cannot be a state root"):

  • states are keyed by block root, with no reverse index;
  • Table::BlockRoots starts above the store's anchor, and a checkpoint-synced directory has no genesis block anyway.

Fix.

  • Index state root to block root for the states the store holds, written at import and pruned with States/StateDiffs. Resolve a 0x state_id through it.
  • Serve GET /eth/v1/beacon/states/{state_id}/root.
  • Resolve genesis, on either id, when the store's anchor is at slot 0: that anchor is the genesis block and state, as on every devnet that starts from its own genesis.ssz. Keep the 404 for a checkpoint-synced directory.
  • Update docs/spec_deviations.md and docs/rpc.md. The rpc.md heading "Accepted ids, and three that are refused" lists only two.
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.