Ethereum Name Service (ENS) is taking a major step toward its next major protocol evolution, seeking approval from its decentralized autonomous organization (DAO) to activate an upgraded naming architecture directly on the Ethereum mainnet. The proposal marks a critical milestone for the widely used decentralized naming and digital identity protocol, setting the stage for modernized infrastructure, enhanced flexibility, and ultimate administrative decentralization.
Nick Johnson, the founder and lead developer of ENS, formally submitted an executable draft proposal aimed at launching ENSv2, which represents the next-generation iteration of the protocol. If the decentralized community votes to approve the measure, the upgrade will set off a carefully coordinated sequence of events. Notably, this will include temporarily freezing new domain registrations on the original ENS registrar while maintaining uninterrupted renewal services for existing domain holders, who will not be required to undergo any immediate migration.
A Redesigned Architecture for Greater Flexibility
At the core of the ENSv2 initiative is a completely redesigned registry architecture. The upcoming version of the protocol introduces vastly improved flexibility when it comes to domain management, granular permissions, and overall smart contract interactions. As the Web3 ecosystem has matured, the architectural limitations of early Ethereum naming infrastructure have become apparent. ENSv2 is designed to address these scaling and management hurdles, ensuring that the protocol can continue serving as a fundamental pillar of decentralized identity for millions of users worldwide.
Furthermore, the activation of ENSv2 serves as a pivotal moment for governance and protocol stewardship. Following the successful deployment and stabilization of the upgraded contracts, ENS Labs has outlined plans to surrender its remaining administrative control. This authority will be handed over entirely to the ENS DAO, reinforcing the project’s long-term commitment to fully decentralized, community-driven governance and operational independence.
Transitioning Registrations and Ensuring Continuity
The deployment of ENSv2 involves a meticulous operational transition to safeguard user assets and prevent disruptions. According to the draft proposal, new .eth registrations will be migrated over to the newly upgraded system once all existing domain records have been fully synchronized.
However, Johnson has issued explicit warnings to the community regarding a brief operational window during the switchover. Specifically, new .eth registrations will be temporarily unavailable on either the legacy or the upgraded version of the system for several hours while the transition takes place. This brief pause is necessary to ensure data integrity and a seamless handoff between the smart contract layers.
Despite this brief downtime for new names, existing domain holders will enjoy a frictionless experience. The proposal explicitly states that current domain owners are under no obligation to migrate their assets immediately. Their existing .eth names will continue to function normally without interruption. To provide additional peace of mind, ENS Labs has reserved all existing .eth names for their rightful current owners on the new system, ensuring that users can execute their migration at their own convenience whenever they feel ready.
The Governance Process and Voting Requirements
Before any of these changes can take effect on the Ethereum mainnet, the activation proposal must successfully navigate the ENS DAO governance lifecycle. The initiative is currently in the draft stage, meaning it must gather community feedback and refine its parameters before advancing to an official onchain DAO vote.
Under the established governance rules governing the ENS ecosystem, executable proposals face strict requirements to ensure broad consensus and legitimate community backing. Specifically, any proposal of this magnitude requires a minimum of 1% voter participation—representing at least one million ENS votes—alongside a decisive majority approval during a mandatory seven-day voting window.
Should the community vote in favor of the upgrade, the proposal will not be implemented immediately. Instead, it will be subjected to a mandatory minimum two-day timelock period before the code is officially executed on the network, providing an essential safety buffer for network participants and developers. As of the submission of the draft, an official start date for the voting period has not yet been announced by the core team or governance facilitators.
