validator: take the default target gas limit from GAS_LIMIT_SCHEDULE

Aberta
#795 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
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust, yaml
Domínio
backend, cli

Direção de pesquisa

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.

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

Descrição

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.

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.