Ethereum’s Glamsterdam upgrade packages throughput, block-building, and state-pricing changes that could reframe how users, rollups, and builders experience L1 blockspace. With mainnet timing widely discussed for Q3 2026, the question isn’t just “Will gas get cheaper?”—it’s whether cheaper, bigger blocks can also grow total fee demand.
This piece explains what’s shipping, how the roadmap targets both capacity and stability, and what it may mean for ETH fees, burn dynamics, and Layer 2 economics. You’ll find a clear summary, comparison points, and a practical checklist for dapps and rollups preparing for the transition.
Where relevant, we cite primary materials from Ethereum’s roadmap and active devnet notes to triangulate expectations and timelines.
Glamsterdam is designed to expand capacity and stabilize block-building, which could lower typical L1 transaction costs and improve inclusion for complex flows. That doesn’t automatically mean lower total ETH fees: aggregate demand depends on usage, MEV dynamics, and how rollups adapt. If bigger blocks and better builder separation unlock new activity, fee demand could broaden—even as per-transaction prices fall for many use cases.
- ePBS extends the data propagation window to about 9 seconds, a key enabler of larger blocks and parallel execution potential (ethereum.org (Glamsterdam)).
- Roadmap materials outline a post-upgrade gas-limit floor target near 200M gas per block, versus ~60M today, with 150M being used in testing while state pricing is tuned via EIP-8037 (ethereum.org (Glamsterdam)).
- Recent explainers place mainnet in Q3 2026 and discuss potential L1 fee reductions in the high-60% to high-70% range for some transactions (IG (investor explainer), June 16, 2026).
- Active devnet work in early–mid June 2026 underscores that tuning and calibration are in flight (ethpandaops).
What does Glamsterdam actually change under the hood?
The core of Glamsterdam is enshrined proposer-builder separation (ePBS, EIP-7732), which formalizes the split between validators who propose blocks and specialized builders who assemble block payloads. A prominent detail: ePBS increases the data propagation window from roughly two seconds to about nine seconds—critical headroom for larger payloads and more parallelized execution without choking the network’s ability to disseminate blocks (ethereum.org (Glamsterdam)).
Alongside that, the roadmap signals a post-upgrade block gas-limit floor target around 200 million gas—around 3.33× the current ~60M baseline—while client teams calibrate state-pricing parameters using a ~150M reference limit during testing. EIP-8037 is discussed as the lever to keep state growth near a controlled trajectory (the materials cite a target around 120 GiB per year), so storage-heavy applications feel a more accurate cost of state bloat (ethereum.org (Glamsterdam)).
On cadence, public devnet notes show a rapid iteration cycle: glamsterdam-devnet-5 targeted or ran around 4 June 2026 and devnet-6 was slated for mid-June, reinforcing that the engineering process is actively validating block-building, propagation, and pricing interactions in early–mid June (ethpandaops).
Big picture, these pieces aim to safely scale L1 throughput while containing long-term state growth, a tension that has tripped many high-throughput chains. If the parameters land well, capacity rises and gas markets clear more efficiently without compromising decentralization or validator diversity.
How much could L1 fees drop—and for whom?
Market commentary over the last month points to a base case of Q3 2026 for mainnet—often framed as end-August—alongside broad estimates that some L1 transaction types could see fee reductions from the high-60% to high-70% range once capacity expands and state pricing bites appropriately. These are directional estimates, not guarantees, and actual outcomes will vary by transaction complexity, priority, and congestion (IG (investor explainer), June 16, 2026).
Ethereum’s own materials underscore the mechanics behind these expectations: a longer propagation window and a targeted 200M gas floor are enablers for larger blocks, which—in normal conditions—should lower the clearing price for many transactions. In parallel, developers are testing around a 150M reference gas limit while they dial in EIP-8037’s state-pricing parameters to curb excess state growth (ethereum.org (Glamsterdam)).
That said, gas is a market. During peak demand (e.g., hot NFT mints, L2 settlement spikes, or intense MEV competition), users can still bid up inclusion. Glamsterdam reduces structural frictions; it doesn’t suspend supply-and-demand dynamics.
| Dimension | Pre-Glamsterdam (today) | Post-Glamsterdam (expected) |
|---|---|---|
| Block gas baseline | ~60M gas baseline | Targeted floor ~200M gas; ~150M used in testing |
| Block propagation window | ~2 seconds | ~9 seconds with ePBS |
| Execution room | Constrained payloads | Larger payload headroom; potential for more parallel execution |
| State growth policy | Existing pricing | EIP-8037 calibration to control state expansion |
| Typical L1 user fees | Variable, often spiky | May fall materially in normal conditions; still market-driven |
Could cheaper blockspace hurt or help ETH fee demand?
There are two moving pieces: price per transaction and total volume. Glamsterdam should push many L1 transactions down the supply curve, but if that catalyzes new dapps, more L2 settlements, or richer onchain activity, aggregate fee volume could expand. Markets often confuse “lower fees” with “lower revenue,” when a well-calibrated capacity increase can increase throughput and attract new demand.
Ethereum’s EIP-1559 burn mechanics also matter. Base fees on execution gas are burned; tips go to validators. For data availability, post-EIP-4844 blobs use a separate 1559-style market where the base component is similarly designed to be burned. If Glamsterdam reduces friction for rollups and complex L1 flows, total burned ETH could depend on the mix of execution versus blob usage and the cadence of high-demand periods.
Finally, ePBS could influence MEV distribution. Stronger separation and more predictable block-building may temper certain extraction patterns while opening new ones. The net effect on fee demand likely depends on how builder markets equilibrate and whether new orderflow products (e.g., preconfirmations) expand participation without raising censorship risks.
Pro tip: Watch a blend of metrics—not just average gas—such as daily burned ETH, blob base fee levels, builder tip share, and inclusion latency during peak hours. Those paint a better picture of fee demand health than any single gas snapshot.
What should rollups and dapp teams do before mainnet?
Glamsterdam is not a “flip a switch and forget it” event. Teams that depend on predictable inclusion—bridges, perps, NFT mints, MEV-sensitive flows—should rehearse their operations against higher block gas limits and revised state pricing before mainnet. Devnets spinning through early and mid-June signal that parameters are still being tuned; treat estimates as directional, not final (ethpandaops).
- Simulate with a 150M gas environment and stress-test batching logic; validate that oracles and gas estimators stay accurate at higher throughput (ethereum.org (Glamsterdam)).
- Re-evaluate storage-heavy designs under EIP-8037 assumptions; expect more precise costs for state growth.
- Update inclusion policies for preconfirmations and fallbacks; align user-facing SLAs with potential changes in latency variance.
- Benchmark bridge and settlement schedules against larger blocks; verify that fraud/validity windows and liquidity buffers still fit.
- Audit networking assumptions: a longer propagation window reduces orphan risk for big blocks, but edge connectivity still matters for builders and relays.
Communication is underrated. Wallets and exchanges should prime users that fees may trend lower on average but still spike during bursts of activity—and that gas-saving behaviors (batching, off-peak execution, L2 usage) remain relevant.
How might ePBS change builder, wallet, and MEV dynamics?
By enshrining the separation of proposers and builders, Ethereum narrows the scope for validators to vertically integrate extraction while inviting broader competition among builders. The nine-second propagation window offers more time for builders to assemble heavy blocks without jammed networking, potentially reducing orphan rates for large payloads (ethereum.org (Glamsterdam)).
For wallets and orderflow originators, this environment can support healthier markets for preconfirmations and transaction quality guarantees—if implemented carefully to avoid soft-censorship pressure. Builders may differentiate on latency, privacy guarantees, and failure modes. Monitoring concentration will be critical; centralization can erode credible neutrality and reintroduce tail risks when a dominant builder falters.
MEV isn’t “fixed” by ePBS, but the rails for managing it become more consistent. Expect policy conversations to continue around inclusion lists, backrunning norms, and user protections, especially for retail orderflow and stablecoin transfers that suffer most during surges.
Does Glamsterdam close the gap with high-throughput L1s?
Competing L1s emphasize monolithic throughput and low latency, while Ethereum leans modular: a resilient L1 plus a thick layer of rollups. Glamsterdam aims to improve L1 capacity meaningfully (with a gas-floor target around 200M and longer propagation) without overburdening node operators, thanks to state-pricing and careful calibration (ethereum.org (Glamsterdam)).
The comparison isn’t binary. Many developers prize Ethereum’s security model, liquidity, tooling, and L2 optionality. Alternative chains still offer compelling UX for specific apps, and some match bursts of demand with very low fees. If Glamsterdam’s throughput gains land as planned, the cost/performance gap for everyday flows could narrow while Ethereum preserves decentralization properties that enterprises and regulators watch closely.
For builders, the practical question is opportunity cost: where can your app achieve the best mix of cost, speed, and distribution? Post-Glamsterdam, Ethereum’s answer might be “more often than today”—but teams should test workloads on several environments before committing.
Common Mistakes
- Assuming fees will only fall. In reality, a cheaper baseline can coexist with sharp spikes. Avoid hardcoding gas expectations; keep dynamic caps and user prompts.
- Ignoring state costs. If your design leans on permanent storage, model EIP-8037 sensitivity and plan pruning or compression to avoid runaway costs.
- Overlooking builder centralization risk. ePBS helps, but builder markets can still concentrate. Maintain multi-builder connectivity and fallback paths.
- Skipping devnet rehearsals. Parameter changes are being tuned in June; test with 150M reference conditions and verify estimator accuracy before mainnet.
- Equating lower L1 fees with lower burn. Track volume, blob usage, and MEV tips; the mix drives total fee demand and burned ETH, not price alone.
For ongoing coverage, analysis, and practical explainers as Glamsterdam firms up, visit Crypto Daily.
Frequently Asked Questions
Will existing smart contracts need changes for Glamsterdam?
Most contracts won’t require code changes. The bigger shifts are network-level: block assembly via ePBS, more capacity, and tuned state pricing. Still, contracts that assume tight gas ceilings or rely on timestamp/latency quirks should be audited against larger-block dynamics.
Do node operators need different hardware?
Expect slightly higher resource pressure from larger blocks and a longer propagation window. Ethereum’s roadmap targets sustainable growth, but operators should review client guidance as mainnet parameters finalize and ensure healthy bandwidth and disk headroom.
How should rollups update their fee oracles?
Plan to re-fit oracles to new L1 cost surfaces, including execution gas and blob markets. Measure over several weeks post-upgrade; don’t recalibrate on day one. Include guardrails for congestion pockets and backpressure during hot dapp cycles.
What if Glamsterdam slips past Q3 2026?
Timelines can shift as engineering feedback arrives. Recent explainers set expectations around Q3 2026, but shipping securely is the priority (IG (investor explainer), June 16, 2026). Treat integration plans as contingent and avoid over-committing to specific dates.
Does ePBS eliminate MEV?
No. ePBS structures competition among builders and reduces certain validator-level risks. MEV remains, though its distribution and user experience may improve as markets standardize preconfirmations and inclusion practices.
Will NFTs and memecoins minting frenzies still clog the network?
They can still create surges, but a larger block budget should reduce the severity of congestion in typical bursts. Pricing remains market-driven, so hot mints can still push fees higher, just from a lower baseline.
How can I track whether fee demand is actually improving?
Monitor daily burned ETH, blob base fee averages, builder tip share, L1-to-L2 settlement volumes, and median inclusion latency. Together, they signal whether cheaper blockspace is translating into broader onchain activity.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.