Ethereum’s Glamsterdam Upgrade Will Reprice State Operations: What Developers and Users Need to Know

Ethereum’s upcoming Glamsterdam upgrade is expected to introduce an important change that may not be immediately visible to everyday users, but could matter a great deal for smart contract developers and infrastructure teams: a new Gas pricing model for state-related operations.

The Ethereum Foundation team has published an impact assessment for two proposed changes, EIP-8037 and EIP-8038, both designed to make Ethereum Gas costs better reflect the real computational and storage burden of interacting with the network’s growing state. In practical terms, the upgrade aims to charge more accurately for operations such as creating new accounts, writing new storage slots, deploying bytecode, reading contract storage, and accessing cold accounts.

For most users, this will not require any action. Wallets, RPC providers, block builders, and application frontends are expected to update fee estimation and transaction handling automatically. However, a small number of contracts that rely on hardcoded Gas assumptions may need to be reviewed and fixed before Glamsterdam goes live.

Why Ethereum Is Repricing State Operations Now

Ethereum’s “state” refers to the live database that full nodes must maintain: account balances, contract code, storage values, nonces, and other data required to validate the chain. As DeFi, stablecoins, NFTs, L2 settlement, restaking, and on-chain infrastructure have expanded, this state has grown substantially.

The issue is not only storage size. State access also affects performance. When nodes process transactions, they must read and write state data efficiently. If Gas prices underestimate the real cost of these operations, the network can become exposed to throughput bottlenecks, especially as the Gas limit rises.

Ethereum last made a major adjustment to state access pricing during the Berlin upgrade in 2021, which introduced changes such as access lists and cold/warm access distinctions through proposals including EIP-2929 and EIP-2930. Since then, Ethereum’s usage profile has changed considerably. The recent increase in Gas limits has further raised the urgency of making state growth sustainable.

Glamsterdam’s Gas repricing is therefore not just a fee adjustment. It is part of Ethereum’s broader roadmap to support higher throughput while keeping node operation viable.

What EIP-8037 and EIP-8038 Change

The Glamsterdam assessment focuses on two proposals:

• EIP-8037: reprices the creation of new state, including new accounts, new storage slots, and deployed bytecode.
• EIP-8038: increases costs for state access operations such as SSTORE, SLOAD, and cold account access.

The core idea is straightforward: operations that place a heavier burden on Ethereum nodes should carry a Gas cost closer to their actual resource usage.

This is especially relevant for contracts that create many storage slots, deploy many contracts, or perform large numbers of cold reads and writes. These patterns are common in certain DeFi protocols, smart contract factories, NFT minting systems, account abstraction infrastructure, and complex on-chain games.

The Goal: Preparing Ethereum for Higher Throughput

A key point in the assessment is that the new pricing is calibrated around a performance target that could support roughly three times the baseline throughput. This does not mean Glamsterdam alone triples Ethereum’s capacity overnight. Instead, the repricing is a prerequisite for safely raising the Gas limit in the future.

Ethereum scaling in 2025 is increasingly multi-layered. Rollups continue to handle a large share of user activity, while Ethereum mainnet remains the settlement, liquidity, and security layer. As blob-based scaling evolves after EIP-4844, mainnet execution efficiency still matters. If L1 state operations remain underpriced, higher throughput could push more burden onto node operators and weaken decentralization.

In other words, Glamsterdam’s repricing is a defensive upgrade as much as a scaling upgrade. It attempts to preserve Ethereum’s ability to grow without making the network too expensive or difficult to validate.

How the Impact Was Evaluated

To estimate real-world consequences, Ethereum researchers replayed historical mainnet transactions under the proposed Gas schedule. This method helps identify which transactions would behave differently if the new pricing rules were applied.

The results were grouped into four broad categories:

1. Transactions that are unaffected
   Most historical transactions fall into this group. They either do not rely heavily on the repriced operations or already include enough Gas margin.

2. Transactions that still succeed but consume different amounts of Gas
   Some transactions remain valid, but their Gas usage or execution details change. This is expected when pricing rules are updated.

3. Transactions that run out of Gas under the original limit but succeed with a higher limit
   These transactions are not fundamentally broken. They simply need more Gas under the new pricing model.

4. Transactions that may still fail even with a much higher Gas limit
   This is the smallest but most important category. These failures often point to contracts that assume specific Gas costs inside their logic.

The last category is where developers should focus. If a contract uses fixed Gas assumptions for low-level calls, fallback behavior, proxy patterns, or execution branching, it may behave unexpectedly when the Gas schedule changes.

Why Hardcoded Gas Assumptions Are Risky

