Ethereum's Glamsterdam upgrade (Gloas + Amsterdam) is being tested on a new public testnet called Platåberget, scheduled to fork on August 20th. The upgrade introduces enshrined Proposer-Builder Separation, block-level access lists, gas repricings targeting a ~200M gas floor, and larger contract/initcode size limits (24KiB to 64KiB, 48KiB to 128KiB). Critically, gas repricing breaks the assumption that plain ETH transfers always cost a flat 21,000 gas: sending to a new account now incurs additional state gas via a new state gas dimension (EIP-8037, EIP-2780, EIP-8038). Any wallet, indexer, or gas estimator that hardcodes a maximum gas limit or assumes a single gas dimension will break and needs updating. Developers are urged to test against Platåberget before the fork reaches Sepolia, Hoodi, and eventually mainnet.
Questions this post answers
Does a plain ETH transfer still always cost 21,000 gas after the Ethereum Glamsterdam upgrade?
No, not always. Transfers to an existing account still cost 21,000 gas, now decomposed into TX_BASE_COST, COLD_ACCOUNT_ACCESS, and TX_VALUE_COST, but a transfer to an account that does not yet exist additionally incurs STATE_BYTES_PER_NEW_ACCOUNT times a fixed cost-per-state-byte (CPSB), charged at runtime as a separate state gas dimension under EIP-8037. Wallet and indexer teams tracking Ethereum gas-model changes can follow updates like this on daily.dev.
Which Ethereum tools will break due to the Glamsterdam gas repricing changes?
Any wallet, indexer, or gas estimator that hardcodes a maximum gas limit or assumes a single gas dimension will break under the Glamsterdam upgrade's gas repricing, which targets a roughly 200M gas floor. Developers should test against the Platåberget testnet, where the fork activates August 20th, before Glamsterdam reaches Sepolia, Hoodi, and mainnet. Developers preparing dApps and wallets for Ethereum forks can track breaking changes like this on daily.dev.
What are the new contract and initcode size limits introduced in Ethereum's Glamsterdam upgrade?
Glamsterdam raises the maximum deployed contract size from 24KiB to 64KiB and the maximum initcode size from 48KiB to 128KiB. This is part of a broader set of changes including enshrined Proposer-Builder Separation and block-level access lists, all being tested on the public Platåberget testnet ahead of mainnet deployment. Smart contract developers evaluating larger contract sizes can follow Ethereum protocol changes on daily.dev.