What to Know
- Ethereum developers confirmed an Oct. 6 public Sepolia test for the Glamsterdam upgrade.
- Developers warned that free test ether and disposable builder identities could let malicious operators win block auctions and withhold payloads.
- The risk does not threaten mainnet funds because the concern is centered on Sepolia, a test network.
- Glamsterdam is designed to support a block gas limit of about 200 million while helping Ethereum fit more activity into each block.
- Client teams have until Sept. 29 to release Sepolia ready software, leaving seven days before the fork.
- That review window is half the 14 days normally reserved in Ethereum’s upgrade process for security reviews and bug bounty testing.
- A Hoodi public test is tentatively planned for Oct. 27, while mainnet activation remains unscheduled.
Ethereum Sets Glamsterdam Testing Schedule
Ethereum developers have confirmed the next major public step for the Glamsterdam upgrade, setting an Oct. 6 test on Sepolia while also raising a warning about how the new block building design could be abused in a low cost testing environment. The concern focuses on malicious or unserious builders using free test ether and disposable identities to dominate block auctions, then failing to deliver the transaction payloads that validators expect after accepting a winning bid.
The issue is not being framed as a direct risk to mainnet funds. Sepolia is a public test network, and its test ether has no meaningful financial cost. That distinction matters because the scenario under discussion would not allow an attacker to steal user assets on Ethereum mainnet. Instead, the risk is operational. If malicious builders repeatedly win auctions and withhold payloads, they could interfere with the infrastructure testing that client teams, builder teams, validators and other ecosystem participants need before Glamsterdam can be considered ready for Ethereum itself.
Glamsterdam is one of Ethereum’s most important upcoming protocol upgrades because it is intended to help the network process more activity inside each block without pushing verification requirements beyond what ordinary network participants can handle. The upgrade is associated with changes to gas pricing and a target block gas limit of about 200 million. In practical terms, that would create more room for payments, trading activity and application usage before users are forced to compete as aggressively through higher fees.
Why Fake Builders Are a Testnet Problem
The warning centers on how Ethereum’s block production pipeline changes under Glamsterdam. The upgrade moves the relationship between validators and specialized block builders into Ethereum’s protocol. Builders assemble blocks of transactions and compete to provide them. Validators select a winning bid, after which the builder is expected to reveal the underlying transaction payload that makes the block usable.
On mainnet, economic costs and reputational concerns can discourage reckless behavior. On Sepolia, those constraints are weaker. Test ether is free and does not carry the same economic value as ETH on mainnet. That means a malicious operator can bid unrealistically high amounts with little consequence. If that operator also uses many disposable builder identities, it becomes harder for clients to rely on simple reputation assumptions. A bad actor could win repeatedly, refuse to deliver payloads and then reappear under another identity.
Ethereum consensus developer Potuz described the risk in direct terms during a core developer call, saying an operator could spin up a thousand builders, rotate them, offer very high bids and then fail to produce payloads. Potuz added that any teenager could do this, emphasizing that the attack does not require deep capital or sophisticated access when the environment is a public testnet with free test ether.
The result would be disruptive rather than financially catastrophic. Blocks could be left without transaction payloads, forcing clients to rely on fallback behavior. Developers indicated that current safeguards may fall back to locally built blocks only after several payloads go missing. That delay could be enough to make testing noisy, reduce confidence in results and slow the process of validating the upgrade’s infrastructure assumptions.
Client Teams Face a Shorter Review Window
The timing adds pressure. Client teams now have until Sept. 29 to release software ready for the Sepolia fork. That leaves seven days before the Oct. 6 test. Ethereum’s normal upgrade process reserves 14 days for security reviews and bug bounty testing, meaning teams are working with half the usual review period for this stage.
Developers accepted the tighter schedule partly because Sepolia is relatively centralized and easier to recover if a fault emerges. That does not eliminate the need for careful testing, but it changes the risk calculation. A public testnet failure can be disruptive and embarrassing, yet it is far less dangerous than a mainnet incident. For Ethereum’s upgrade process, Sepolia serves as a place to expose implementation problems, coordination gaps and unexpected edge cases before the network moves toward production deployment.
The shortened review window also comes with another complication. Production builder software operated by teams Titan and Ultrasound has not completed a Glamsterdam fork transition. That leaves an additional gap between test readiness and mainnet readiness. Even if Sepolia proceeds as scheduled, developers will still need to assess whether the broader builder ecosystem can safely handle the transition under more realistic conditions.
Recent Rehearsal Cleared a Major Capacity Step
The warning about fake builders follows a large private rehearsal that completed the Glamsterdam transition and raised the block gas limit toward 200 million without losing finality. That result gave developers a positive signal on the upgrade’s basic transition mechanics. Finality is a core property for Ethereum because it indicates that blocks have become accepted by the network’s consensus process in a way that is not expected to be reversed under normal conditions.
Still, a successful private rehearsal does not remove the need for public testnet trials. Private environments can be controlled more closely, while Sepolia introduces broader participation and more unpredictable behavior. That is precisely why the fake builder issue matters. Public testnets are useful because they expose upgrades to less tidy conditions. They can also attract opportunistic activity from participants who want to probe weak points, stress assumptions or simply cause disruption.
For Glamsterdam, the builder component is especially important because the upgrade changes where builder and validator interactions sit in Ethereum’s architecture. When a protocol change formalizes a process that previously depended on external infrastructure, the client layer must handle more responsibility. Developers are therefore focused not only on whether blocks can be built, but also on whether clients can detect, reject and route around builders that behave maliciously or unreliably.
What Developers Need to Solve
One immediate focus is builder identification and rejection. Potuz indicated that clients need to identify and reject individual builders so an attacker cannot simply return under a fresh identity and continue winning auctions. That is a difficult problem in an open network. Permissionless systems aim to avoid centralized gatekeeping, yet they still need ways to reduce repeated abuse when participants are cheap to create and easy to discard.
Technical traders and market participants often watch Ethereum upgrades for potential effects on throughput, fees and network utility, but the current discussion is primarily about engineering reliability. Glamsterdam’s promise of more capacity depends on safe execution. If public testing shows that payload withholding is easy to trigger and hard to contain, developers may need to refine client behavior or test procedures before confidence can build around a later mainnet activation.
The next public test after Sepolia is tentatively planned for Oct. 27 on Hoodi. Developers will decide whether to keep that date after observing Sepolia. That sequencing gives teams a chance to incorporate lessons from the Oct. 6 event, especially if the fake builder scenario materializes or if unexpected client behavior appears during the fork.
Mainnet activation remains unscheduled. That is typical for a major Ethereum upgrade still moving through public testing. Developers generally avoid committing to a mainnet date until testnet results, client releases and ecosystem readiness are sufficiently aligned. In Glamsterdam’s case, the state of production builder software and the response to malicious testnet behavior are likely to be important factors in determining when the upgrade can move closer to Ethereum mainnet.
Why Glamsterdam Matters for Ethereum Users
For ordinary Ethereum users, the immediate Sepolia test will not change wallet balances or mainnet transactions. The broader upgrade, however, is important because capacity remains a central issue for the network. When demand rises, users compete for block space through fees. An upgrade designed to fit more activity into each block could improve the user experience by creating more room for transactions before fee pressure intensifies.
The goal is not simply to raise capacity at any cost. Ethereum client teams must ensure that validators can still verify blocks without being overwhelmed. If blocks become too demanding to process, decentralization can suffer because fewer participants are able to run infrastructure. Glamsterdam’s design challenge is therefore about balancing throughput with the practical limits of the machines that secure the network.
The fake builder warning shows how capacity upgrades can create new coordination and security questions. Increasing throughput is only one part of the work. Developers must also make sure the systems that assemble, propose and validate blocks can behave safely under adversarial conditions. On a public testnet where identities are cheap and assets have no meaningful cost, those adversarial conditions can appear quickly.
Market Takeaway
FXCOINZ views the Glamsterdam testing schedule as a meaningful milestone for Ethereum’s technical roadmap, but the builder abuse warning underscores that the upgrade is not yet in a mainnet ready phase. The Oct. 6 Sepolia test will be closely watched for whether clients can maintain reliable block production, detect missing payloads and limit disruption from malicious builders using disposable identities.
If Sepolia proceeds smoothly, attention will shift to the tentatively planned Oct. 27 Hoodi test and the remaining work needed from production builder teams. If Sepolia is disrupted, developers may need to adjust client safeguards before moving forward. In either case, the absence of a mainnet activation date signals that Ethereum’s process remains conditional on evidence from testing rather than a fixed calendar.
Frequently Asked Questions (FAQs)
What is the Glamsterdam upgrade?
Glamsterdam is Ethereum’s next major upgrade, designed to help fit more activity into each block while supporting a block gas limit of about 200 million and changing how validators and specialized builders interact within the protocol.
When is the Sepolia test scheduled?
The public Sepolia test for Glamsterdam is scheduled for Oct. 6. Client teams have until Sept. 29 to release software ready for that test.
Does the fake builder risk threaten Ethereum mainnet funds?
No. The warning concerns Sepolia, a test network where test ether has no meaningful cost. Developers described the issue as a disruption risk for testing, not as a threat to mainnet funds.
How could fake builders disrupt Sepolia?
Malicious builders could use free test ether to place very high bids, win block auctions and then refuse to reveal the promised transaction payload. Repeating that behavior could leave blocks without payloads and interfere with testing.
Why are disposable builder identities a concern?
If builders can easily return under new identities after behaving maliciously, clients may struggle to block repeated abuse. Developers want clients to identify and reject bad builders more effectively.
Why is the review window considered short?
Client teams have seven days between the Sept. 29 software release deadline and the Oct. 6 Sepolia fork. Ethereum’s normal upgrade process reserves 14 days for security reviews and bug bounty testing.
What happened in the private Glamsterdam rehearsal?
A large private rehearsal completed the Glamsterdam transition and raised the block gas limit toward 200 million without losing finality, giving developers a positive but still limited signal before public testing.
When is the Hoodi test planned?
The next public test on Hoodi is tentatively planned for Oct. 27. Developers will decide whether to keep that date after reviewing how Sepolia performs.
Is there a mainnet activation date for Glamsterdam?
No. Mainnet activation remains unscheduled, and developers are expected to base the next steps on public test results, client readiness and builder ecosystem preparedness.