The Ethereum Name Service (ENS) is taking a major step forward in its protocol evolution, formally seeking approval from its decentralized autonomous organization (DAO) to activate an upgraded naming protocol directly on the Ethereum mainnet. The proposal marks a pivotal milestone for one of the blockchain’s most prominent decentralized identity and domain name projects, paving the way for a modernized technical foundation designed to offer greater flexibility, improved permission structures, and enhanced long-term decentralization.
ENS founder Nick Johnson has officially submitted an executable draft proposal to the community to initiate ENSv2, which represents the next major generational version of the protocol. If the decentralized governance body ultimately grants its approval, the sweeping upgrade will freeze new domain registrations on the original ENS registrar contract. However, the proposal ensures continuity by allowing existing domain holders to continue renewing their human-readable names without interruption under the legacy system, protecting the interests of the existing user base while the ecosystem transitions toward the new architecture.
At the technical core of the ENSv2 upgrade is a completely redesigned registry architecture. This new system is engineered to provide more flexible domain management capabilities and more granular permissions, giving users and developers advanced tools to handle their decentralized identifiers. Furthermore, as part of the transition to a fully community-led model, ENS Labs has outlined plans to transfer its remaining administrative control over the newly upgraded contracts directly to the DAO once the activation process is successfully completed. This move is designed to further decentralize the governance and operational oversight of the protocol, ensuring that it remains a public good governed entirely by its community stakeholders.
Under the mechanics of the proposed rollout, new .eth domain registrations will officially migrate to the upgraded system once all underlying domain records have been successfully synchronized. However, founder Nick Johnson has issued a technical advisory warning to the community, noting that new registrations will be temporarily unavailable on either the legacy or the new version of the protocol for several hours during the active transition window. This brief downtime is a necessary logistical step to ensure data integrity and a seamless migration of the underlying registry state without risking discrepancies between the old and new smart contracts.
For the millions of existing domain holders across the ecosystem, the migration path has been designed to be as frictionless as possible. The proposal explicitly states that current domain owners are not required to migrate immediately, and their existing .eth names will continue functioning normally on the network without any forced action required on their part. To accommodate this flexible approach, ENS Labs has reserved existing .eth names for their current rightful owners on the upgraded system. This ensures that users can comfortably take their time and migrate their domains to the ENSv2 architecture whenever they feel ready, eliminating any pressure or risk of losing their digital identities during the transition period.
At this stage, the activation proposal remains in the draft phase. Before it can be implemented on the live Ethereum network, it must advance through the established governance pipeline and secure a majority green light during an onchain DAO vote. The ENS governance framework dictates strict participation and approval thresholds for executable changes of this magnitude. Specifically, executable proposals require at least one percent voter participation—representing a minimum of one million ENS votes—alongside a majority approval margin during a standard seven-day voting period.
If the community successfully passes the proposal through the voting mechanism, the implementation will still be subject to a mandatory minimum two-day timelock before the code is executed on-chain. This critical safety delay allows all ecosystem participants, developers, and integrated applications sufficient time to review the final execution and prepare their systems for the arrival of ENSv2. As of the time of submission, an official date for the upcoming community vote has not yet been formally announced by the core team or governance facilitators.
