Ethereum’s Glamsterdam rehearsal clears a key test before Sepolia deployment
A client benchmark processed Glamsterdam’s new block-building rules successfully, but the 200 million gas setting remains a test value rather than a mainnet commitment.
Ethereum’s upcoming Glamsterdam upgrade cleared another development milestone this week after a Nethermind performance run processed blocks using the upgrade’s new block-building rules, CoinDesk reported Thursday. The client completed 2,302 tests while processing 570.7 billion gas in three minutes and 15 seconds, according to the report.
The benchmark is encouraging because it exercised block-level access lists, which let execution clients identify the accounts and storage slots a block will touch before processing begins. That advance notice is intended to make more parallel work possible. But the test measured Nethermind’s execution software in a controlled environment, not the performance of the entire Ethereum network.
The distinction matters. A devnet result is not a mainnet guarantee. Client interoperability, validator propagation, application compatibility and real-world hardware constraints still need to be tested before any production activation.
Why the gas-limit experiment matters
During the rehearsal, the test environment raised its block gas limit from 60 million to 200 million. Gas is a measure of computational work, so a higher limit creates room for more transactions, swaps and contract calls in each block. If the network can safely process larger blocks, users could face fewer fee spikes during periods of heavy demand.
Larger blocks also increase the burden on nodes. Operators must receive, execute and validate more data within the time available to keep the chain synchronized. Glamsterdam’s design pairs higher capacity with changes to block construction and data propagation, including a longer window for validators to receive and check blocks.
Ethereum’s official roadmap still lists Glamsterdam as being tested on devnets, with a Sepolia fork targeted for October 6 and mainnet expected in the fourth quarter of 2026 without a confirmed date. Dates and scope can change as client teams find new edge cases.
The next evidence is multi-client stability
A single client’s clean run is only one part of the upgrade process. Ethereum depends on multiple execution and consensus clients, plus wallets, indexers, RPC providers and applications that may rely on old gas assumptions. The Foundation has previously warned developers that Glamsterdam’s repricing changes can affect a small set of contracts and tools.
The proposed Sepolia deployment will be a more consequential checkpoint because it exposes the upgrade to a public testnet and a wider range of software. Developers can test transaction estimation, contract execution, block explorers and validator operations before the mainnet decision.
Readers should watch for the formal Sepolia fork announcement, client release notes, incident reports and evidence that multiple clients remain synchronized under the new rules. More capacity is useful only if decentralization holds. The current rehearsal supports continued testing; it does not establish final throughput, lower fees or a guaranteed activation date.
