Glamsterdam did not remain scheduled for its previously announced October 26 Hoodi activation. The Ethereum Foundation’s October 22, 2026 notice explicitly supersedes the old instructions and sets no replacement date. For an ETH holder this is not a mainnet upgrade instruction; for a Hoodi operator it is a reason to verify that the installed client configuration reflects the postponement.
Read the correction before the countdown
The Foundation’s postponement notice says developers need more time to investigate EIP-8037’s interaction with existing mainnet contracts. A postponed test does not establish that those production contracts have already been affected by a newly activated rule. The notice concerns Hoodi and says mainnet users need no action as a result of this update.
The older Hoodi announcement now begins with a correction, while retaining the original schedule below. Reading only the old activation table can therefore give a different impression from reading the complete page. Treat the table as historical context where the correction says it has been superseded.
An official domain does not make every displayed date current
| Document inspected on October 27 | What was visible | How to use it |
|---|---|---|
| October 22 postponement notice | Old activation removed; no replacement date | Current event-specific instruction |
| October 16 announcement with update banner | Correction above the original table | Read the update before using older values |
| ethereum.org roadmap, marked updated September 14 | A Hoodi milestone dated October 27 | An older overview, not evidence overturning the postponement |
| Your client team’s release notes | Changes for that implementation | Verify the actual installed release and configuration |
The roadmap page is a useful example of why publication context matters. At this check, its older status card still displayed an October 27 Hoodi milestone. That is not enough to infer a newly scheduled activation after October 22. When sources conflict, look for the dated, network-specific notice and an explicit new schedule rather than silently combining their dates.
The configuration change has its own primary record
The merged Hoodi configuration change, dated October 22, removes the scheduled Amsterdam activation, Gloas parameters and the associated gas-limit schedule. This is direct evidence of changing a future configuration. It is not a reversal of transactions already recorded in Hoodi, and it does not increase Ethereum mainnet’s gas limit.
Client implementations also have their own release evidence. The notice links Lodestar 1.50.1 and Besu 26.10.1 among its confirmed releases. These are examples to trace back to the relevant client team, not a recommendation to install both regardless of your stack. Custom settings and other implementations require their own checks.
The practical operator question is more precise than “Is my client recent?” Ask whether the release notes and active Hoodi configuration remove the cancelled activation. An earlier version table that supported the original plan does not answer that question. Do not change mainnet settings to imitate a testnet correction.
Separate an operator task from a wallet task
- If you only hold or transfer mainnet ETH, do not treat a Hoodi countdown as a request to move or migrate coins.
- If you run Hoodi infrastructure, review the relevant execution, consensus and validator-client instructions for the postponed schedule.
- If a payment is delayed, check its actual network and transaction; a testnet scheduling notice is not a diagnosis of that payment.
- Wait for an explicit replacement Hoodi announcement instead of inventing a new activation time from an older calendar.
There is no need to sign a recovery message, share a seed phrase or pay an activation charge merely because a testnet date changed. This does not diagnose an actual phishing campaign; it explains why a purported instruction of that kind would need separate verification. The next evidence to watch is a revised activation announcement and corresponding client guidance, not a forecast of ETH’s price.
For transfers, compare the chain your recipient expects with the route you are actually using. The supported-coin page is relevant before choosing an exchange route, while the exchange flow explains the service interaction. None of these steps is replaced by a testnet roadmap entry. Recheck the source notices before planning a transfer because the schedule may subsequently change.
FAQ
Does the Ethereum Glamsterdam upgrade date on an old roadmap override the Hoodi postponement?
Not by itself. The October 22 notice explicitly supersedes the earlier Hoodi instructions, so look for a subsequent network-specific activation announcement.
Does the Ethereum Glamsterdam delay mean mainnet ETH must be moved?
The postponement notice says mainnet users need no action as a result of this update. It changes a testnet schedule, not your recipient’s payment instructions.
Are earlier Ethereum Glamsterdam client tables sufficient for a Hoodi operator?
No: the earlier table covered the original activation plan. Verify the instructions and configuration that implement its removal for your particular clients.