Ethereum’s Glamsterdam upgrade has reached a new stage: public experimentation. The Ethereum Foundation introduced Platåberget in August 2026 as an early, short-term testnet that anyone can join. It is intended to run for several months, giving client teams, validators, infrastructure providers, wallet developers, and smart-contract builders a stable place to find problems before the upgrade reaches Sepolia, Hoodi, and mainnet.
Public testing does not mean the upgrade is finished. It means the specifications and client implementations are mature enough for broader, adversarial use. Glamsterdam combines major consensus changes with execution-layer repricing, so the most useful question is not “when will it ship?” but “which assumptions could break before it ships?”
Enshrined proposer-builder separation is the headline change
EIP-7732 introduces enshrined proposer-builder separation, usually shortened to ePBS. Today, many proposers rely on external infrastructure to obtain builder payloads. The proposal moves builders into the protocol, separates consensus and execution components, and introduces payload-timeliness attestations.
That design changes validator and builder workflows substantially. Platåberget allows public validator and builder deposits so solo stakers, distributed-validator projects, custom software, and large operators can exercise the new path. The testnet’s relatively small validator set is a feature: it creates a practical environment for testing deposits, payload reveals, attestations, and failure cases without waiting for a long-lived public network.
For application users, ePBS is mostly infrastructure. For operators, it affects client compatibility, monitoring, keys, and timing. A validator setup that works under the current proposer-builder workflow should not be assumed ready without testing.
Gas repricing can expose hidden assumptions
Glamsterdam also schedules state-creation and state-access gas changes through EIP-8037 and EIP-8038. The goal is to make gas charges better reflect the work of creating and accessing Ethereum state as the network grows. The Ethereum Foundation says the repricing supports a path toward roughly three times higher base throughput while keeping state growth manageable.
Historical transaction replays found that most contracts are unaffected, but a small set can fail or degrade. The common danger is hardcoded gas logic: fixed call stipends, assumptions about transfer costs, branches based on remaining gas, presigned transactions with fixed limits, or cached gas constants in wallets and estimators.
Many flagged transactions succeed after increasing the supplied gas limit. Some contracts require code review and targeted fixes. Wallets, indexers, RPC infrastructure, and gas estimators should update their models rather than treating older constants as permanent.
Other changes broaden the testing surface
The Glamsterdam meta proposal, EIP-7773, lists a wide set of scheduled changes. These include block-level access lists, forward-compatible consensus data structures, revised block-gas accounting, larger maximum contract sizes, transaction-cost changes, and rules affecting validator exits and slashed proposers.
Larger contracts and initcode may help complex deployments, but they also require tooling to handle new limits correctly. Forward-compatible data structures and block-level access information can affect clients, explorers, indexers, and downstream analytics. The breadth of the upgrade is why testing only a single smart contract call is not enough.
What teams should test now
Smart-contract teams should replay realistic transactions, especially paths with internal calls, fixed gas limits, or unusual state access. Wallet and infrastructure teams should verify gas estimation, transaction simulation, indexing, and monitoring under the new rules. Validator and builder operators should test deposits, payload workflows, failover, observability, and mixed-client behavior.
Teams should also record what fails. A public testnet is most valuable when reproducible issues reach the relevant specification or client repository, not when local workarounds hide them. Ordinary users do not need to take action at this stage, but developers who maintain critical Ethereum infrastructure should treat Platåberget as an early compatibility deadline.
The road from Platåberget to mainnet
The planned sequence remains deliberate. After feedback is incorporated, additional devnets are expected to test difficult consensus scenarios. Glamsterdam then moves to Ethereum’s long-lived testnets. Mainnet activation follows only after those upgrades are stable, and the EIP-7773 activation table still has no mainnet timestamp.
That uncertainty is healthy. Glamsterdam’s public testing phase is a chance to turn broad protocol ambition into observable behavior. The important milestone is not the name of the testnet; it is the opportunity to discover which contracts, tools, and operational assumptions need to change before real value depends on them.
Key takeaways
- Platåberget is an early public testnet, not the final mainnet release.
- ePBS changes validator and builder workflows at the consensus layer.
- State gas repricing can break software that relies on hardcoded gas assumptions.
- Mainnet timing remains dependent on successful testing and long-lived testnet upgrades.