The Ethereum ecosystem is entering a critical phase of preparation for the highly anticipated Glamsterdam upgrade, with the launch of Platypusberg, a short-term public testnet. This initiative, codenamed "Glamsterdam’s (Gloas + Amsterdam) early testing ground," invites developers, stakers, and the broader community to engage in rigorous testing of upcoming protocol changes. The primary objective of Platypusberg is to provide a stable, albeit temporary, environment for identifying and rectifying potential issues before the Glamsterdam hard fork is deployed on Ethereum’s more permanent testnets, Sepolia and Goerli (formerly referred to as Hoodi in the original text), and ultimately, the mainnet.
A crucial announcement accompanying the launch of Platypusberg highlights significant breaking changes for application developers. Specifically, any tool or application that relies on a hardcoded maximum gas limit, such as cryptocurrency wallets, blockchain indexers, and gas estimation services, will cease to function correctly post-Glamsterdam and requires immediate updates. This proactive call to action underscores the importance of community participation in Platypusberg, offering an invaluable opportunity to test and adapt essential infrastructure.
Platypusberg distinguishes itself from previous, more ephemeral development networks (devnets) by its intended longer operational lifespan, slated to run for several months. This extended duration is designed to facilitate comprehensive experimentation with the post-Glamsterdam Ethereum protocol, allowing ample time for the community to discover and address any unforeseen complexities.
The Transformative Changes of the Glamsterdam Upgrade
The Glamsterdam upgrade represents a substantial evolution for the Ethereum protocol, introducing significant modifications to both its consensus and execution layers. While a comprehensive list of included Ethereum Improvement Proposals (EIPs) is meticulously tracked under the Glamsterdam meta EIP-7773, several key advancements are poised to reshape the network’s functionality and performance.
One of the most impactful changes is the introduction of proposer-builder separation (PBS) and its early implementation through partial PBS (pPBS) and eventually full PBS. This innovation aims to enhance the efficiency and decentralization of block production. Platypusberg offers a unique opportunity for the community to test these new paradigms. The testnet features a relatively small but publicly accessible validator set, allowing any interested party to deposit a new validator and experiment with validator operations and the builder deposit workflows. This is particularly vital for solo stakers, decentralized validator technology (DVT) projects, custom software developers, and large-scale operators, ensuring they have ample opportunities to stress-test their infrastructure against the new consensus mechanisms. The Glamsterdam fork on Platypusberg is scheduled for August 20th, providing a clear deadline for validator deposits and preparations for the fork transition.
Another profound alteration within the Glamsterdam upgrade concerns gas repricing. These adjustments are expected to have a far-reaching impact, affecting virtually every component of the Ethereum ecosystem, including wallets, indexers, and gas estimators. The move necessitates a thorough re-evaluation of how gas is consumed and calculated, prompting developers to scrutinize their systems for any assumptions or dependencies that might be invalidated by these changes.
Navigating Platypusberg: Resources and Technical Details
To facilitate widespread adoption and testing on Platypusberg, a comprehensive suite of resources has been made available. The Platypusberg resources page offers a detailed summary of the included EIPs, client support status, and the current launch progress. For those seeking in-depth technical specifications, the devnet-8 specification provides crucial network settings, configuration values, bootnodes, and client release information.
For a streamlined onboarding experience, the dedicated Platypusberg website features a convenient "Add Network" flow, simplifying the configuration of both Execution Layer (EL) and Consensus Layer (CL) clients. Furthermore, a faucet is available to provide testnet Ether, essential for covering validator deposits and gas fees incurred during testing.
When running a node on Platypusberg, several key considerations are paramount:
Client Images for Testing:
While official client teams are diligently preparing tagged releases for the Glamsterdam upgrade, the ethPandaOps team has provided specialized container images for immediate testing purposes. These images are crucial for ensuring all components of the network are functioning as expected in the pre-release phase.
-
Consensus Layer (CL) Client Images:
lighthouse:ethpandaops/lighthouse:glamsterdam-devnet-8lodestar:ethpandaops/lodestar:unstablenimbus:ethpandaops/nimbus-eth2:unstableprysm:ethpandaops/prysm-beacon-chain:glamsterdam-devnet-8prysm_validator:ethpandaops/prysm-validator:glamsterdam-devnet-8teku:ethpandaops/teku:glamsterdam-devnet-8grandine:ethpandaops/grandine:glamsterdam-devnet-8
-
Execution Layer (EL) Client Images:
besu:ethpandaops/besu:glamsterdam-devnet-8geth:ethpandaops/geth:glamsterdam-devnet-8erigon:ethpandaops/erigon:glamsterdam-devnet-8nethermind:ethpandaops/nethermind:glamsterdam-devnet-8reth:ethpandaops/reth:glamsterdam-devnet-8nimbusel:ethpandaops/nimbus-eth1:glamsterdam-devnet-8ethrex:ethpandaops/ethrex:glamsterdam-devnet-8
Support and Community Feedback Channels
The success of Platypusberg hinges on active community engagement and the swift identification of bugs and issues. The Ethereum R&D Discord server serves as the primary hub for raising such concerns and fostering collaborative problem-solving. For those who prefer alternative channels, the specification repositories for consensus, execution, execution-apis, builder-specs, and beacon-APIs on GitHub are also open for issue reporting and discussion.
The Road Ahead: From Platypusberg to Mainnet
Platypusberg represents a pivotal stepping stone in the roadmap towards the Glamsterdam upgrade. By providing a dedicated testing environment, it empowers the community to thoroughly experiment with the forthcoming changes and to proactively address potential challenges.
The gas repricing mechanism, in particular, demands the immediate attention of application developers. The fundamental shift away from a singular, hardcapped maximum gas limit signifies a paradigm change. Tools that rely on fixed gas estimations will inevitably break. This includes, but is not limited to, wallets that need to accurately convey transaction costs to users, indexers that track gas usage patterns, and gas estimators that inform users about optimal transaction fees. The urgency for these developers to test against Platypusberg cannot be overstated, as this class of change is most likely to impact downstream tooling unexpectedly if not addressed proactively.
The gas repricing extends beyond just the block gas limit; individual operation costs are also being recalibrated. Notably, EIP-8037 introduces a distinct "state gas dimension" for operations that create new state on the blockchain. Actions such as creating a new account, deploying smart contract code, or writing to an empty storage slot will now incur a fixed cost per state byte, referred to as "Cost Per State Byte" (CPSB). This cost is charged at runtime rather than being bundled into an upfront transaction fee.
The practical implication of this change is that a simple Ether transfer will no longer be a universally flat 21,000 gas. Transfers to an existing account will still maintain a similar cost structure (composed of TX_BASE_COST, COLD_ACCOUNT_ACCESS, and TX_VALUE_COST), but sending funds to a newly created account will incur an additional state gas cost equivalent to STATE_BYTES_PER_NEW_ACCOUNT multiplied by CPSB. Consequently, any application or tool that assumes a flat 21,000 gas for all transfers, or relies on a single gas dimension for estimations, must be revisited and updated. EIP-2780 provides a detailed breakdown of the decomposed intrinsic costs, while EIP-8038 outlines the increases in state-access costs.
Following the feedback and adjustments made based on the Platypusberg testing phase, the next stage will involve a non-finality devnet. This network will be deployed within the month to specifically test pathological consensus scenarios, ensuring the network’s resilience under adverse conditions.
Once these development networks have demonstrated sustained stability, the Glamsterdam fork will be rolled out to Ethereum’s existing long-lived testnets: Sepolia and Goerli. The successful upgrade and stabilization of these testnets will pave the way for the ultimate transition of the Ethereum mainnet to the Glamsterdam protocol.
For those who wish to stay abreast of the development progress at a more granular level, several key resources are recommended. The Ethereum R&D Discord server provides real-time discussions and updates. The All Core Dev calls, accessible via forkcast.org, offer insights into the technical decision-making process. The Glamsterdam upgrade tracker on forkcast.org serves as a central repository for all information related to the upgrade. Finally, the ethPandaOps Glamsterdam devnets GitHub repository offers a detailed look at the technical implementation and ongoing work. The Ethereum community is encouraged to actively participate on Platypusberg, contributing to the collective effort of building a more robust and efficient blockchain for the future.
