Overview of the Glamsterdam Upgrade
Ethereum’s development team has tentatively set the date of October 6, 2026, at 13:53 UTC for the anticipated Glamsterdam upgrade on the Sepolia testnet. However, this is not yet a firm commitment, as the upgrade’s success hinges on additional testing to be conducted on a private development network.
Current Testing and Development Focus
Findings from ACDC #186 and insights from Ethereum researcher Christine D. Kim reveal that the current timeline is conditional. At the time of selecting this date, developers had not confirmed stable performance on previous private test networks.
On September 11, Kim indicated that the focus is now on Glam-Devnet-11, which is slated for deployment on September 14, succeeding the previous Devnet-10 plans that have since evolved. She emphasized that the initial caution regarding the October 6 date remains, with the primary concern now being directed towards the outcome of Devnet-11.
Activation Epoch and Concerns
No definitive activation dates have emerged for either the Hoodi testnet or the Ethereum mainnet, although discussions of a possible mainnet launch in December are in the air, contingent on the results from the ongoing tests.
In a recent All Core Developers meeting conducted on September 3, the participants designated the activation epoch for Sepolia as 351232, aligning with the proposed date of October 6. This epoch selection provides a focal point for client teams, infrastructure operators, and application developers; however, it does not guarantee the upgrade will occur on that date, as any discovered faults or readiness concerns could lead to a postponement.
Challenges in Testing
This concern arises in light of the issues encountered in previous test environments, notably with Devnet-9 experiencing significant finality failures. Finality, a critical component for the successful processing of transactions, relies heavily on sufficient agreement among validators. When a test network faces finality issues, developers must diagnose whether the problems stem from client software, validator participation, the network setup, or inherent interactions among multiple protocol adjustments.
Initially, the plan had progressed towards Devnet-10 after issues were discovered in earlier trials, but Kim has confirmed that attention has now shifted to Devnet-11, suggesting advancements in the sequence of private tests. A reliable Devnet-11 setup could offer Ethereum client teams another viable testing environment for the integrated Glamsterdam specifications.
Importance of Client Stability
These specifications are crucial for layer-2 teams, staking providers, and other infrastructure operators, as reliable client implementations are necessary for them to effectively test their systems against potential changes. Furthermore, the complexity of Ethereum’s client diversity complicates the testing process, as multiple independently developed execution and consensus clients must be consistently interoperable. A fault in any single client can cause disruptions if those validators play a significant role in the network’s operation.
Requests for stability before executing a fork have also been noted, with Lido and Optimism advocating for at least one day of stability prior to any potential upgrade. Crucial aspects like client fixes and successful interoperability need to be verified ahead of the planned Sepolia activation.
Future Considerations
While stability issues in Devnet-11 wouldn’t necessarily halt the October 6 activation, developers would need to investigate the underlying cause and the time required for adjustments. Significant issues could prompt a reassessment of the timeline during subsequent developer meetings.
The history of Glamsterdam trials revealed challenges on both ends of Ethereum’s architecture, including a consensus-layer problem reported during Devnet-8. Additionally, issues associated with EIP-8037 were identified by Ethereum researchers, necessitating revisions in execution client implementations. This proposal focuses on adjusting how gas fees are calculated for new state creation, which includes new accounts and contracts.
Importantly, the testing phase aims not just to ratify individual proposals but to ensure that all selected changes function cohesively across varied client configurations and transaction scenarios. Developers have opted not to set a date for the Hoodi testnet while Sepolia remains subject to conditions, as Hoodi will later serve as a second public testnet phase aligning more closely with mainnet conditions.
Conclusion
Ultimately, the push towards a potential December mainnet activation holds promise but is not finalized. The schedule for Sepolia seeks to accommodate a second public testnet phase and client release readiness, pending test progress in the upcoming weeks. To sum up, as the launch of Devnet-11 approaches on September 14, client teams will closely monitor aspects like finality, cross-client behavior, and newly implemented fixes as they evaluate whether Sepolia can maintain its current schedule.
