Repository navigation
feat: schedule Gloas fork and 200M gas limit on Hoodi - #10313
Conversation
Set GLOAS_FORK_EPOCH to 132352 in the Hoodi network config and add a GAS_LIMIT_SCHEDULE entry raising the gas limit to 200000000 at the same epoch, mirroring eth-clients/hoodi PR 31. Update the Lighthouse, Teku, and Nimbus Hoodi interop fixtures to the scheduled Gloas fork epoch and version so assertEqualParams keeps comparing against the expected remote configs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@lodekeeper can you double check the timestamp and epoch are accurate (time wise) and that this is what we discussed in ACDE today |
|
Yes, both check out. Time: epoch ACDE #247 (summary): the Mon 26 Oct 17:42 UTC option was picked over Tue 27 Oct (epoch 132608), client releases are due by Oct 16, and the gas limit change was confirmed to happen at the fork epoch. That matches eth-clients/hoodi#31 ( Two notes on the sources, neither affects this PR:
|
Performance Report✔️ no performance regression detected Full benchmark results
|
|
🎉 This PR is included in v1.50.0 🎉 |
**Motivation** The Hoodi Glamsterdam fork planned for 26 October 2026 (epoch `132352`) was unscheduled on today's ACD call ([ACDE #248](ethereum/pm#2267)). The upstream config already reverted it in [eth-clients/hoodi#33](eth-clients/hoodi#33). **Description** Reverts #10313: - `GLOAS_FORK_EPOCH` on Hoodi goes back to `Infinity` - removes the `GAS_LIMIT_SCHEDULE` entry that raised the gas limit to 200M at the fork epoch - restores the other clients' Hoodi interop config snapshots **AI Assistance Disclosure** Written with AI assistance (Claude). Co-authored-by: lodekeeper <lodekeeper@users.noreply.github.com>
**Motivation** The Hoodi Glamsterdam fork planned for 26 October 2026 (epoch `132352`) was unscheduled on today's ACD call ([ACDE #248](ethereum/pm#2267)). The upstream config already reverted it in [eth-clients/hoodi#33](eth-clients/hoodi#33). **Description** Reverts #10313: - `GLOAS_FORK_EPOCH` on Hoodi goes back to `Infinity` - removes the `GAS_LIMIT_SCHEDULE` entry that raised the gas limit to 200M at the fork epoch - restores the other clients' Hoodi interop config snapshots **AI Assistance Disclosure** Written with AI assistance (Claude). Co-authored-by: lodekeeper <lodekeeper@users.noreply.github.com>
Motivation
Schedule the Glamsterdam fork (Gloas on the CL) on Hoodi so operators can upgrade ahead of activation and Lodestar ships the fork timing in a release.
Description
Sets
GLOAS_FORK_EPOCHto132352in the Hoodi network config, activating Glamsterdam at:13235242352641793036568(Mon, 26 Oct 2026, 17:42:48 UTC)1742213400 + 4235264 * 12 = 1793036568, epoch-aligned with Hoodi genesis.GLOAS_FORK_VERSION(0x80000910) already matches upstream.Also adds a
GAS_LIMIT_SCHEDULEentry raising the gas limit to 200M at the fork, same as Sepolia (#10172):Mirrors eth-clients/hoodi#31. The remaining Gloas params in that PR match the mainnet defaults Hoodi already inherits.
The Lighthouse, Teku, and Nimbus Hoodi interop fixtures used by the
assertEqualParamstest are updated to the scheduled Gloas epoch and version, same as #8435 did for Fulu on Holesky.🤖 Generated with Claude Code