From 60M To 200M Gas: How Ethereum’s Glamsterdam Fork Tests The Limits Of Block Capacity And Decentralized Coordination
In Brief
Ethereum’s Glamsterdam upgrade activated on Sepolia, stress-testing a 200 million gas limit through a coordinated, opt-in model. The experiment probes block capacity, validator workload, and the path to mainnet scaling.
On October 6, 2026, Ethereum reached one of the more consequential milestones in its recent scaling roadmap. At approximately 13:53 UTC, the network’s Sepolia testnet activated the Glamsterdam upgrade — and in doing so, it began an experiment that could eventually redefine how much work a single Ethereum block can contain.
The fork did not go entirely to plan, however. In the hours leading up to activation, developers with the Prysm client — one of the most widely used pieces of software for running Ethereum validators — were forced to issue an emergency update. Version 7.2.1 was released late on October 5 to ensure that validators would automatically propose blocks with a 200 million gas limit during the Glamsterdam test. Without it, validators running Prysm would have continued producing blocks capped at the older 60 million gas default, quietly diluting the very test designed to measure how the network handles larger blocks.
The distinction between a default and a choice matters here, and it reveals something important about how Ethereum actually governs itself. Technically, the 200 million gas figure is not a protocol mandate imposed at the fork. Rather, it is a configurable preference that validators can adopt — or decline — after activation. Prysm validators can enable the higher limit through updated proposer settings or the keymanager API, while Teku users must set a specific flag, with the older suggested-gas-limit option rendered ineffective after the transition. Sepolia’s eventual gas ceiling will therefore depend on how many validators opt in and how the limit evolves from there.
This opt-in architecture is a deliberate design philosophy, not an accident. Ethereum does not push capacity increases through a centrally enforced switch; it arrives through coordinated operator choices and client defaults. Glamsterdam’s activation on Sepolia, set at epoch 353,024 and slot 11,296,768, marks the first full rehearsal of that coordination mechanism at a scale three times larger than the network’s previous default.
The Technical Package Behind the Number
For the broader crypto audience, the headline number is easy to misread. A higher gas limit means more room for transactions, stablecoin transfers, and complex applications within each block — a meaningful step toward relieving congestion on the world’s largest smart-contract platform. But Glamsterdam’s real significance lies less in the number itself and more in the technical package wrapped around it.
The upgrade combines the Amsterdam execution-layer changes with Gloas at the consensus layer, and its centerpiece is enshrined proposer-builder separation — a structural redesign of how blocks are constructed and proposed. Alongside it, block-level access lists record which accounts and storage locations a block touches, allowing clients to read state and validate transactions in parallel. Gas accounting is also being refined: EIP-8037 raises and separately meters the cost of creating new state, EIP-8038 updates state-access costs, and the package removes gas refunds from block accounting while eliminating the SELFDESTRUCT burn. The cumulative effect is an effort to use existing capacity more efficiently, not simply to pack more work into every block.
What the Test Does Not Promise
Equally important is what the test does not promise. A larger gas limit does not make block times faster. It does not automatically make transactions cheaper — fees still rise and fall with demand, and no usage figures or measured Layer 2 effects are yet attached to the 200 million target. And it does not grant any single transaction unlimited room: EIP-7825 imposes a protocol-level cap of 16,777,216 gas per individual transaction regardless of the block limit. The increase creates room for more aggregate activity, not permission for one operation to consume an entire block.
There are also known risks baked into the experiment. A previous roadmap marker, EIP-7935, identified 150 million gas as a threshold of potential concern, since the worst-case block size at that level would approach the consensus layer’s gossip limit — the boundary beyond which blocks may propagate too slowly across the network. Ethereum is, in effect, deliberately probing that boundary to learn where validation costs, propagation delays, and hardware requirements for node operators begin to outweigh the benefits of extra capacity.
A companion proposal, EIP-8261, offers a longer-term answer to the coordination problem. Still in peer review, it introduces an optional machine-readable gas limit schedule that validators could adopt at specified epochs — replacing the current system, in which new defaults take effect only whenever operators happen to update their software. Notably, the proposal does not change consensus rules; blocks above or below the scheduled value would remain valid. It simply gives validators a shared target to aim at, preserving the network’s decentralized character while enabling a more deliberate, network-wide evolution.
For users and builders, the honest conclusion today is narrower than the headlines suggest. Glamsterdam on Sepolia does not confirm a 200 million gas limit for Ethereum’s mainnet — neither an activation date nor a mainnet gas target has been decided, with the Hoodi testnet and mainnet timelines still undetermined. What it does confirm is a working method: supported client releases from Grandine, Lighthouse, Lodestar, Nimbus, Prysm, and Teku, an active bug bounty on the specifications, and a live environment in which the consequences of much larger blocks can be observed rather than theorized.
The next weeks of Sepolia data will determine whether the experiment succeeds. Developers will be watching block production consistency, validation latency, and whether validators adopt the higher limit at all. If the network proves it can handle blocks more than three times its previous default without compromising decentralization, the case for a gradual, opt-in capacity expansion on mainnet becomes considerably stronger. Ethereum’s scaling debate has always been a negotiation between ambition and pragmatism. Today, that negotiation is finally running on real blocks.
Disclaimer
In line with the Trust Project guidelines, please note that the information provided on this page is not intended to be and should not be interpreted as legal, tax, investment, financial, or any other form of advice. It is important to only invest what you can afford to lose and to seek independent financial advice if you have any doubts. For further information, we suggest referring to the terms and conditions as well as the help and support pages provided by the issuer or advertiser. MetaversePost is committed to accurate, unbiased reporting, but market conditions are subject to change without notice.
About The Author
Alisa, a dedicated journalist at the MPost, specializes in crypto, AI, investments, and the expansive realm of Web3. With a keen eye for emerging trends and technologies, she delivers comprehensive coverage to inform and engage readers in the ever-evolving landscape of digital finance.
More articles
Alisa, a dedicated journalist at the MPost, specializes in crypto, AI, investments, and the expansive realm of Web3. With a keen eye for emerging trends and technologies, she delivers comprehensive coverage to inform and engage readers in the ever-evolving landscape of digital finance.