Smart contracts should ideally avoid depending on exact Gas prices for specific opcodes. Ethereum has changed Gas costs before, and it may do so again as the protocol evolves. A contract that assumes a certain operation will always cost the same can become fragile.

Common risk areas include:

• low-level calls with fixed Gas stipends;
• fallback or receive functions that depend on tight Gas margins;
• proxy or factory contracts that allocate Gas manually;
• contracts that use Gas left checks for control flow;
• batch execution systems that estimate internal execution too aggressively;
• legacy contracts written before Berlin-style cold and warm access pricing.

This does not mean all such contracts will fail. Many will continue to work normally. But Glamsterdam is a reminder that Gas should be treated as a protocol variable, not a permanent constant.

Developers can review the Ethereum Improvement Proposal repository for the latest specification details and monitor client implementation discussions through the Ethereum EIPs GitHub repository.

What Developers Should Do Before Glamsterdam

For smart contract teams, the best response is proactive testing rather than waiting for mainnet activation. A practical checklist includes:

1. Audit Gas-Sensitive Logic

Review any code that uses:

• gasleft();
• low-level .call{gas: ...}();
• fixed execution buffers;
• custom relayer or bundler Gas accounting;
• fallback functions that assume minimal execution cost;
• factory deployments with tightly constrained Gas limits.

If the contract’s correctness depends on exact Gas behavior, it deserves closer inspection.

2. Re-Test Deployment and Batch Operations

Contracts that deploy other contracts or write many new storage slots are more likely to see higher costs under EIP-8037. Batch mints, vault creation, account deployment, bridge operations, and registry updates should be tested under the new rules.

3. Validate Against the Platåberget Testnet

The Ethereum Foundation team has indicated that developers can use the Platåberget testnet to verify whether fixes work under Glamsterdam-style pricing. Testing on a dedicated network is especially useful for protocols with complex execution flows that are hard to model locally.

4. Update Gas Estimation Assumptions

Frontends, SDKs, relayers, bundlers, and account abstraction services should ensure that transaction simulation and Gas buffers are updated. Even if contracts remain safe, poor estimation can create failed transactions and a bad user experience.

5. Communicate With Integrators

If your protocol is integrated by wallets, aggregators, custodial platforms, analytics providers, or automated market systems, share any known changes early. Gas repricing can affect not only the contract itself but also off-chain systems that simulate or route transactions.

What Regular Ethereum Users Need to Do

For ordinary users, the answer is simple: no manual action is expected.

You do not need to move funds, redeploy assets, approve anything, or change how you secure your wallet. Once infrastructure providers update their software, most changes should be handled behind the scenes through improved Gas estimation and transaction simulation.

That said, users may notice that certain complex transactions become slightly more expensive after the upgrade, especially if they involve many storage writes or contract deployments. Simple transfers and common interactions are expected to be far less affected.

As always, users should be cautious of phishing campaigns around major network upgrades. Protocol upgrades do not require seed phrase entry, private key export, or “wallet migration” through unknown websites.

What This Means for Ethereum’s Long-Term Design

Glamsterdam’s state operation repricing highlights a recurring theme in blockchain infrastructure: scalability is not only about increasing blockspace. It is also about pricing scarce resources correctly.

If Gas prices are too low for state-heavy operations, the network may grow faster than nodes can comfortably handle. If prices are too high, useful applications may become unnecessarily expensive. Ethereum’s challenge is to find a balance that supports innovation while protecting decentralization.

This is especially important as Ethereum’s roadmap continues to develop across several dimensions:

• larger and more efficient L2 ecosystems;
• better data availability for rollups;
• improved execution-layer performance;
• account abstraction adoption;
• long-term state management research;
• safer conditions for future Gas limit increases.

Glamsterdam is one piece of that larger roadmap. Its immediate impact may be narrow, but its design goal is foundational: make Ethereum’s resource pricing more realistic before pushing the network toward higher capacity.

Security Reminder: Protocol Upgrades Do Not Change Private Key Best Practices

Gas repricing affects transaction execution costs, not the way users control assets. Whether the network is undergoing a hard fork, a testnet rehearsal, or a client upgrade cycle, the most important user-side security principle remains the same: keep private keys offline and verify transactions carefully.

For users who interact with Ethereum DeFi, NFTs, staking services, and L2 bridges, a hardware wallet can add an important security layer. OneKey is designed to help users protect private keys offline while reviewing transaction details before signing. As network upgrades make Ethereum more capable, secure self-custody remains essential for safely participating in the ecosystem.

Glamsterdam is unlikely to disrupt most users, but it is a meaningful technical step for Ethereum developers. Teams with Gas-sensitive contracts should test early, update assumptions, and prepare integrations before the upgrade reaches mainnet.