Ethereum Glamsterdam Upgrade Moves Toward 200M Gas Limit Roadmap
TL;DR
Ethereum’s Glamsterdam upgrade work is moving through devnet planning ahead of a projected H2 2026 mainnet window.
EIP-7732, or enshrined proposer-builder separation, is one of the key pieces being tracked by developers.
EIP-7928, covering block-level access lists, is another major component tied to parallel execution and higher throughput.
The headline target is a path toward a much higher gas limit, but the exact mainnet package remains subject to Ethereum’s normal testing and governance process.
Glamsterdam Moves Into Focus
Ethereum’s next major upgrade cycle is now turning toward Glamsterdam, a protocol package expected to define the network’s post-Pectra scaling and block-production roadmap. The upgrade is being watched closely because it touches two of Ethereum’s biggest long-running constraints: who builds blocks, and how much execution capacity the base layer can safely support.
Developer materials and EIP discussions point to enshrined proposer-builder separation and block-level access lists as two of the most important items in the Glamsterdam conversation. Together, they help frame a longer-term path toward higher throughput without simply asking every node operator to absorb more load without structural changes.
What ePBS Tries To Fix
EIP-7732, commonly described as enshrined proposer-builder separation, would move part of the current external block-building market into Ethereum’s protocol design. Today, block construction often depends on external relay infrastructure and specialized actors. That system has helped the network manage maximum extractable value, but it has also raised concerns about centralization and censorship pressure.
By bringing proposer-builder separation closer to the protocol layer, Ethereum developers are trying to reduce reliance on off-protocol arrangements and create a cleaner separation between validators proposing blocks and builders assembling them. It is a technical change, but it also speaks directly to Ethereum’s decentralization goals.
Why Block-Level Access Lists Matter
EIP-7928, covering block-level access lists, is aimed at making execution more predictable by identifying state access patterns at the block level. In plain English, validators and clients could get better information about what a block needs to touch before processing it. That matters because parallel execution is difficult when the system does not know which transactions are likely to conflict.
If block-level access lists work as intended, they could help Ethereum process more activity without turning every block into a heavier, less predictable burden for nodes. That is why the proposal is often discussed alongside higher gas-limit targets and broader L1 scaling.
A 200M Gas Limit Is The Big Headline
The most attention-grabbing part of the Glamsterdam narrative is the potential path toward a 200 million gas limit. That would be a major increase from today’s base-layer capacity and would represent a very different Ethereum L1 if it can be achieved safely. But the wording matters: this is a roadmap and testing target, not a guarantee that every detail is locked for mainnet exactly as discussed in current devnet materials.
Ethereum upgrades usually move through a long process of specification, client implementation, devnets, testnets and final coordination. That process is slow by design. Glamsterdam is important because it shows the network is still trying to scale the base layer itself, not only pushing activity to rollups. The risk is that aggressive capacity increases without careful client and node work could weaken the decentralization properties Ethereum is trying to protect.
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information from Ethereum EIP specifications. at Ethereum EIP specifications
