Ethereum’s Hoodi Test Network Set for Crucial Glamsterdam Upgrade on October 26

The Ethereum network has officially scheduled the Glamsterdam upgrade for the Hoodi test network to take place on October 26, 2026, at 17:42:48 UTC, which establishes a precise deadline for node operators to ensure their software is updated.

This schedule was announced by the Ethereum Foundation on October 16. The deployment on Hoodi follows the previous activation of Glamsterdam on the Sepolia test network, which occurred on October 6. This specific upgrade pairs modifications to block production and validation with a planned target of 200 million gas.

Operator Software Requirements

Every operator on the Hoodi network must update both their execution and consensus clients before the activation time arrives. This requirement is mandatory for every single node that is participating in the test network. Any failure to update the software in time will result in that node being excluded from the upgraded network state.

Validators are facing specific dual-upgrade requirements that demand attention. They are required to update the beacon node as well as the validator client. Beyond the simple installation of software, validators must spend time reviewing new duties and ensuring that there is full compatibility with builder tooling. Furthermore, they must adjust their gas-limit settings so that they align with the upgraded parameters of the testnet.

As of October 17, the Foundation provided a comprehensive list of confirmed releases for Hoodi. Ethrex is currently listed with a release candidate version. However, several other major client implementations have not yet been listed on the confirmed releases page of the Foundation. These include Grandine, Lighthouse, Erigon, go-ethereum, and Reth. Operators who are using these specific clients should verify that their own release notes confirm compatibility with the Hoodi activation.

Besu 26.10.0 stands as a confirmed release for this upgrade. This particular version includes specific changes regarding storage management. It is designed to migrate Bonsai code storage upon the first startup and it retains a larger amount of history when pruning data. Operators who plan to downgrade Besu to an older version must utilize the documented besu storage revert-code-format command. This specific step is required before an older version of the software can successfully reopen the database.

Technical Changes and Gas Targets

The target of 200 million gas represents a planned budget for the amount of computational work allowed per block. It should be viewed as a guideline for the block limit rather than an instantly enforced ceiling. The actual block limit will adjust gradually according to existing Ethereum rules. While client defaults and recommendations are set by the schedule, the individual preferences of the operator are preserved within the configuration.

The overall throughput of the network will depend on the complexity of the transactions. Similarly, fees will continue to depend on the level of demand. The upgrade does not change the fundamental mechanics of the fee market, but it does alter the total capacity available for transaction inclusion.

Glamsterdam is a combined upgrade that consists of two distinct components. The execution layer is receiving the Amsterdam upgrade, while the consensus layer is receiving the Gloas upgrade. A key feature of this combination is the enshrined proposer-builder separation. This change moves the exchange between block proposers and builders directly into the protocol itself. This provides validators with more time to check execution data before the blocks are finalized.

The upgrade also introduces block-level access lists. These lists are used to record accessed accounts, storage, and state changes. This specific data allows clients to perform more work in parallel, which improves overall efficiency. Developers should be aware that changed gas pricing rules may affect smart contracts. Contracts that rely on fixed stipends, hardcoded limits, or assumptions regarding remaining gas may behave differently. The Foundation advises developers to test their contracts and their gas estimation logic under these new rules.

ETH holders and operators on the mainnet have no action to take as a result of the Hoodi announcement. The timing for mainnet activation remains undecided. The Hoodi test is a prerequisite for validating the upgrade on a live test network before any schedule for the mainnet is considered.