The primary keyword for this update is Ethereum Platåberget testnet. The Ethereum Foundation announced on August 17, 2026 that it is opening the Platåberget testnet as the early testing ground for the Glamsterdam upgrade (Gloas + Amsterdam). The testnet is open to public participation and intended to run for a few months before Glamsterdam moves to the longer-lived Sepolia and Hoodi testnets.
What Happened
The Ethereum Foundation announced on August 17, 2026 that it is opening the Platåberget testnet as the early testing ground for the Glamsterdam upgrade (Gloas + Amsterdam). The testnet is open to public participation and intended to run for a few months before Glamsterdam moves to the longer-lived Sepolia and Hoodi testnets.
The event dates above come from the cited sources; this page was checked against those sources on August 18, 2026 UTC before publishing. The event date and the publish date are intentionally separated: the event date comes from the cited source, while this page is published in UTC during the August 18 news window.
Why It Matters
Platåberget includes breaking changes for application developers: gas repricings aimed at a ~200M gas floor break any tool that hardcodes a maximum gas limit, wallets, indexers and gas estimators are all affected, EIP-7732 enshrined proposer-builder separation changes block production and validation, and the Glamsterdam fork on the testnet is scheduled for August 20. For Radar this is a protocol-operations signal: node operators, validators and dapp teams should test against the new consensus and execution assumptions before the fork reaches mainnet.
The owner fit controls the framing. Exchange and venue events stay on CryptoSigy as listing, liquidity, fee or contract-risk context; protocol and ecosystem events stay on Radar when the useful question is chain operations, governance or security infrastructure.
What To Watch Next
Watch validator and builder deposit workflows, client image tags for both layers, how wallets and indexers handle the new gas model, and the move of Glamsterdam to Sepolia and Hoodi before mainnet.
If the official source updates contract specs, fee terms, deadlines, block heights or protocol details, rebuild the decision from the updated source rather than from a stale headline.
The editorial filter is protocol operations, testnet, node and dapp readiness for a consensus and execution fork.. Treat this as decision context, not as a prediction, recommendation or promotional note.
Date discipline matters: published and updated timestamps are generated at publish time in UTC, while event dates in the body come from the cited source.
Risk reminder: betting and crypto decisions can cause financial loss. Use official sources, keep stakes or position sizes controlled, and avoid treating one update as a complete strategy.
Before acting on the update, compare the official notice with the live product, market or protocol surface. If contract specs, fee terms, route availability, lineup status or governance details differ, the live source should override the older assumption.
The practical output is a watchlist, not a verdict. Readers should know which timestamp, rule, venue field or protocol dependency must be checked next before the update has any operational value.
Continue this cluster
Continue this cluster with related source-backed updates that keep the same owner-specific decision frame.
