Repository navigation
chore: unschedule Hoodi Glamsterdam activation - #33
Merged
Merged
Conversation
pk910
approved these changes
Oct 22, 2026
parithosh
approved these changes
Oct 22, 2026
spencer-tb
approved these changes
Oct 22, 2026
spencer-tb
left a comment
spencer-tb
left a comment
There was a problem hiding this comment.
it wouldn't be a real fork without some fun
3 tasks
1 task
daniellehrner
added a commit
to besu-eth/besu
that referenced
this pull request
Oct 22, 2026
* Revert "Schedule Amsterdam on Hoodi (#11531)" Unschedules the Amsterdam fork on Hoodi, matching eth-clients/hoodi#33. The 26.10.0 changelog entry stays, since that release scheduled the fork, and a new entry under Unreleased records the unscheduling. This reverts commit 059671c. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: daniellehrner <daniel@lehrner.me> * Add PR number to CHANGELOG entry Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: daniellehrner <daniel@lehrner.me> --------- Signed-off-by: daniellehrner <daniel@lehrner.me> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
github-merge-queue Bot
pushed a commit
to lambdaclass/ethlambda
that referenced
this pull request
Oct 22, 2026
## 🗒️ Description / Motivation Hoodi's Glamsterdam fork is unscheduled: [eth-clients/hoodi#33](eth-clients/hoodi#33) calls off the Gloas activation planned for epoch **132352** (2026-10-26 17:42:48 UTC), which #677 picked up. Our built-in Hoodi config is eth-clients' file byte for byte, so it follows. ## What Changed `bin/ethlambda/assets/hoodi/config.yaml` is copied again from `eth-clients/hoodi` at `987ca9a` (#33's head): | Key | Before | After | |---|---|---| | `GLOAS_FORK_EPOCH` | `132352` | `18446744073709551615` (far future) | | `GAS_LIMIT_SCHEDULE` | 200M gas at `132352` | removed | `GLOAS_FORK_VERSION` and the Gloas preset/timing keys stay, since upstream keeps them so the fork can be rescheduled with one epoch change. `bootstrap_nodes.yaml` already matches upstream. ## Correctness / Behavior Guarantees | Build | Effect | |---|---| | `main` | Gloas keys are ignored here, so only `GAS_LIMIT_SCHEDULE` drops out of the ignored-keys warning | | A gloas build | No longer activates Gloas on 2026-10-26, so it stays on the same chain as the rest of Hoodi. Existing directories resume: both the old and the new epoch are ahead of anything processed, which `first_config_difference` accepts since #677 | > [!NOTE] > eth-clients/hoodi#33 is still open at the time of writing. If its final version differs, this file should be re-copied before merging. ## Tests Added / Run No new tests: nothing pins Hoodi's Gloas epoch. ```bash cargo test -p ethlambda --bins --profile release-fast git clone https://github.com/eth-clients/hoodi && git -C hoodi fetch origin pull/33/head && git -C hoodi checkout FETCH_HEAD cmp bin/ethlambda/assets/hoodi/config.yaml hoodi/metadata/config.yaml ``` ## Related Issues / PRs - Reverts the config half of #677 - Upstream: eth-clients/hoodi#33 ## ✅ Verification Checklist - [ ] Ran `make fmt` — n/a, no Rust changes - [ ] Ran `make lint` (clippy with `-D warnings`) — n/a, no Rust changes - [ ] Ran `make test` (`test-consensus` plus `test-node`, at `release-fast`) — ran `cargo test -p ethlambda --bins` only, the crate embedding the file
matthewkeil
pushed a commit
to ChainSafe/lodestar
that referenced
this pull request
Oct 22, 2026
**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>
matthewkeil
pushed a commit
to ChainSafe/lodestar
that referenced
this pull request
Oct 22, 2026
**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>
ilitteri
pushed a commit
to lambdaclass/ethrex
that referenced
this pull request
Oct 22, 2026
eth-clients/hoodi#33 removed `amsterdamTime` from Hoodi's genesis.json, unscheduling the Glamsterdam fork planned for 2026-10-26 (epoch 132352). Keeping the timestamp would make ethrex advertise a fork ID with `next = 1793036568` that no other client announces, and activate Amsterdam on its own on the 26th, splitting it off the network. This reverts #7391, restoring the Hoodi preset, fork-ID rows and eth_config expectations to their BPO2-last state.
jflo
pushed a commit
to jflo/besu
that referenced
this pull request
Oct 22, 2026
* Revert "Schedule Amsterdam on Hoodi (besu-eth#11531)" Unschedules the Amsterdam fork on Hoodi, matching eth-clients/hoodi#33. The 26.10.0 changelog entry stays, since that release scheduled the fork, and a new entry under Unreleased records the unscheduling. This reverts commit 059671c. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: daniellehrner <daniel@lehrner.me> * Add PR number to CHANGELOG entry Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: daniellehrner <daniel@lehrner.me> --------- Signed-off-by: daniellehrner <daniel@lehrner.me> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
github-merge-queue Bot
pushed a commit
to OffchainLabs/prysm
that referenced
this pull request
Oct 22, 2026
Removes the Hoodi Gloas fork epoch (132352) and its 200M gas limit schedule entry, following the upstream unscheduling in eth-clients/hoodi#33.
tersec
added a commit
to status-im/nimbus-eth2
that referenced
this pull request
Oct 22, 2026
jimmygchen
pushed a commit
to sigp/lighthouse
that referenced
this pull request
Oct 22, 2026
* Unschedule Gloas on Hoodi (#10430) Reverts #10304 per eth-clients/hoodi#33 * Version bump --------- Co-authored-by: Eitan Seri-Levi <eserilev@gmail.com>
rayjun
pushed a commit
to rayjun/erigon
that referenced
this pull request
Oct 23, 2026
Reverts erigontech#24847 following [eth-clients/hoodi#33](eth-clients/hoodi#33), which unscheduled Hoodi's Glamsterdam activation planned for 26 October 2026 at 17:42:48 UTC (epoch `132352`). Removes Hoodi's Amsterdam timestamp, Gloas activation settings, and 200,000,000 gas-limit schedule, and restores the previous test expectations. Co-authored-by: Alex Sharov <AskAlexSharov@gmail.com>
samcm
added a commit
to ethpandaops/cartographoor
that referenced
this pull request
Oct 25, 2026
Glamsterdam on Hoodi (epoch 132352, 2026-10-26 17:42:48 UTC) was postponed with no new date (blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay), and eth-clients/hoodi#33 removed it from the network config. Reverts #115 and Amp-Thread-ID: https://ampcode.com/threads/T-01a17551-910d-71c9-8ae7-129fcb6d5668 #116 so networks.json stops advertising the fork to lab and other consumers. Co-authored-by: Amp <amp@ampcode.com> Co-authored-by: Sam Calder-Mason <samcaldermason@gmail.com>
MegaRedHand
added a commit
to suna4/ethrex
that referenced
this pull request
Oct 27, 2026
**Motivation** [eth-clients/hoodi#33](eth-clients/hoodi#33), merged 2026-10-22, unschedules the Hoodi Glamsterdam fork planned for **2026-10-26 17:42:48 UTC** (epoch 132352, `amsterdamTime` 1793036568). It removes `amsterdamTime` from `metadata/genesis.json`, restoring the files to their state before eth-clients/hoodi#31. If ethrex keeps the timestamp, it advertises an EIP-2124 fork ID with `next = 1793036568` that other clients no longer announce, and on the 26th it activates Amsterdam alone and forks itself off Hoodi. **Description** Reverts lambdaclass#7391: | File | Change | |---|---| | `cmd/ethrex/networks/hoodi/genesis.json` | drop `amsterdamTime` | | `crates/common/config/networks.rs` | drop `test_hoodi_amsterdam_activation` | | `crates/common/types/fork_id.rs` | Hoodi rows after BPO2 go back to `0x23aa1351`, `next = 0` | | `crates/networking/rpc/rpc.rs` | `eth_config` test: `last` is BPO2 again (no builder predeploys) | | `docs/roadmaps/forks-roadmap.md` | note that Hoodi was unscheduled; mainnet still TBD | The automatic revert merged `rpc.rs` by also moving an unrelated `handle_get_heap` stub. I reapplied only the test hunk, so the diff touches nothing outside the test. **How to Test** ```sh cargo test -p ethrex-config cargo test -p ethrex-common --lib fork_id cargo test -p ethrex-rpc --lib eth_config ``` All pass locally: 9 config tests (including `test_hoodi_genesis_block_hash`), 8 `fork_id` tests, and the `eth_config` test. **Checklist** - [ ] Updated `STORE_SCHEMA_VERSION` (crates/storage/lib.rs) if the PR includes breaking changes to the `Store` requiring a re-sync. (Not needed: no schema change.) Co-authored-by: Ivan Litteri <67517699+ilitteri@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unschedules the Hoodi Glamsterdam fork that was planned for 26 October 2026 (epoch 132352) by removing
amsterdamTimefrom genesis.json, all Gloas parameters (fork version/epoch, timing, churn and networking values) and the Gloas-epoch gas limit schedule from config.yaml, and the Glamsterdam section from the README, restoring these files to their state before #31.