As the Ethereum ecosystem continues to evolve, the core development community has taken a significant step toward the future of the network. The introduction of Platåberget, a long-term public testnet, marks a pivotal moment in the path toward the highly anticipated Glamsterdam network upgrade. By bridging the gap between experimental devnets and established testnets like Sepolia and Hoodi, Platåberget provides a vital sandbox for developers, node operators, and infrastructure providers to stress-test the complex changes slated for the next phase of Ethereum.
The Genesis of Glamsterdam: Main Facts
The Glamsterdam upgrade represents one of the most comprehensive overhauls of the Ethereum protocol to date. It introduces deep-seated changes to both the Consensus Layer (CL) and the Execution Layer (EL). At the heart of this upgrade is a fundamental shift in how the network handles gas, validator interactions, and state management.
The primary objective of the Glamsterdam fork is to modernize the Ethereum architecture, ensuring that it remains scalable, secure, and performant as it handles increasingly complex decentralized applications (dApps). The inclusion of ePBS (enshrined Proposer-Builder Separation) is perhaps the most significant structural change, aiming to decentralize the block-building process and mitigate the risks of MEV (Maximum Extractable Value) centralization.
Platåberget serves as the testing ground for these changes. Unlike previous "devnets"—which are typically short-lived and designed for rapid, internal iteration—Platåberget is intended to run for several months. This longevity is by design; it offers a stable environment for the community to experiment, identify edge cases, and ensure that the infrastructure supporting the Ethereum mainnet is battle-tested before the upgrade is deployed to public testnets.
A Chronology of the Transition
The rollout of the Glamsterdam upgrade follows a disciplined, multi-stage timeline:
- Phase 1: Foundation and Specification. The initial research and specification phase led by core developers, documented in the Glamsterdam meta-EIP (EIP-7773).
- Phase 2: The Launch of Platåberget. Officially opened to the public, this testnet allows for validator deposits and infrastructure configuration. The fork transition on this testnet is scheduled for August 20th.
- Phase 3: Community Stress-Testing. The current period, where developers and operators are encouraged to deploy nodes, test their workflows, and identify potential breaking changes.
- Phase 4: Non-Finality Devnets. Following the integration of feedback from the Platåberget phase, subsequent devnets will be launched to test pathological consensus scenarios—stress-testing the network’s ability to recover from extreme failures.
- Phase 5: Public Testnet Upgrades. Once Platåberget and subsequent devnets demonstrate stability, the upgrade will be rolled out to existing, long-lived testnets such as Sepolia and Hoodi.
- Phase 6: Mainnet Deployment. The final transition of the Ethereum mainnet to the Glamsterdam protocol, marking the completion of the upgrade cycle.
Supporting Data and Technical Architecture
Platåberget is designed to mirror the actual network configuration as closely as possible. To facilitate easy participation, the EthPandaOps team has provided a suite of container images for all major execution and consensus clients.
Consensus Layer Support
The following clients are currently supported for the Platåberget deployment:
- Lighthouse:
ethpandaops/lighthouse:glamsterdam-devnet-8 - Lodestar:
ethpandaops/lodestar:unstable - Nimbus:
ethpandaops/nimbus-eth2:unstable - Prysm:
ethpandaops/prysm-beacon-chain:glamsterdam-devnet-8 - Teku:
ethpandaops/teku:glamsterdam-devnet-8 - Grandine:
ethpandaops/grandine:glamsterdam-devnet-8
Execution Layer Support
- Geth, Besu, Erigon, Nethermind, Reth, Nimbus (EL), and Ethrex all have dedicated container images (
ethpandaops/[client]:glamsterdam-devnet-8) available to ensure that node operators can participate in the testing process without delay.
The inclusion of these images underscores the collaborative nature of the effort. By providing a "one-click" configuration flow via the Platåberget portal, the developers aim to lower the barrier to entry, inviting not just institutional stakers, but solo stakers and home-node operators to contribute to the network’s resilience.
Implications for Developers: The Gas Paradigm Shift
Perhaps the most critical takeaway for the developer community is the gas repricing introduced in Glamsterdam. This is not a minor adjustment; it is a fundamental shift in the economics and mechanics of transaction execution.
The End of the "21,000 Gas" Assumption
Historically, developers and wallets have operated under the assumption that a standard ETH transfer costs a flat 21,000 gas. Glamsterdam shatters this assumption. Through EIP-8037 and EIP-2780, the network is introducing a "state gas" dimension.
Operations that create new state—such as deploying a contract or sending funds to a previously non-existent account—now incur a runtime cost based on the number of bytes added to the state. This "Cost Per State Byte" (CPSB) means that the cost of an operation is no longer deterministic based solely on the instruction type; it is now sensitive to the current state of the blockchain.
Who is affected?
- Wallet Developers: Any wallet that relies on hard-coded gas limits or simplistic gas estimation algorithms will likely encounter errors. These tools must be updated to account for the new, multi-dimensional gas metering.
- Indexers and Analyzers: Tools that calculate historical gas costs or forecast transaction fees will need to re-architect their logic to handle the state-dependent nature of the new pricing model.
- Smart Contract Developers: DApps that rely on specific gas calculations for cross-contract calls or internal accounting will need to audit their code to ensure they do not exceed block limits unexpectedly.
Official Responses and Community Engagement
The Ethereum R&D community has emphasized that the primary goal of this testnet is to catch "downstream" issues—the types of bugs that don’t appear in isolated laboratory conditions but manifest when complex, real-world user traffic hits the network.
"We want to ensure that all the solo stakers, DVT projects, custom software, and large-scale operators have ample chances to test their infrastructure," stated a lead developer on the EthPandaOps team. The community has established several avenues for feedback, including the Ethereum R&D Discord and various GitHub repositories (consensus-specs, execution-specs, and builder-specs).
The collaborative nature of the Glamsterdam upgrade is designed to prevent the "surprises" that often accompany major protocol changes. By forcing a period of public testing, the core developers are signaling that they prefer to break things in a controlled environment—like Platåberget—rather than risking network stability on Mainnet.
Next Steps and Future Outlook
As we look toward the months following the August 20th fork, the focus will shift from initial testing to performance optimization. Once the initial bugs are ironed out, the attention will turn toward "pathological" testing—simulating network partitions, under-performing nodes, and other edge cases that test the robust nature of the consensus layer.
For those involved in the Ethereum ecosystem, the mandate is clear: Test now. The transition to the Glamsterdam upgrade is not a passive event that will happen in the background; it requires the active participation of every developer who builds on, for, or around Ethereum.
By engaging with the Platåberget testnet, developers are not just preparing their applications for the next upgrade—they are helping to secure the future of the world’s most robust decentralized computing platform. Whether you are a validator operator managing a cluster or a developer writing the next generation of DeFi protocols, your contributions on the testnet are the bedrock upon which the success of the Glamsterdam upgrade will be built.
The road to Glamsterdam is paved with the collective efforts of the community. As the fork date approaches, the eyes of the ecosystem remain fixed on the metrics, stability reports, and feedback loops emanating from Platåberget. The transition is coming, and with it, a more efficient, scalable, and sophisticated Ethereum.
