Ethereum’s Glamsterdam upgrade eyed

Ethereum’s next big protocol fight is not about wallets or staking tweaks. It’s about raw base-layer throughput — how much activity Ethereum itself can handle before it gets too expensive, too slow, or too heavy for ordinary nodes to run. That’s where Glamsterdam comes in. Over the past week, more than 100 core contributors met in Svalbard to push the upgrade from roadmap talk toward something that actually looks shippable. (blog.ethereum.org) ### What is Glamsterdam, exactly? Glamsterdam is Ethereum’s planned H1 2026 network upgrade. It sits after Pectra and Fusaka, and the whole point is to clear the path for much bigger L1 scaling — not by one magic trick, but by changing how blocks are built, how data dependencies are exposed, and how state growth gets priced. Basically, Ethereum wants more throughput without quietly making home-node operation impossible. (ethereum.org) ### Why is Ethereum still chasing L1 scaling? Because rollups helped, but they did not make the base layer irrelevant. Ethereum still needs the chain underneath to be cheaper, faster, and more predictable if it wants to support more on-chain activity directly and support the rest of the stack cleanly. The catch is that raising capacity the dumb way — just cranking gas limits — can bloat state and push hardw(ethereum.org)dam is trying to manage. (ethereum.org) ### What actually changed this week? The concrete news is from the Soldøgn interop in Longyearbyen, posted May 2. By the end of that week, developers said they had aligned on three things: a post-Glamsterdam gas-limit floor of 200M, stable enshrined proposer-builder separation implementations running with external builders, and final EIP-8037 repricing numbers. That is not the same as “upgrade finalized,” but it is much more specific than vague roadmap optimism. (blog.ethereum.org) ### Why does 200M matter so much? Because Ethereum’s mainnet gas limit was 60M as of the February protocol-priorities update. So a 200M floor would imply more than a 3x jump from that level after the upgrade. That is the number people latch onto when they talk about Glamsterdam as a throughput story. But the important part is not just the headline multiple — it’s that core devs are trying to anchor that target in client benchmarking rather than wishful thinking. (blog.ethereum.org) ### What are the key ingredients? Two scheduled headliners already stand out in the Glamsterdam meta-EIP: EIP-7732 for enshrined proposer-builder separation, and EIP-7928 for block-level access lists. ePBS gives the protocol a cleaner split between block building and proposing, which buys more timing headroom inside a slot. Block-level access lists are meant to expose data de(blog.ethereum.org)cess. Think of it like labeling the boxes in a warehouse before trying to move three aisles at once. (eips.ethereum.org) ### Where do repricings fit in? They are the unglamorous part that makes the glamorous part safer. EIP-8037 raises the cost of creating new state, and other repricing proposals try to make gas costs reflect real resource usage under higher throughput. Without that, a higher gas limit could just mean faster state growth and worse long-run node performance. So the scaling story is really two stories glued (eips.ethereum.org)t capacity consumes. (blog.ethereum.org) ### Is the timeline locked? Not really. Ethereum.org says H1 2026, and back in December an All Core Devs note floated June 24, 2026 as a hypothetical mainnet target for illustration, not a commitment. Another Ethereum Foundation update in April said Glamsterdam was proving trickier and slower-going than expected. So June is plausible, but “eyed” is the right word here — not “set.” (et([blog.ethereum.org)dam matters because Ethereum has finished the easier near-term upgrades and is now moving into the harder base-layer scaling work. The Svalbard interop gave that effort real shape — especially the 200M gas-limit floor target. But this is still an engineering story first, not a done deal. If Ethereum lands it, the network gets a much stronger case that L1 scaling is no longer theoretical. (blog.ethereum.org)