Ethereum infrastructure
Ethereum schedules Glamsterdam on Hoodi; mainnet timing remains undecided
The Ethereum Foundation’s 16 October notice sets the next testnet milestone for 26 October. Here is what it means for testing, operators and ordinary users.
By CoinPressroom automated news desk ·
AI-assisted briefing, automatically published after source and duplication checks. Event date: 2026-10-16. Not investment advice.
The next scheduled milestone
The Ethereum Foundation announced on 16 October that Glamsterdam is scheduled to activate on the Hoodi testnet on 26 October 2026 at 17:42:48 UTC. The notice identifies epoch 132,352 and slot 4,235,264, and schedules Hoodi’s gas limit to rise to 200 million at the same epoch. It does not announce a mainnet activation date.
The announcement follows the upgrade’s reported activation on Sepolia on 6 October. Hoodi node operators are instructed to use compatible execution and consensus clients, while validator operators also need to check the relevant validator software and tooling. Readers should use the Foundation’s maintained release table rather than assume that any recent client release is suitable.
Why Hoodi is a distinct test
Ethereum’s network documentation describes Sepolia as the usual choice for application development and Hoodi as a network for validator, staking and protocol-upgrade testing. Hoodi has an open validator set and a large state, making it relevant to exercises involving operational infrastructure as well as complex interactions.
These are test environments, separate from the production network. Results from them can inform readiness, but a scheduled test is not evidence that a production change has already happened. The useful distinction is between an announced activation, its observed execution, and a later decision about deployment elsewhere.
Analysis: readiness needs more than a date
Our operational reading is that a useful test record should identify the exact software versions, the network, the time window and the behavior being checked. Without those details, a statement that an upgrade worked is difficult for another operator to reproduce or investigate.
Teams can also separate basic availability from correctness. A node responding to requests is one observation; an application producing the expected outcome is another. Keeping those observations separate makes a test report more useful than a single green status label. Any unsupported assumption should remain an open question rather than disappear into a pass result.
What this means for ordinary users
The Foundation states that mainnet users and ETH holders do not need to take action because of this Hoodi announcement. Mainnet timing and compatible releases will be announced separately.
For now, the next evidence to watch is the actual Hoodi activation and subsequent operator reporting. This is a development milestone, not a prediction about ETH’s price or a claim that production performance has already improved. We will treat the planned date as a plan until an observed result supports a stronger statement.
Sources
- Ethereum Foundation: Glamsterdam Hoodi Testnet Announcement — primary source
- Ethereum documentation: Networks, Sepolia and Hoodi — primary source