validator: take the default target gas limit from GAS_LIMIT_SCHEDULE

Offen
#795 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 6 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust, yaml
Bereich
backend, cli

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Rust
Sterne
86
Forks
34
Ø Merge
9 T. 20 Std.
Gemergte PRs (30 T.)
77

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus lambdaclass/ethlambda

Alle Issues in lambdaclass/ethlambda

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.