The Ethereum Foundation announced that the Gas repricing in Glamsterdam will render wallets, indexers, and Gas estimators that rely on hardcoded maximum Gas limits ineffective, requiring developers to update their systems.

The Platåberget public testnet is now open and will run continuously for several months; the Glamsterdam fork is scheduled to activate on August 20 on this testnet for developers to test compatibility before deploying on Sepolia, Hoodi, and the mainnet.

EIP-8037 introduces a separate "status Gas" dimension for creating new on-chain states. New accounts, deploying contract code, or writing to new storage slots will incur additional charges based on the number of status bytes and CPSB at runtime.

The base cost for transferring ETH to existing accounts remains 21,000 Gas, but this cost is split into transaction base fees, cold account access fees, and transfer value fees; if the recipient address has not yet been created on-chain, additional status Gas for account creation must be paid.

As a result, the default wallet logic of "all ETH transfers only require 21,000 Gas" will underestimate some transaction costs; products that estimate transaction fees solely based on a single Gas dimension will also fail to correctly handle the combination of execution Gas and status Gas.

The upgrade will also involve collaborative Gas repricing, aiming to push the minimum Gas capacity of blocks to around 200 million; the pricing of individual operations will also change, and fixed maximum Gas limits, old transaction simulation logic, and old exception handling processes may trigger failures or incorrect pricing.

Glamsterdam also includes native proposer-builder separation, block-level access lists, and increased limits on contract and initialization code sizes. The Ethereum roadmap marks this upgrade target for Q4 2026, with the specific mainnet launch date yet to be finalized.

In terms of market mechanisms, status Gas will directly price the externality of "expanding Ethereum's global state": new accounts, contract deployments, and new storage will no longer only consume execution resources once, but will also incur additional costs for nodes to maintain and synchronize state over the long term. Data-intensive applications that frequently create wallets, deploy contracts, and write new storage will bear higher marginal costs; node operators and long-term network health will benefit from constraints on state expansion, while wallets, RPC service providers, L2 bridges, and indexing infrastructure will need to bear the costs of migration, simulation, and pricing system transformation first.

Source: Public Information