The Ethereum ecosystem is abuzz with the launch of Platåberget, a crucial new public testnet designed to facilitate early community participation and robust testing for the forthcoming Glamsterdam upgrade. This significant development marks a pivotal step in Ethereum’s continuous evolution, introducing substantial modifications to both its consensus and execution layers. Application developers and infrastructure operators are strongly advised to engage with Platåberget immediately, as the Glamsterdam upgrade brings breaking changes, most notably to how gas limits are handled, which will necessitate updates for a wide array of existing tools. Any application or service relying on a hardcapped maximum gas limit – including wallets, indexers, and gas estimators – will require urgent recalibration to remain functional post-Glamsterdam.
Ethereum’s Relentless Pursuit of Scalability and Efficiency: The Context of Glamsterdam
Ethereum, the world’s leading smart contract platform, has consistently evolved through a series of ambitious upgrades aimed at enhancing its scalability, security, and sustainability. Following the monumental shift to Proof-of-Stake with "The Merge" and subsequent improvements like "Shanghai" and "Dencun," the network continues its methodical journey towards a more robust and efficient architecture. Each upgrade, guided by Ethereum Improvement Proposals (EIPs), represents a collective effort from core developers, researchers, and the wider community to implement features that address current challenges and lay the groundwork for future innovations. Testnets serve as indispensable proving grounds in this process, providing a controlled environment for developers to test new features, identify bugs, and ensure the stability of client software before mainnet deployment. This iterative approach minimizes risks and fosters a secure transition for the entire ecosystem. The Glamsterdam upgrade, encapsulated by the meta EIP-7773, is positioned as the next critical phase, bringing changes that are foundational to Ethereum’s long-term vision. These changes are not merely incremental; they represent a fundamental rethinking of how transactions are processed and how state is managed on the network, promising greater efficiency and paving the way for further scaling solutions.
Platåberget: A Dedicated Testbed for Community Engagement
Unlike the typically short-lived "devnets" that precede major upgrades, Platåberget is engineered for longevity, intended to operate for several months. This extended runtime offers the Ethereum community an unprecedented opportunity to engage deeply and stably with the post-Glamsterdam Ethereum environment. It functions as an early, publically joinable testing ground, providing a stable platform for experimentation, stress testing, and identifying potential vulnerabilities or unintended consequences before the upgrade rolls out to Ethereum’s longer-lived public testnets, Sepolia and Hoodi. The decision to maintain Platåberget for a sustained period underscores the complexity of the Glamsterdam changes and the development team’s commitment to thorough community-driven validation. This extended testing phase allows for multiple cycles of feedback, bug fixes, and refinements, ensuring that the eventual mainnet upgrade is as seamless and secure as possible.
Key Innovations of the Glamsterdam Fork
The Glamsterdam upgrade introduces a suite of significant changes impacting both the consensus and execution layers of Ethereum. Two principal areas demand immediate attention from developers and operators: the implementation of Ethereum Proposer-Builder Separation (ePBS) and a comprehensive overhaul of gas repricings.
Ethereum Proposer-Builder Separation (ePBS): Reshaping the Consensus Layer
One of the most profound changes arriving with Glamsterdam is the advancement of Ethereum Proposer-Builder Separation (ePBS). This mechanism aims to further decentralize the block production process and mitigate the risks associated with Maximal Extractable Value (MEV) – the profit a validator can make by arbitrarily including, excluding, or reordering transactions within a block. In the current model, validators are responsible for both proposing and building blocks, giving them significant control over transaction ordering. ePBS separates these roles: "builders" construct blocks from user transactions, optimizing for MEV and submitting them to "proposers," who then select the most profitable valid block to include in the chain.
Platåberget features a relatively small but publicly joinable validator set, allowing anyone to deposit a new validator and test their validator and builder deposit workflows. This hands-on testing is crucial for solo stakers, Distributed Validator Technology (DVT) projects, custom software providers, and large-scale operators to ensure their infrastructure is compatible with the new ePBS paradigm. The Glamsterdam fork on Platåberget is scheduled for August 20th, providing ample time for participants to make their deposits and prepare for the transition. The successful implementation of ePBS is vital for Ethereum’s long-term health, promoting censorship resistance and fostering a more equitable and decentralized network by distributing the power associated with block production.
Gas Repricings: A Fundamental Shift in Transaction Cost Calculation
Perhaps the most impactful change for the broader Ethereum ecosystem, particularly for application developers and users, is the comprehensive suite of gas repricings. These modifications are designed to optimize network resource utilization and address inefficiencies in the current gas model. The repricings extend beyond a simple adjustment to the block gas limit; they fundamentally alter the cost of individual operations and introduce an entirely new dimension to gas metering.
The Breaking Change for Existing Tools:
The most immediate and critical consequence of the gas repricings is that any tool or application relying on a hardcapped maximum gas limit will break and requires immediate updates. This includes widely used wallets, blockchain indexers, and gas estimation services that currently assume a fixed maximum gas ceiling for transactions or operations. The previous assumptions about gas consumption will no longer hold true, leading to failed transactions, incorrect cost estimations, or even denial-of-service issues if not updated. Developers are urged to use Platåberget as a testing ground to identify exactly which tools and assumptions within their systems are affected before the Glamsterdam fork goes live on Mainnet.
Introduction of a Separate State Gas Dimension (EIP-8037):
A cornerstone of the new gas model is the introduction of a separate state gas dimension for operations that create new state on the network, as detailed in EIP-8037. Historically, all operations were metered solely based on computation and storage access within a single gas dimension. Now, creating an account, deploying new code, or writing to a fresh storage slot will incur a distinct "state gas" cost, metered at a fixed cost per state byte (CPSB) and charged at runtime rather than upfront.
This change has significant practical consequences. For instance, a simple ETH transfer, which has long been assumed to cost a flat 21,000 gas, will no longer always conform to this figure. While transfers to an existing account will still incur a base cost of 21,000 gas (now decomposed into TX_BASE_COST + COLD_ACCOUNT_ACCESS + TX_VALUE_COST as per EIP-2780), sending funds to an account that does not yet exist will additionally incur STATE_BYTES_PER_NEW_ACCOUNT × CPSB state gas at runtime. This means the transaction cost will be higher and dynamically determined based on the state impact.
Any dApp, wallet, or service that assumes a fixed 21,000 gas covers every ETH transfer, or that relies on a single gas dimension for its estimations, must be thoroughly revisited. EIP-8038 further elaborates on these state-access increases. The rationale behind this dual-dimension gas metering is to more accurately reflect the true resource consumption of different operations, particularly those that expand the network’s state. By internalizing the cost of state growth, Ethereum aims to encourage more efficient contract design, mitigate state bloat, and improve overall network performance and sustainability.
Using Platåberget: A Developer’s Toolkit
To facilitate widespread testing, comprehensive resources have been made available for developers and operators. The Platåberget resources page on forkcast.org offers a summary of included EIPs, client support status, and launch details. Further technical specifications, including network settings, configuration values, bootnodes, and client release information, can be found in the devnet-8 specification on notes.ethereum.org.
For ease of access, the dedicated plataberget.dev page provides a streamlined "one-click Add Network" flow, enabling users to effortlessly configure their Execution Layer (EL) and Consensus Layer (CL) clients. Additionally, a faucet at faucet.plataberget.ethpandaops.io dispenses testnet ETH, essential for covering deposit requirements for validators and gas costs for transactions during the testing phase.
Client Images for Immediate Deployment:
Recognizing the urgency of testing, ethPandaOps has provided temporary container images for various client implementations, allowing developers to begin testing immediately while official client teams prepare their tagged releases.
-
Consensus Layer Clients:
- Lighthouse:
ethpandaops/lighthouse:glamsterdam-devnet-8 - Lodestar:
ethpandaops/lodestar:unstable - Nimbus:
ethpandaops/nimbus-eth2:unstable - Prysm:
ethpandaops/prysm-beacon-chain:glamsterdam-devnet-8 - Prysm Validator:
ethpandaops/prysm-validator:glamsterdam-devnet-8 - Teku:
ethpandaops/teku:glamsterdam-devnet-8 - Grandine:
ethpandaops/grandine:glamsterdam-devnet-8
- Lighthouse:
-
Execution Layer Clients:
- Besu:
ethpandaops/besu:glamsterdam-devnet-8 - Geth:
ethpandaops/geth:glamsterdam-devnet-8 - Erigon:
ethpandaops/erigon:glamsterdam-devnet-8 - Nethermind:
ethpandaops/nethermind:glamsterdam-devnet-8 - Reth:
ethpandaops/reth:glamsterdam-devnet-8 - Nimbusel:
ethpandaops/nimbus-eth1:glamsterdam-devnet-8 - Ethrex:
ethpandaops/ethrex:glamsterdam-devnet-8
- Besu:
These images enable developers to quickly spin up nodes compatible with the Platåberget testnet and begin their testing procedures without delay.
Support and Feedback Mechanisms
The success of a major network upgrade hinges on robust community feedback. The Ethereum R&D Discord server is designated as the primary channel for reporting bugs or issues related to the Glamsterdam specification. For those who prefer alternative communication methods, issues can also be raised directly within the respective specification repositories on GitHub, including those for consensus, execution, execution-apis, builder-specs, and beacon-APIs. This multi-channel approach ensures that all feedback, from minor glitches to critical vulnerabilities, is captured and addressed by the core development teams.
Chronology and Future Milestones
The launch of Platåberget initiates a structured timeline for the Glamsterdam upgrade. The fork on Platåberget is scheduled for August 20th, providing a concrete deadline for initial preparations and testing. Following this initial phase of community experimentation and issue identification on Platåberget, the development roadmap includes several key stages:
- Non-Finality Devnet: Within approximately one month after Platåberget stabilizes and feedback is incorporated, a specialized non-finality devnet will be launched. This environment is designed to test pathological consensus scenarios, pushing the limits of the network under extreme conditions to ensure its resilience.
- Long-Lived Public Testnets: Once these devnets have demonstrated stability, the Glamsterdam fork will be deployed on Ethereum’s existing long-lived public testnets, Sepolia and Hoodi. This stage is crucial for broader ecosystem testing, allowing a wider range of dApps and services to interact with the new protocol in a more persistent environment.
- Ethereum Mainnet Transition: Only after Sepolia and Hoodi have successfully upgraded and maintained stability for a sufficient period will the final transition to Glamsterdam on the Ethereum mainnet occur. This methodical, phased approach is a hallmark of Ethereum’s upgrade strategy, prioritizing security and stability above all else.
Broader Implications and Ethereum’s Vision
The Glamsterdam upgrade, spearheaded by the Platåberget testnet, is more than just a technical update; it represents a significant step in Ethereum’s ongoing journey towards its long-term vision. The changes to gas repricing and the introduction of a state gas dimension are crucial for improving the network’s efficiency, managing state growth, and creating a more predictable and fair transaction fee market. These advancements are instrumental in preparing Ethereum for future scaling solutions, such as sharding (The Surge), and bolstering its security and resilience against various threats (The Scourge).
For dApp and wallet developers, proactive engagement with Platåberget is not merely a recommendation but a necessity. The changes introduced are fundamental and will directly impact user experience and application functionality. By actively participating, developers can not only ensure their products remain compatible but also contribute to the robustness and success of the upgrade, shaping the future of decentralized applications on Ethereum. The community’s collective effort in testing and providing feedback is paramount to a smooth and secure transition.
For those keen to monitor progress at a granular level, several key resources are available: the Ethereum R&D Discord server, the All Core Dev calls, the Glamsterdam upgrade tracker on forkcast.org, and the EthPandaOps Glamsterdam devnets GitHub repository. These platforms offer real-time updates, discussions, and technical insights into the development process. The Ethereum community is united in its commitment to advancing the network, and Platåberget stands as a testament to this collaborative spirit, inviting all stakeholders to contribute to the next chapter of Ethereum’s evolution.








