The Glamsterdam Hoodi upgrade is scheduled for October 26, 2026, at 17:42:48 UTC, with the testnet’s gas limit rising to 200 million at the same activation epoch. Following Glamsterdam’s October 6 activation on Sepolia, the next deployment requires Hoodi operators to update both execution and consensus clients. The Ethereum Foundation’s October 16 announcement does not set a mainnet date.

Key Takeaways

  • Hoodi activation is scheduled for epoch 132,352 and slot 4,235,264, alongside a gas-limit increase to 200 million.
  • Hoodi validators must update their execution client, consensus beacon node and validator client, and review new builder-related duties.
  • Developers should test gas assumptions and estimation under the revised rules; mainnet users and operators need take no action from this announcement.

Table of Contents

Glamsterdam Hoodi schedule and deployment status

Hoodi is the next scheduled testnet deployment for Glamsterdam, which combines the Amsterdam execution-layer upgrade with the Gloas consensus-layer upgrade. Its planned 200 million gas limit matches Sepolia’s. The Ethereum Foundation’s Glamsterdam Hoodi announcement distinguishes this testnet deadline from mainnet deployment. Client teams have not decided the mainnet activation time, and mainnet-compatible releases will be announced separately.
Item Details
Sepolia deployment Activated October 6, 2026, at 13:53:36 UTC; epoch 353,024, slot 11,296,768.
Hoodi deployment Scheduled October 26, 2026, at 17:42:48 UTC; epoch 132,352, slot 4,235,264.
Hoodi gas limit Scheduled to rise to 200 million at the activation epoch, matching Sepolia.
Mainnet deployment Activation date remains undecided; this announcement schedules no mainnet upgrade.

What Hoodi operators need to update

Before activation, non-staking nodes need compatible execution and consensus clients. Validators must also ensure that both their beacon node and validator client are updated. Software that does not support the new rules cannot follow the upgraded network. The announcement lists consensus releases for Grandine, Lighthouse, Lodestar, Nimbus, Prysm and Teku. Its execution-client table provides versions for Besu, Ethrex and Nethermind, while Erigon, go-ethereum and Reth have no versions listed. Operators should select only releases whose notes explicitly confirm support for the scheduled Hoodi activation. The tooling table lists commit-boost 0.12.0-rc1. Additional builder and validator compatibility guidance remains pending confirmation. Operators using external block-building infrastructure should review its Glamsterdam instructions, alongside their client’s guidance on validator gas-limit targets.

Why builder and validation workflows change

For validator and builder teams, readiness involves more than installing binaries. EIP-7732, enshrined proposer-builder separation, introduces protocol-defined responsibilities for a process that previously relied more heavily on trusted middleware. Teams need to check their tooling against the new duties and interfaces. Under that process, a proposer commits to a builder’s execution payload before the builder discloses it. Ethereum’s protocol manages the proposer’s payment, while a payload timeliness committee checks timely disclosure and blob-data availability. Separating consensus checks from execution checks also gives validators more time to assess execution payloads. The other headline change, EIP-7928, targets client validation work. Enforced block-level access lists identify accounts and storage touched by a block and capture post-transaction state changes. Clients can use that information to parallelize disk reads and transaction validation and calculate state roots more efficiently. Together, these changes support greater execution capacity while keeping validation practical for node operators.

Where application testing should focus

Gas repricing makes contract assumptions a priority for testing. EIP-8037 increases and separately meters state-creation costs, while EIP-8038 changes state-access costs. Other scheduled changes affect intrinsic transaction gas, calldata, access lists and block gas accounting. Contracts using fixed gas stipends, hardcoded limits or assumptions about remaining gas may need changes. Developers should use the repricing impact guide to identify affected contracts and test gas estimation on Sepolia and, after activation, Hoodi. Testing should also cover relevant changes to logs, opcodes and client interfaces. Scheduled additions include ETH transfer logs, a slot-number opcode, a higher maximum contract size and a deterministic factory contract.

Conclusion

The immediate deadline is for Hoodi infrastructure: compatible clients and tooling must be ready before October 26. Developers have a testnet rollout against which to check application behavior, while mainnet activation remains a separate, unscheduled step.

Read More News

More FinanceVelix news

Disclaimer

This FinanceVelix article provides general information, not personalized financial, investment, legal, or tax advice. Crypto prices can change quickly, and you could lose all invested funds. Facts reflect the material available when published and may change. Check important information independently and consult a qualified professional when needed. Mentioning an asset, company, or service is not an endorsement.