The Ethereum ecosystem is abuzz with the launch of Platypusberg, a new short-term testnet designed to serve as an early, public testing ground for the forthcoming Glamsterdam upgrade. This vital initiative, a collaborative effort spearheaded by EthPandaOps, offers developers, stakers, and the broader community a stable environment to stress-test the significant changes slated for the next major Ethereum network hard fork. While Platypusberg aims to provide a robust platform for experimentation, it comes with a crucial warning: application developers must be prepared for breaking changes, particularly concerning the new gas repricing mechanisms. Tools that rely on hardcapped maximum gas limits, such as wallets, indexers, and gas estimators, are expected to break and will require immediate updates to function correctly post-Glamsterdam.
Platypusberg, a name playfully combining "Platypus" (suggesting its unique, early-stage nature) and "berg" (mountain, implying a significant challenge or peak to be climbed), is distinguished from previous short-lived devnets by its extended operational period. Intended to run for several months, it provides ample time for the community to thoroughly experiment with the functionalities and architectural shifts introduced by the Glamsterdam upgrade. This extended testing phase is critical for identifying and rectifying potential issues before Glamsterdam is deployed on Ethereum’s more established, longer-lived testnets, Sepolia and Goerli, and ultimately on the mainnet. The proactive engagement of the community on Platypusberg is seen as indispensable for ensuring a smooth transition and a robust network following the mainnet upgrade.
What the Glamsterdam Upgrade Entails
The Glamsterdam upgrade represents a substantial evolution for the Ethereum network, encompassing significant modifications to both its consensus and execution layers. At its core, Glamsterdam aims to enhance network efficiency, scalability, and the overall economic model of transaction processing. While the full scope of changes is detailed in the Glamsterdam meta EIP-7773, several key features are poised to reshape the Ethereum landscape.
One of the most impactful changes is the introduction of enhanced proposer-builder separation (PBS) mechanisms. Platypusberg, with its intentionally limited yet publicly accessible validator set, provides an ideal environment for stakers and infrastructure providers to test their validator setups and explore the builder deposit workflows. This includes the ability for anyone to deposit a new validator and participate in the testing of these new functionalities. The emphasis on ePBS (enhanced Proposer-Builder Separation) is a major architectural shift within the consensus layer. The goal is to ensure that solo stakers, decentralized validator technology (DVT) projects, custom software developers, and large-scale staking operators have sufficient opportunities to rigorously test their infrastructure in a live, albeit test, environment. The Glamsterdam fork on the Platypusberg testnet is scheduled for August 20th, offering a critical window for validator deposits and preparations leading up to the fork transition.
Beyond consensus layer changes, Glamsterdam introduces profound alterations to the network’s gas mechanics. These gas repricings are expected to affect a considerably wider audience, including every wallet, indexer, and gas estimator operating on the Ethereum network. The primary objective of these changes is to better align gas costs with the actual computational resources and state changes required for transactions, aiming to improve network efficiency and prevent certain forms of abuse. The implications of these repricings are far-reaching, necessitating a thorough review of how gas is calculated, displayed, and managed across the entire Ethereum ecosystem. Developers are strongly urged to leverage the Platypusberg testnet to understand precisely which tools or assumptions within their systems might break before the fork goes live on the mainnet.
Navigating the Platypusberg Testnet
To facilitate widespread participation and testing, EthPandaOps has provided a comprehensive suite of resources for using Platypusberg. Developers and users can access the Platypusberg resources page for a detailed summary of the included Ethereum Improvement Proposals (EIPs), client support status, and the latest launch updates. The devnet-8 specification, available on the Ethereum notes platform, offers crucial network settings, configuration values, bootnodes, and client release information necessary for setting up and running nodes.
A key feature designed to simplify the onboarding process is the Platypusberg website, which offers a convenient "Add Network" flow. This feature allows users to easily configure their Execution Layer (EL) and Consensus Layer (CL) clients for the testnet. Furthermore, a dedicated faucet is available to provide testnet ETH, essential for covering validator deposits and transaction fees during testing.
When running a node on Platypusberg, several considerations are paramount for effective testing and contribution to the ecosystem’s stability. These include:
- Validator Deposits: The testnet supports validator deposits, allowing stakers to familiarize themselves with the process and test their staking infrastructure under the new fork conditions.
- Builder Workflows: For those interested in the evolving proposer-builder separation, Platypusberg offers a testing ground for builder deposit mechanisms and related workflows.
- Gas Limit and Repricing: Users must be acutely aware of the changes to gas limits and repricing. Tools and applications that assume fixed gas costs or hardcapped limits will likely encounter issues.
Client Implementations for Platypusberg
To ensure compatibility and facilitate rapid testing, EthPandaOps has provided pre-built container images for various consensus and execution layer clients. While official client teams are in the process of preparing tagged releases for the Glamsterdam upgrade, these provided images offer immediate access for developers and operators.
Consensus Layer Client Images:
- 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
Execution Layer Client Images:
- 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 EL:
ethpandaops/nimbus-eth1:glamsterdam-devnet-8 - Ethrex:
ethpandaops/ethrex:glamsterdam-devnet-8
These images allow participants to quickly set up a full Ethereum node and begin testing the Glamsterdam fork’s functionalities without delay.
Support and Feedback Channels
The success of the Platypusberg testnet hinges on robust community feedback and swift resolution of identified issues. EthPandaOps has established primary channels for bug reporting and technical discussions. The Ethereum R&D Discord server is the most active venue for raising bugs and issues related to the specification. For those who prefer not to use Discord, direct contributions and issue reporting can be made to the relevant specification repositories on GitHub:
- Consensus Specs: https://github.com/ethereum/consensus-specs
- Execution Specs: https://github.com/ethereum/execution-specs
- Execution APIs: https://github.com/ethereum/execution-apis
- Builder Specs: https://github.com/ethereum/builder-specs
- Beacon APIs: https://github.com/ethereum/beacon-APIs
This multi-channel approach ensures that feedback is captured effectively and that development teams can iterate rapidly based on community input.
Implications and Next Steps in the Upgrade Path
The Platypusberg testnet is a critical stepping stone in a carefully orchestrated roadmap leading to the mainnet Glamsterdam upgrade. Its primary purpose is to provide the ecosystem with an early opportunity to experiment with the post-Glamsterdam Ethereum environment and proactively identify potential problems.
The gas repricing mechanism is particularly noteworthy for application developers. The core issue lies with any tool that relies on a fixed, hardcapped maximum gas limit. This includes essential components like wallets, which need to accurately display gas fees to users, and indexers, which process and store transaction data. Gas estimators, crucial for predicting transaction costs, will also need significant recalibration. The expectation is that any such tool assuming a static gas limit will break and require substantial updates. The community’s proactive engagement in testing Platypusberg alongside infrastructure operators is vital, as these downstream tooling changes are the most likely to catch the broader developer community off guard if not addressed early.
The gas repricing extends beyond just the block gas limit. Individual operation costs are also being adjusted to better reflect their computational intensity and impact on network state. A significant change introduced by EIP-8037 is the implementation of a separate state gas dimension. This means that operations which create new state – such as creating an account, deploying smart contract code, or writing to a new storage slot – will now incur a fixed cost per state byte (CPSB), calculated at runtime rather than upfront. The practical consequence is that a standard ETH transfer will no longer universally cost 21,000 gas. Transfers to an existing account will still be composed of base transaction costs, cold account access, and value transfer costs, totaling 21,000 gas. However, sending funds to a non-existent account will now incur additional state gas, calculated as STATE_BYTES_PER_NEW_ACCOUNT * CPSB. This necessitates a reassessment of any assumption that 21,000 gas covers all transfer scenarios or that gas estimation can rely on a single, monolithic gas dimension. EIP-2780 provides details on the decomposed intrinsic cost, while EIP-8038 elaborates on the increases in state access costs.
Following the feedback and necessary adjustments derived from Platypusberg, the next phase will involve a non-finality devnet, planned for deployment within the month. This devnet will focus on testing pathological consensus scenarios, further stress-testing the network’s resilience. Once these devnets have demonstrated sustained stability, the established long-lived testnets, Sepolia and Goerli, will undergo the Glamsterdam fork. Only after these significant testnets have successfully upgraded and proven stable will Ethereum’s mainnet begin its transition to Glamsterdam.
For those deeply invested in tracking the intricate progress of this upgrade, several resources are invaluable. The Ethereum R&D Discord server remains a central hub for real-time discussions. The All Core Dev calls provide direct insights into the technical decision-making process. The Glamsterdam upgrade tracker on Forkcast.org offers a comprehensive overview of the upgrade’s status, and the EthPandaOps Glamsterdam devnets GitHub repository provides granular details on the development and deployment of the testnets. The launch of Platypusberg marks a significant leap forward in preparing the Ethereum network for its next major evolution, emphasizing community collaboration and rigorous testing as cornerstones of a successful upgrade.
