Ethereum’s Glamsterdam upgrade narrows focus on scaling
Ethereum’s next major upgrade, Glamsterdam, is taking shape around a higher gas limit and changes designed to support more throughput, even as the network’s user growth metrics remain mixed. The upgrade package centers on EIP-8037, which would raise the cost of new state creation to help prevent state bloat while Ethereum expands capacity [1][3]. The timing matters because Ethereum is still trying to balance faster execution on layer 1 with limits on storage growth and validator burden.
Overview
- Glamsterdam’s target includes a 200 million gas cap, about 3.3 times the current roughly 60 million baseline, which would materially expand Ethereum’s processing capacity [1].
- EIP-8037 would increase the cost of state creation, aiming to keep state growth closer to a target of 100 GiB a year at a 96 million gas reference point [3].
- The upgrade also folds in changes around ePBS, which are intended to improve block-building stability and give execution clients more flexibility [1].
- Developers are testing multi-client devnets for Glamsterdam, indicating the upgrade is already moving beyond concept into implementation work [1].
- The trade-off is clear: more throughput can improve network capacity, but higher state costs may raise the bar for contract deployment and storage-heavy activity [3].
Subscribe to our Social Media for Exclusive Crypto News and Insights 24/7!
Glamsterdam centers on EIP-8037 and higher throughput
Ethereum’s Glamsterdam work is being framed as a scaling upgrade, not a user-growth event. The key piece in the current package is EIP-8037, a draft standards-track proposal that raises the gas cost of state creation to limit excessive state growth while allowing block gas limits to rise [3]. In practical terms, that means the network is trying to make room for more activity without letting storage costs spiral out of control.
The proposal introduces a separate cost-per-state-byte model and a more harmonized way to meter state creation across contract deployment and storage [3]. That matters for market participants because state-heavy activity becomes more expensive relative to lighter transaction flow, which can influence where developers and applications choose to build.
| Item | Verified data | Direct implication |
|---|---|---|
| Current gas baseline | ~60 million | Room for a materially larger block gas target remains available [1] |
| Glamsterdam gas goal | 200 million | Ethereum could handle much higher throughput if the change is adopted [1] |
| EIP-8037 reference point | 96 million gas | State growth controls are being tied to a higher-capacity network design [3] |
| State growth target | 100 GiB per year | The upgrade is intended to limit database expansion as activity rises [3] |
Why the upgrade matters for market structure
Market participants view Glamsterdam as a capacity upgrade with direct implications for network economics. Higher throughput can reduce congestion pressure, while a tighter state-cost framework can make Ethereum more expensive for applications that rely on persistent on-chain storage [1][3]. That combination supports scaling, but it also changes the cost profile for builders.
Analysts note that this kind of upgrade tends to shift demand toward applications that can operate efficiently within the new cost structure. Interpretation based on available data: if state creation becomes meaningfully more expensive, the relative advantage may move toward lighter-weight contracts and away from designs that rely on large or frequent state expansion [3]. The benefit is broader network headroom; the risk is that some deployment patterns become less economical.
EIP-8037 reflects a narrower objective than user growth
The available data points to a development process focused on infrastructure capacity rather than near-term user acceleration. Multi-client Glamsterdam devnets are already active, and builder pipelines are being evaluated across major clients, which suggests the project is centered on technical readiness [1]. That is consistent with a network preparing for more load, not necessarily a network already seeing it from end users.
The limitation is that higher theoretical capacity does not guarantee stronger activity. If transaction demand remains subdued, the upgrade may improve optionality more than immediate usage. That distinction matters for investors because infrastructure improvements can support valuation narratives, but they do not automatically translate into higher throughput utilization or stickier demand.
| Upgrade component | Status / direction | Likely effect |
|---|---|---|
| EIP-8037 | Draft standards track | Higher state-creation costs, lower storage growth pressure [3] |
| ePBS-related changes | In development and being stabilized | More flexible block-building and improved client handling [1] |
| Gas cap target | 200 million | Larger blocks and greater potential throughput [1] |
The key risk is adoption, not design
The main upside scenario is straightforward. If Glamsterdam lands as designed, Ethereum gets more room to scale on layer 1 while keeping long-term storage growth under control [1][3]. That would strengthen Ethereum’s competitive position against chains that already emphasize low-cost throughput.
The downside is equally clear. Higher gas limits can widen capacity, but they can also make operational demands heavier for validators and clients if implementation lags or if the state-growth guardrails prove too restrictive [1][3]. There is also uncertainty around timing. The upgrade is active in development networks, but that does not mean final parameters are settled or that adoption will be smooth across clients.
For now, Glamsterdam reads as a deliberate move to prioritize network capacity and sustainability over short-term user-growth optics. The most important question is not whether Ethereum wants more activity, but whether it can expand throughput without making the system harder and more expensive to run.
