The Ethereum developer community has taken a significant step toward its next major network overhaul with the launch of Platåberget, a public-facing testing ground for the upcoming Glamsterdam upgrade. Combining the codenames Gloas and Amsterdam, Platåberget represents a collaborative milestone where developers, node operators, and validators can interact with post-Glamsterdam Ethereum mechanics in a live network environment. Unlike the short-lived development networks that typically precede major upgrades, Platåberget is designed to operate for several months, providing a reliable environment for stress-testing infrastructure before the upgrade moves to long-standing testnets like Sepolia and Hoodi, and eventually, the Ethereum mainnet.
The deployment of Platåberget comes with critical implications for the broader ecosystem, particularly for application developers and infrastructure providers. While network upgrades routinely adjust consensus and execution mechanisms, the Glamsterdam fork introduces fundamental changes that will immediately impact downstream tooling. Most notably, any software relying on a hardcapped maximum gas limit—including crypto wallets, transaction indexers, and gas estimation tools—will experience disruptions and require substantial updates. Core contributors are strongly urging development teams to utilize this early testing window to identify breaking changes and adapt their systems ahead of wider deployment schedules.
What’s in the Glamsterdam Fork
The Glamsterdam upgrade, tracked collectively through meta EIP-7773, introduces profound architectural modifications across both the consensus and execution layers of the Ethereum network. Platåberget provides a publically joinable validator set, enabling participants to deposit new validators and experiment directly with advanced workflows, including builder deposit procedures. Because ePBS (Enforced Proposer-Builder Separation) represents a major structural shift in how blocks are constructed and proposed on the consensus layer, core developers want to ensure that solo stakers, Distributed Validator Technology (DVT) projects, custom software creators, and large-scale infrastructure operators have ample opportunity to examine their configurations. With the network’s internal fork scheduled to activate on August 20th, stakeholders have a designated timeline to prepare their deposits and align their node architectures.
Beyond consensus modifications, the upgrade implements sweeping gas repricings that reach far beyond validator operations, directly influencing everyday user applications, developer tooling, and automated execution systems. Rather than operating as isolated adjustments, these modifications redefine how execution costs are calculated across the network. The introduction of EIP-8037 establishes a separate state gas dimension specifically targeting operations that expand the global Ethereum state. Under this model, activities that generate new state—such as registering a new account, deploying smart contract code, or writing data to a previously unused storage slot—are metered at a fixed cost per state byte, calculated at runtime rather than billed entirely upfront.
This adjustment fundamentally alters long-standing assumptions regarding basic transaction costs. For instance, a standard native token transfer will no longer maintain a flat, predictable cost of 21,000 gas under every circumstance. While transactions directed toward an account that already exists will retain the traditional 21,000 gas baseline—now systematically decomposed into intrinsic costs, cold account access fees, and value transfer parameters—transfers sent to an uninitialized account will incur additional runtime charges based on the volume of new state bytes created. This operational shift requires wallet providers, indexing services, and gas estimation utilities to move away from single-dimension gas models and update their estimation logic to account for runtime state generation, drawing on the architectural changes detailed in EIP-2780 and EIP-8038.
Using Platåberget
Participants looking to engage with the Platåberget testnet can access comprehensive resources through the official forkcast.org platform, which outlines included Ethereum Improvement Proposals, client support metrics, and launch statuses. Detailed network configurations, bootnode addresses, and client release notes are made available through dedicated documentation channels maintained by core contributors. To simplify deployment, the network provides automated network configuration profiles alongside an active testnet faucet designed to supply developers with test tokens necessary for covering validator deposits and transaction execution fees.
Because official client software releases are actively being prepared by respective client engineering teams, network maintainers have provisioned container images for both execution and consensus layers to support early adopters. The consensus layer lineup includes specialized builds for Lighthouse, Lodestar, Nimbus, Prysm, Teku, and Grandine. Concurrently, the execution layer is supported by specialized container deployments for Besu, Geth, Erigon, Nethermind, Reth, Nimbus EL, and Ethrex. These images allow node operators to spin up dual-client setups immediately and verify compatibility ahead of the scheduled fork transition.
Support, Feedback, and Next Steps
Core developers have established multiple channels for gathering telemetry, identifying software bugs, and refining protocol specifications. Participants encountering implementation hurdles or specification anomalies are encouraged to collaborate within the dedicated Ethereum R&D Discord server or submit technical feedback directly through the relevant open-source repositories covering consensus specifications, execution parameters, execution application programming interfaces, builder specifications, and beacon APIs.
The insights gathered from Platåberget will directly inform subsequent iterations of client software and protocol standards. Following the stabilization of this initial public testnet, core developers plan to launch a non-finality development network within the month to evaluate pathological consensus scenarios and edge-case network behaviors. Once these intermediate test environments demonstrate sustained stability, the upgrade path will progress toward established, long-running testnets such as Sepolia and Hoodi. Only after successful validation across these public testing tiers will the Glamsterdam upgrade be scheduled for deployment on the Ethereum mainnet. For those closely tracking the upgrade cycle, ongoing progress updates continue to be shared through core developer calls, upgrade trackers, and developer documentation repositories.
Ethereum & Smart Contracts
Ethereum & Smart Contracts
Ethereum & Smart Contracts
