validator: take the default target gas limit from GAS_LIMIT_SCHEDULE

Ouverte
#795 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
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust, yaml
Domaine
backend, cli

Piste de recherche

Start in the validator client where DEFAULT_GAS_LIMIT (60000000) is applied when --gas-limit is absent, and in the beacon node config parsing that drops GAS_LIMIT_SCHEDULE and the /eth/v1/config/spec handler. Check the Config struct stored under Metadata["config"] before adding a field, since that touches DB_VERSION. Done when the validator uses the scheduled limit for the proposal epoch on Sepolia and Platåberget and falls back to 60000000 otherwise, with docs/cli.md and the README updated.

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

Description

The validator client's default target gas limit is a fixed 60000000 (DEFAULT_GAS_LIMIT, overridden by --gas-limit or per validator through the keymanager API). From gloas it is signed into every proposer preference, and produceBlockV4 builds this client's own payload toward the preference's target_gas_limit. A validator left on the default therefore pulls the gas limit toward 60M on every gloas proposal, whatever the network targets.

Two built-in networks schedule something else in their config.yaml's GAS_LIMIT_SCHEDULE:

  • Sepolia: 200000000 from epoch 353024 (bin/ethlambda/assets/sepolia/config.yaml).
  • Platåberget: 200000000 from epoch 1566 (bin/ethlambda/assets/plataberget/config.yaml).

Lighthouse takes its default from the network config's GAS_LIMIT_SCHEDULE before falling back to a built-in value. This client cannot: the beacon node parses the key into nothing (it is one of the keys the ignored-keys warning names), and /eth/v1/config/spec does not serve it.

What it takes

  • Beacon node: parse GAS_LIMIT_SCHEDULE into Config and serve it from /eth/v1/config/spec. Config is stored SSZ-encoded under Metadata["config"], so a new field there is a DB_VERSION bump unless it is kept out of the stored struct.
  • Validator client: when --gas-limit is not given, default to the scheduled limit in force at the proposal's epoch, read from /config/spec, and fall back to 60000000 for a node that does not serve the key.

Until this lands, docs/cli.md and the README tell operators on Sepolia and Platåberget to pass --gas-limit 200000000.

Raised in the review of #707.

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.