Ethereum developers have given Glamsterdam more time before its first major public-testnet deployment. During All Core Developers Consensus (ACDC) Call #186 on September 3, client teams agreed to target October 6, 2026 for the Glamsterdam activation on Sepolia, moving away from the earlier September 28 proposal.

The extra week is intended to create room for another round of devnet testing after recent networks failed to deliver the clean fork transition developers wanted to see before moving Glamsterdam onto Sepolia.

• Developers Want Another Stable devnet Before Sepolia
• EIP-8037 Change Will Move Forward
• Sepolia Glamsterdam Moves to October 6, Hoodi Stays Open
• Hegotá EIPs Move Into Client Prioritization

Developers Want Another Stable devnet Before Sepolia

Ethereum developers expect to run another Glamsterdam devnet before the upgrade reaches Sepolia. During ACDC #186, developers discussed a Prysm deployment running against a development branch that did not contain the latest specification changes required by the network.

Alternative branches and devnet 8 images contained the necessary work, but the primary development branch was not yet expected to fork successfully. Optimism had planned to test against devnet 9, while Lido had also requested a stable window around the fork.

Developers therefore leaned toward creating another network once updated images are available. That network exposed problems affecting Lighthouse, Earlier Glamsterdam testing had increasingly shifted in this direction.

The immediate target is not simply another successful devnet launch. It is a clean Glamsterdam transition across clients that gives developers enough confidence to begin public-testnet deployment.

EIP-8037 Change Will Move Forward

Client teams agreed to move forward with the proposed EIP-8037 change after implementations were successfully tested on devnet 8. The decision resolves one of the late technical questions facing Glamsterdam as the upgrade approaches public-testnet deployment.

EIP-8037 deals with state-gas accounting and had returned to discussion after a problem was identified during testing. Because Glamsterdam is already relatively advanced in its development cycle, the important question was not simply whether the behavior could be improved.

Geth and Erigon implemented the proposed change and were able to test it against devnet 8. During ACDC #186, Maria reported that the updated clients successfully synced on the network.

Geth and Erigon supported moving forward. Reth and Nethermind indicated that they would not oppose the majority decision, while Besu and ethrex were also described as supporting the change.

With no substantial objection remaining, developers agreed to adopt it. The next step is to merge the updated specification, allow the remaining execution clients to implement the corresponding behavior and coordinate deployment of the change across the test network.

That coordination matters because Ethereum cannot safely test consensus-critical changes if different clients begin interpreting the same rules differently. The EIP-8037 decision also illustrates the purpose of Glamsterdam’s extended devnet phase.

Sepolia Glamsterdam Moves to October 6, Hoodi Stays Open

Developers agreed to target October 6 for Glamsterdam on Sepolia while leaving the Hoodi activation date undecided. This was the clearest roadmap decision from ACDC #186.

September 28 had previously been discussed as the provisional Sepolia date, with Hoodi tentatively following on October 26. But the latest devnet results changed the risk calculation.

During the call, developers were asked to choose between September 28 and October 6 for Sepolia. Lighthouse considered September 28 workable and was also comfortable with the later option.

Other client representatives were more cautious, arguing that Ethereum should ideally complete another successful devnet transition before moving Glamsterdam onto Sepolia. Nimbus explicitly leaned toward the later date so developers would have another opportunity to observe a clean fork.

Prysm participants also supported separating the Sepolia decision from Hoodi rather than immediately locking both deployments into the roadmap. With client teams broadly comfortable delaying by approximately one week, October 6 became the preferred Sepolia date.

The delay is therefore not a major redesign of the Glamsterdam roadmap. It is a testing buffer. If the expected devnet 10 succeeds, developers gain an additional signal that recent client issues have been addressed before the upgrade reaches Sepolia.

Developers acknowledged during the call that another failed devnet could require a case-by-case assessment, with further discussion possible through ACDT or ACDE before client releases are finalized. The situation around Hoodi is less settled.

An October 26 fork had previously been proposed, but several concerns emerged.

1. First, developers want enough time to observe Glamsterdam operating on Sepolia before moving to another public testnet. One participant suggested that roughly a month of Sepolia operation would provide a more comfortable validation period given the size of the upgrade.
2. Second, October 26 lands shortly before Devcon, creating an operational problem for client teams whose developers may be preparing to travel.
3. Moving Hoodi into that window could leave less room to respond if a problem appeared after activation. November 11 was raised as one possible alternative, but developers did not make a final decision during ACDC #186.

Hegotá EIPs Move Into Client Prioritization

Ethereum client teams are now being asked to rank Hegotá proposals and explain which features they believe deserve implementation priority. That moves Ethereum’s next upgrade another step away from open-ended proposal collection and toward actual scope selection.

Client teams have been asked to prepare tier lists placing Hegotá candidates into priority groups such as S, A, B and lower tiers, accompanied by written explanations for their choices. The rankings were requested around September 10, with further discussions expected across upcoming All Core Developers calls.

A proposal may have strong theoretical benefits but impose considerable implementation complexity. Another may be relatively easy to ship but provide less protocol value. Client developers are in a unique position to judge these trade-offs because they ultimately have to implement, test and maintain the features.

ACDC #186 also provided concrete readiness updates for EIP-8148 and EIP-8205, both of which are Proposed for Inclusion in Hegotá. EIP-8148 would introduce custom sweep thresholds for 0x02 validators.

Under the proposal, validators would not necessarily be forced to use a fixed 2,048 ETH sweep threshold. Instead, they could have greater flexibility around the point at which balances are swept. EIP-8205 has also progressed.

Developers even noted that having no opinion on a proposal can itself become useful information. If an execution client team has no intention of implementing an execution-layer proposal, for example, that lack of support can effectively signal that the EIP should not receive high priority.

If you find any issues in this blog or notice any missing information, please feel free to reach out at yash@etherworld.co for clarifications or updates.

To promote your Web3 articles, events, and projects, you may reach out anytime via EtherWorld PR for submissions and collaboration.

Related Articles

1. Platåberget Testnet Brings Glamsterdam Closer to Mainnet
2. Ethereum Protocol Update: ACDC #184
3. Ethereum Protocol Update: ACDC #183
4. Tracking the Glamsterdam Upgrade on EIPsInsight
5. All You Need to Know About Ethereum Hegotá Upgrade

To follow blockchain news, track Ethereum protocol progress, and read our latest stories, subscribe to our weekly today.

Join the EtherWorld & Avarch Internship Program and build your career in blockchain, content, social media, video, podcast editing, or operations. Send your resume and brief introduction to contact@etherworld.co.