Ethereum core developers have locked in Oct. 6, 2026, as the date to test the network’s next major upgrade, Glamsterdam, on the Sepolia testnet — but they are heading into the trial with an explicit warning attached. During a core developer call on Thursday, Sept. 17, 2026, consensus developer Potuz and colleagues cautioned that malicious actors could exploit fake builder identities to win block auctions and then withhold transaction data, a maneuver that could freeze traffic on the test network and derail the rehearsal before it produces useful results.
The stakes go beyond a single testnet run. Glamsterdam is the upgrade meant to give Ethereum meaningfully more capacity per block, and how cleanly it clears testing will shape when, and how confidently, it can move toward the live network.
What Glamsterdam Changes
Glamsterdam’s defining shift is architectural: it moves the relationship between validators and block builders directly into Ethereum’s own protocol rules, rather than leaving it to the informal, off-chain arrangements that have governed block building since the rise of maximal extractable value markets. Under this design, builders compete through bids to assemble the transactions that go into each block, and the protocol itself enforces the rules of that competition instead of relying on external infrastructure and trust assumptions.
That redesign is also what creates the vulnerability developers flagged this week. Because builder identity and bidding now sit inside the protocol, someone posing as a legitimate builder — a fake identity — could win an auction for the right to build a block and then simply refuse to hand over the transaction data needed to complete it. On a live test network, that kind of withholding could stall block production and disrupt the very process meant to validate the upgrade.
The capacity goal behind all this is concrete: Glamsterdam targets a block gas limit of roughly 200 million, a substantial increase designed to let the network process more activity per block. Notably, a large private rehearsal completed the full Glamsterdam transition just one day before the developer warning was issued, successfully raising the gas limit toward that 200 million target without any loss of finality — a sign the core mechanics can work under controlled conditions, even as the public testing path carries its own risks.
A Compressed Timeline
The schedule developers have set leaves little room for error. Client teams building Ethereum’s software must release Sepolia-ready versions by Sept. 29, 2026, just seven days before the Oct. 6 fork. That is half the 14-day window that has typically been reserved for security review before a network upgrade, a compression that raises the bar for how thoroughly bugs and edge cases can be caught before the test goes live.
Complicating matters further, production builder software from two teams, Titan and Ultrasound, has not yet completed the Glamsterdam transition. Their absence from full readiness heading into the test underscores how much coordination across independent teams this upgrade demands — and how a single lagging piece of software can leave the broader rollout more exposed. If the Oct. 6 Sepolia test does not go smoothly, developers have already penciled in a second public trial, tentatively for Oct. 27, 2026, on the Hoodi testnet. No date has been set for deploying Glamsterdam to Ethereum’s mainnet, and the developers’ cautious posture suggests they are unwilling to commit to one until the builder-identity issue and related risks are better understood.
Why the Stakes Are Real for Ethereum
Ethereum has spent years hardening its infrastructure against exactly this category of problem: bad actors exploiting whatever trust assumptions a new mechanism introduces. Moving builder-validator relationships on-chain is meant to reduce reliance on off-chain infrastructure, but it also means any flaw in how the protocol verifies builder identity becomes a protocol-level risk rather than a peripheral one. A successful attack during testing would not compromise real funds on Sepolia, since it is a test network, but it would cost something arguably just as valuable at this stage: time and confidence. A stalled or inconclusive Oct. 6 test could push back the Hoodi trial’s usefulness, delay client teams’ remaining engineering work, and ultimately extend the runway before Glamsterdam is ready for mainnet.
For an ecosystem where infrastructure resilience has been under scrutiny — as seen in unrelated incidents like the recent breach exposing weaknesses in institutional crypto plumbing — a smooth Glamsterdam test would be a meaningful signal that Ethereum’s core development process can absorb new attack surfaces without losing schedule discipline. A rocky one would raise fresh questions about how ready the network is to take on a more complex builder market at scale.
What to Watch
- Whether client teams meet the Sept. 29 software-readiness deadline with enough runway for review.
- Whether Titan and Ultrasound complete their Glamsterdam transitions in production builder software before Oct. 6.
- How the Sepolia test network handles any attempted fake-builder attack on Oct. 6, and whether block production is disrupted.
- Whether a second test on the Hoodi testnet proceeds as tentatively planned for Oct. 27.
- Any subsequent announcement of a mainnet activation date for Glamsterdam once testing concludes.
Source: CoinDesk
This content is for informational purposes only and does not constitute financial or investment advice.
Create a free account to comment and earn rewards.
Create account Log in