Ethereum Glamsterdam upgrade moves to its next public test
The Ethereum Glamsterdam upgrade is scheduled to activate on Hoodi on October 26, giving developers and node operators another public environment in which to test Ethereum’s proposed scaling changes.
The Ethereum Foundation’s October 16 announcement fixes activation at epoch 132,352, slot 4,235,264. It also schedules a 200 million gas limit, matching Sepolia’s upgraded configuration.
For the ecosystem, the significance lies in the rehearsal: software that works under controlled development conditions must also perform across different client implementations and operational setups.
Deployment schedule
Network | Activation | Position |
Sepolia | October 6, 2026 | Already activated |
Hoodi | October 26, 2026, 17:42:48 UTC | Scheduled |
Ethereum mainnet | Not announced | Awaiting a decision |
The Foundation states that client teams will announce mainnet timing once it is decided.
What a 200 million gas limit actually means
Gas measures the computational work required to execute Ethereum transactions. A block gas limit sets the execution budget available within a block.
Increasing that budget can allow more work to fit into each block. It does not mean 200 million transactions, nor does it establish a fixed transactions-per-second figure. Different activities consume different amounts of gas: a straightforward transfer and a complex smart-contract interaction impose different workloads.
A higher capacity ceiling also differs from actual usage. Blocks do not automatically fill simply because more space becomes available.
For users, any eventual fee benefit would depend on demand, transaction composition and the final mainnet configuration. The Hoodi announcement does not promise a particular percentage reduction in transaction costs.
Two changes reshape how Ethereum handles blocks
Glamsterdam combines the Amsterdam execution-layer upgrade with the Gloas consensus-layer upgrade. Its principal changes address both block production and the information clients use to process transactions.
Enshrined proposer-builder separation, or ePBS, brings a separation between block-building and proposing responsibilities into the protocol. Ethereum’s roadmap describes this as part of an effort to give the network more room to propagate and validate larger workloads.
Block-level access lists, or BALs, record information about the state accessed during block execution. That information supports efforts to process work more efficiently, including parallel execution where dependencies permit it.
The practical objective is greater capacity that clients can handle reliably. Raising a limit is useful only if the supporting software and network can accommodate the resulting workload.
This fits the broader development direction explored in Bitnxt’s report on Ethereum’s shift toward cryptographic verification.
Sepolia has already exposed changes for data infrastructure
The earlier testnet deployment offers a concrete example of the work surrounding a protocol upgrade.
In an October 8 technical report, ethPandaOps explained that ePBS separates the consensus block and execution payload. Its monitoring infrastructure consequently needed changes to how execution information was collected and stored.
The team reported adding 25 raw data tables to its Xatu system for Glamsterdam, compared with three for Fusaka. Those tables capture information including builder bids, payload availability and block access lists.
That is an infrastructure change with practical consequences. Explorers, analytics services and other applications must read the correct data after the fork; assumptions that worked before it may no longer hold.
What operators and application teams should prepare
Hoodi node operators need compatible versions of both execution and consensus clients before activation. The Foundation says supported releases will be added to its client tables as they are confirmed. Operators should check those tables directly rather than rely on a version list copied into an older article.
Application teams have a different task: checking whether wallets, indexers and gas estimators behave correctly under the new rules.
The Foundation’s earlier Platåberget announcement specifically warned that tools relying on hardcoded maximum gas limits would need updating. That makes testnet preparation relevant beyond validators alone.
Ordinary ETH holders have no migration step
The Hoodi fork does not require mainnet ETH holders to transfer funds or exchange their tokens.
Ethereum’s upgrade guidance explicitly warns against messages instructing users to “upgrade” their ETH. Protocol changes are implemented through network software; holders should not interpret an upgrade announcement as a request to connect a wallet to an unfamiliar migration website.
Bitnxt’s coverage of Vitalik Buterin’s warning against rushed wallet migrations explains why unnecessary transfers can introduce operational risk.
For readers reviewing their existing setup, our hot-wallet versus cold-wallet guide covers storage, signing and recovery responsibilities.
Bitnxt View: Reliability will determine the value of extra capacity
The 200 million figure is the headline. The more consequential evidence will come from how clients perform around activation and under demanding workloads.
For Bitnxt, a useful assessment will look at block propagation, validation behaviour, resource requirements and whether supporting tools continue operating correctly. Those observations will help establish how the design performs outside specifications and development environments.
Hoodi gives the ecosystem a scheduled opportunity to gather that evidence. Mainnet readiness remains a separate decision.
