Ethereum's Glamsterdam Testnet Deployment: Key Milestones and Development Progress

The Ethereum development roadmap is advancing with several critical testnet phases approaching completion, according to recent announcements from core developer Christine D. Kim. The ecosystem is preparing for major network upgrades that will involve multiple testnet deployments and technical implementations over the coming weeks.

Hegota Upgrade Proposal Reaches Submission Deadline

The Hegota upgrade proposal has reached its submission deadline on February 4, 2026, marking an important checkpoint in Ethereum’s development cycle. This upgrade represents significant changes that the community must evaluate before implementation. The timeline ensures that all necessary proposals are consolidated and reviewed before proceeding to the next development phase.

Glamsterdam Testnet Phases and Developer Requirements

The Glamsterdam initiative involves multiple testnet launches to validate the proposed changes across different network conditions. The bals-devnet-2 testnet was scheduled for deployment on February 4, requiring developers to finalize two critical Execution API pull requests before the launch window. Following this initial testnet phase, the epbs-devnet-0 testnet is set to arrive at the end of February, incorporating all specifications from the latest consensus specification v1.7.0-alpha.2.

These staged testnet deployments allow developers to identify potential issues and optimize performance across various network configurations before mainnet integration.

Technical Implementation Progress and Client Challenges

Development teams are actively working on implementing partial cell proofs to support an increased capacity for blobs on the Ethereum mainnet. Current testing efforts are underway on the blob-devnet-0 testnet, where the technical specifications are being validated under real-world conditions. However, both the Prysm and Lighthouse client teams have encountered field response issues during these testnet operations, requiring technical adjustments and debugging efforts.

These challenges highlight the complexity of coordinating multiple client implementations while introducing new cryptographic techniques to the protocol. The ongoing testnet phases provide the necessary environment to resolve these technical hurdles before broader deployment.