The Ethereum development community has officially launched Platynberget, a short-term public testnet designed to serve as an early and comprehensive testing ground for the upcoming Glamsterdam network upgrade. This initiative provides developers, stakers, and infrastructure operators with a vital opportunity to identify and address potential issues before Glamsterdam is deployed on Ethereum’s longer-lived testnets, Sepolia and Hoxton, and subsequently, the mainnet. Platynberget’s introduction signifies a critical phase in the iterative development process of Ethereum, emphasizing community participation and rigorous pre-deployment testing.
The Glamsterdam upgrade, named playfully by combining "Gloas" (a nod to the proposed Verkle Tree upgrade) and Amsterdam, introduces significant, albeit backward-incompatible, changes to both the consensus and execution layers of the Ethereum protocol. The most impactful of these changes, particularly for application developers and service providers, involves a fundamental alteration to how gas limits are handled. This necessitates a proactive update for any tool that relies on a hardcoded maximum gas limit, including essential components like cryptocurrency wallets, blockchain indexers, and gas estimation services. Failure to adapt these tools will result in their malfunction, highlighting the imperative for immediate engagement with the Platynberget testnet.
A Deeper Dive into the Glamsterdam Upgrade’s Core Components
The Glamsterdam upgrade is not a single, monolithic change but rather a collection of Ethereum Improvement Proposals (EIPs) designed to enhance scalability, efficiency, and the overall architecture of the network. At its heart, Glamsterdam aims to lay the groundwork for future advancements, particularly in the realm of execution and data availability.
One of the most significant advancements expected with Glamsterdam is the introduction of Proposer-Builder Separation (PBS), specifically in its early forms. While the full vision of PBS is a long-term goal, Glamsterdam begins to integrate aspects of it into the consensus layer. Platynberget is explicitly designed to allow a broad spectrum of participants to test their validator and builder deposit workflows. This includes solo stakers, Decentralized Validator Technology (DVT) projects, custom software developers, and large-scale staking operators. The ability for anyone to deposit a new validator and experiment with becoming a block builder is a cornerstone of this testnet. The Glamsterdam fork on Platynberget is scheduled for August 20th, providing ample time for participants to make necessary validator deposits and prepare for the transition. This phased approach to validator and builder integration is crucial for ensuring the stability and security of the network as it evolves.
Beyond the structural changes related to PBS, Glamsterdam also ushers in substantial gas repricings. These adjustments are fundamental and are expected to affect a much wider audience within the Ethereum ecosystem. Every wallet, indexer, and gas estimator currently operates with certain assumptions about transaction costs and block capacity. The gas repricings in Glamsterdam will alter these assumptions, requiring a thorough re-evaluation and potential overhaul of existing tooling. The objective of these changes is to create a more dynamic and efficient gas market, better reflecting the actual computational cost of various operations and preventing potential network congestion through more nuanced pricing mechanisms.
The complete suite of EIPs integrated into the Glamsterdam upgrade is formally tracked under EIP-7773, serving as the meta-EIP that binds all the individual proposals together. This comprehensive proposal outlines the objectives and technical specifications for the entire upgrade package.
Navigating Platynberget: A Practical Guide for Participants
The Platynberget testnet is more than just a theoretical exercise; it’s a fully functional environment designed for practical engagement. For those looking to join and contribute, a dedicated resources page at forkcast.org/devnets/glamsterdam-devnet-8/ provides a detailed summary of the included EIPs, client support status, and the current launch status of the network. Furthermore, the devnet-8 specification, available at notes.ethereum.org/@ethpandaops/glamsterdam-devnet-8, offers essential network settings, configuration values, bootnodes, and specific client release information necessary for running a node.
To facilitate an accessible entry point, the Platynberget website, plataberget.dev/, offers a user-friendly "Add Network" flow. This feature simplifies the process of configuring both the execution layer (EL) and consensus layer (CL) clients, eliminating a common barrier to entry for less experienced users. Complementing this ease of setup, a dedicated faucet at faucet.plataberget.ethpandaops.io/ provides essential testnet ETH. This test currency is crucial for covering validator deposits and transaction fees, enabling participants to fully engage with the network’s functionalities.
Client Implementations: Staying Ahead of the Curve
To support the testing efforts on Platynberget, specific container images have been made available by ethPandaOps, while official client teams finalize their tagged releases for the Glamsterdam upgrade. These images ensure that developers and operators can immediately begin testing with compatible software.
For the Consensus Layer (CL), the following client images are recommended:
- Lighthouse:
ethpandaops/lighthouse:glamsterdam-devnet-8 - Lodestar:
ethpandaops/lodestar:unstable - Nimbus:
ethpandaops/nimbus-eth2:unstable - Prysm (Beacon Chain):
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
For the Execution Layer (EL), the following client images are available:
- 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 - Nimbus (Execution Layer):
ethpandaops/nimbus-eth1:glamsterdam-devnet-8 - Ethrex:
ethpandaops/ethrex:glamsterdam-devnet-8
Implications of Gas Repricing and State Gas Dimensions
The gas repricing component of Glamsterdam is arguably the most critical for the broad Ethereum ecosystem, extending far beyond validator operations. The announcement explicitly states that "any tool that relies on a hardcapped maximum gas limit (think wallets, indexers and gas estimators) will break and needs to be updated." This is a direct consequence of how the gas mechanics are being re-architected.
The repricing is not solely about adjusting the overall block gas limit. It introduces a fundamental shift with EIP-8037, which establishes a separate "state gas dimension" for operations that result in the creation of new state on the blockchain. This means that actions like creating a new account, deploying smart contract code, or writing to a previously unused storage slot will incur a fixed cost per byte of new state created. This cost, referred to as "CPSB" (Cost Per State Byte), is charged at runtime, adding a dynamic layer to transaction cost calculations.
The practical consequence of this change is profound. A simple ETH transfer, which has historically been understood to cost a flat 21,000 gas, will now have a more nuanced pricing structure. Transfers to an existing account will still cost approximately 21,000 gas, but this figure is now a decomposition of base transaction costs, cold account access, and value transfer costs. However, sending funds to an account that does not yet exist will incur an additional state gas charge. This additional cost is calculated as STATE_BYTES_PER_NEW_ACCOUNT * CPSB.
Consequently, any application or service that makes assumptions about fixed transaction costs or operates with a single, unified gas dimension for estimation will need significant revision. Developers must revisit EIP-2780 for the decomposed intrinsic costs and EIP-8038 for understanding the increases in state-access costs. This proactive testing on Platynberget is essential to identify and rectify these dependencies before they cause widespread disruptions on the mainnet.
Support and Feedback Channels: Collaborative Development
The success of Platynberget and the subsequent Glamsterdam upgrade hinges on effective community engagement and robust feedback mechanisms. The primary channel for reporting bugs, suggesting improvements, and discussing issues related to the specification is the Ethereum R&D Discord server (discord.gg/ZEws7Pu7g4). This real-time communication platform allows for immediate interaction with core developers and other community members.
For those who prefer asynchronous communication or wish to contribute to the formal specification process, feedback can also be provided through the relevant specification repositories on GitHub:
- Consensus Specs: github.com/ethereum/consensus-specs
- Execution Specs: github.com/ethereum/execution-specs
- Execution APIs: github.com/ethereum/execution-apis
- Builder Specs: github.com/ethereum/builder-specs
- Beacon APIs: github.com/ethereum/beacon-APIs
The Road Ahead: From Testnets to Mainnet
Platynberget represents the initial phase of a carefully orchestrated rollout for the Glamsterdam upgrade. Its primary objective is to allow the community to experiment with the proposed changes and identify potential issues in a controlled environment. The data gathered from Platynberget will be instrumental in refining client software and the core specifications.
Following the stability and feedback gathered from Platynberget, the next step involves deploying the Glamsterdam fork on a non-finality devnet within the month. This will allow for the testing of more complex and potentially pathological consensus scenarios that might not arise in a standard testnet environment.
Once these devnets have demonstrated sustained stability, the upgrade will be rolled out to Ethereum’s existing long-lived testnets, Sepolia and Hoxton. This provides another layer of testing on established networks with a history of active usage. Only after these crucial steps have been successfully completed will the Glamsterdam upgrade be scheduled for deployment on the Ethereum mainnet. This multi-stage approach is a testament to Ethereum’s commitment to robust, community-driven development and ensuring a smooth transition for its global user base.
For those keen on staying abreast of the upgrade’s progress at a granular level, several resources are invaluable. The Ethereum R&D Discord server remains a central hub for real-time discussions. The All Core Dev calls (forkcast.org/calls?filter=acd) offer direct insights into development discussions. The Glamsterdam upgrade tracker at forkcast.org/upgrade/glamsterdam/ provides a comprehensive overview of the upgrade’s status. Finally, the EthPandaOps Glamsterdam devnets GitHub repository (github.com/ethpandaops/glamsterdam-devnets) offers technical details and ongoing updates.
The launch of Platynberget marks a significant milestone, inviting the entire Ethereum ecosystem to participate in shaping the future of the network. The emphasis on community testing and feedback underscores the decentralized ethos of Ethereum, ensuring that advancements are robust, secure, and beneficial to all participants.
