Update checked 24 October 2026: the October26 Hoodi activation has been postponed. Read the revised client instructions and current scope. The original announcement report below is preserved as history; its schedule is no longer current.
What happened
The Ethereum Foundation's Protocol Cluster has announced a Hoodi timetable for Glamsterdam. Its October 16 notice follows Sepolia and leaves the mainnet date undecided. If you hold ETH on mainnet, the Foundation says this notice requires no action from you.
Hoodi is a test network. Giving it an upgrade date does not put the same changes into the Ethereum network people use for real funds. Our earlier Sepolia report records the previous announcement; its open Hoodi date reflects the sources checked then, not this new timetable.
What is confirmed
The Hoodi configuration change merged on October 9 sets the Gloas consensus fork at epoch 132352 and the Amsterdam execution fork at Unix timestamp 1793036568. These are the two halves of Glamsterdam's scheduled Hoodi upgrade.
| Item | Scheduled value | Scope |
|---|---|---|
| Activation | October 26, 2026, 17:42:48 UTC | Hoodi testnet |
| Epoch and slot | 132352 and 4235264 | Hoodi testnet |
| Gas-limit schedule | 200,000,000 gas at the activation epoch | Hoodi testnet only |
| Mainnet activation | Undecided | Separate announcement needed |
The merged configuration supplies a useful cross-check: 1742213400 + 132352 × 384 = 1793036568. Converting that Unix timestamp gives the UTC time above. This is a check of scheduled coordinates, not an observation of a running upgraded chain.
Why it matters
The Glamsterdam specification tracker, EIP-7773, lists proposer-builder separation, block-level access lists and changes to gas accounting among the scheduled work. It is marked Review. Those changes concern Ethereum's block production, validation and execution rules; a calendar entry tells you when a network is meant to start applying them, not whether testing will succeed.
For Hoodi operators, the Foundation calls for compatible execution and consensus releases before activation. Validators also need both their beacon node and validator client updated. Its release tables still have empty rows at our October 17 check. Follow releases explicitly confirmed for Hoodi rather than assuming every client is ready. This report is not an installation guide.
For readers following fees, the distinction between a gas limit and a gas price matters here. The 200M setting belongs to Hoodi. It establishes neither a mainnet capacity change nor a guaranteed reduction in your transaction fee.
What remains unknown
The public records are not fully synchronized. EIP-7773 still leaves Hoodi's activation cells empty. The deployment planning table shows the same Hoodi date, epoch and slot as the announcement, but a different Unix value, 1793134872. We use 1793036568 because the merged network configuration, the announcement and the arithmetic agree.
Mainnet timing remains open. Brokzi has not independently observed Hoodi activation or measured post-upgrade performance. A future schedule cannot establish either result, and it does not support an ETH price forecast.
Brokzi's Take
Keep the rehearsal ticket separate from the main event. Hoodi operators have a software-readiness deadline; mainnet wallet holders have no migration, claim or transfer to perform under this notice. Check which network an upgrade headline names before following any action attached to it. Our Ethereum explainer covers the network's underlying roles.
Sources
- Ethereum Foundation Protocol Cluster: Glamsterdam Hoodi Testnet Announcement, October 16, 2026; checked October 17. Announcement and client-table status, not completed activation evidence. No publication hour is provided.
- eth-clients/hoodi PR #31: schedule Hoodi Glamsterdam activation, merged October 9, 2026; checked October 17. Configuration, epoch, timestamp and testnet gas-limit schedule.
- EIP-7773: Hardfork Meta - Glamsterdam, Review status; checked October 17. Scheduled specification list; Hoodi timing cells remain empty.
- Ethereum project management: Glamsterdam deployments, checked October 17. Its Hoodi Unix value conflicts with the date and configuration; it is not used for the activation timestamp here.
See something wrong? Brokzi logs material changes. Prepare a correction note.




