Ethereum client teams are releasing software for the next public deployment of Glamsterdam, with the upgrade scheduled to activate on the Hoodi testnet on October 26. The fork is set for epoch 132,352, slot 4,235,264, corresponding to 17:42:48 UTC, and Hoodi’s gas limit will rise to 200 million at the same point.
According to the Ethereum Foundation’s official Hoodi announcement, node operators must upgrade both their execution and consensus clients before activation. Hoodi follows Glamsterdam’s October 6 activation on Sepolia, giving developers and infrastructure providers another long-lived public environment in which to test the upgrade before Ethereum mainnet.
Glamsterdam combines Amsterdam on the execution layer with Gloas on the consensus layer. Its two headline changes are Enshrined Proposer-Builder Separation, or ePBS, under EIP-7732 and Block-Level Access Lists under EIP-7928, alongside multiple changes to gas pricing and state accounting intended to support higher Layer 1 capacity.
Client Teams Release Hoodi-Compatible Software
Several client teams have now published versions containing the Hoodi activation configuration. On the consensus side, confirmed releases include Lodestar v1.50.0, Nimbus v26.10.1 and Teku v26.10.1. Prysm v7.3.0 was subsequently released with the Hoodi Gloas fork explicitly scheduled at epoch 132,352 and the 200M gas-limit change included.
Execution-layer support currently includes Besu v26.10.0, Ethrex v30.0.0-rc.2 and Nethermind v2.2.0. Nethermind’s release schedules Amsterdam for the corresponding Unix timestamp and requires Hoodi nodes to update before the fork.
Not every client has reached the same release stage. Lighthouse v8.3.0-rc.0 supports Gloas on Sepolia but should not be described as the final Hoodi release, while the Ethereum Foundation had not yet listed confirmed Hoodi versions for Geth, Erigon or Reth in its original October 16 compatibility table.
That staggered rollout is normal for an Ethereum upgrade because independent client teams implement the same consensus specification on separate schedules. Earlier Prysm releases had already been adding ePBS and data-availability infrastructure, but preparation code is different from a release containing the final activation parameters for a specific network.
Validator operators face an additional requirement under Gloas: the beacon node and validator client must both understand the new block-production model. External builder infrastructure also needs compatible configuration because ePBS changes how builders commit to and subsequently reveal execution payloads.
Hoodi Tests Ethereum’s Higher-Capacity Architecture
EIP-7732 moves important parts of the proposer-builder relationship directly into Ethereum consensus. Instead of relying entirely on external middleware, builders commit to execution payloads and payments through protocol-defined mechanisms, while a Payload Timeliness Committee checks whether payloads and associated data were revealed on schedule.
Block-Level Access Lists address execution from another direction. They record the accounts and storage locations touched by a block, giving clients information that can support more concurrent state access and validation. BALs create infrastructure for greater parallelism, but they do not mean every Ethereum transaction automatically executes in parallel after the fork.
The 200M gas limit provides the test environment for those scaling changes. Ethereum Foundation’s broader 2026 scaling roadmap has tied higher gas capacity to client benchmarking and protocol improvements rather than treating larger blocks as an isolated parameter increase.
Hoodi activation therefore represents another validation stage, not the production rollout. Ethereum mainnet does not yet have a Glamsterdam activation date, and mainnet validators or ordinary ETH holders do not need to take action based on the Hoodi announcement.
The October 26 test will instead show whether independently developed execution and consensus clients can operate together under ePBS, BALs and the substantially higher gas ceiling. Only after those public test deployments provide sufficient confidence will client teams determine when Glamsterdam is ready for Ethereum mainnet.
Jack Reynolds is SatoshiPick’s infrastructure mind. Based in Denmark, he follows Bitcoin, Ethereum, Layer 1 networks, stablecoins and DeFi with a practical question always in the background: does this actually make crypto work better?
His articles focus on the systems beneath the headlines: settlement rails, protocol upgrades, stablecoin usage, DeFi coordination and the regulatory limits around them. Jack avoids turning technical coverage into a maze. He explains what is live, what is still experimental and why the difference matters.