The Ethereum Name Service (ENS) is taking a major step toward the future of decentralized digital identifiers by seeking formal approval from its decentralized autonomous organization (DAO) to activate an upgraded naming protocol directly on the Ethereum mainnet. This pivotal development marks a significant milestone in the evolution of the protocol, which has become a foundational pillar for human-readable addresses within the broader Ethereum ecosystem.
Nick Johnson, the founder of ENS, has officially submitted an executable draft proposal aimed at bringing ENSv2—the highly anticipated next version of the protocol—to life. If the decentralized community grants its approval, the sweeping upgrade will introduce profound structural changes to how domains are registered, managed, and governed on the network. Most notably, the activation proposal outlines a plan to freeze new domain registrations on the original ENS registrar while ensuring that existing domain holders experience uninterrupted service, maintaining the full ability to renew their names as they have always done.
At the heart of the ENSv2 upgrade is a completely redesigned registry architecture. This new infrastructure is engineered to deliver significantly more flexible domain management capabilities alongside advanced permission structures. By modernizing the underlying smart contracts, ENS aims to empower users and developers with a more robust and adaptable framework for decentralized naming. Furthermore, as part of the transition to a fully decentralized operational model, ENS Labs has outlined its intention to transfer its remaining administrative control over the newly upgraded contracts directly to the DAO once the activation process is successfully completed.
The transition plan addresses the mechanics of how new dot-eth registrations will move into the modern era. Once the underlying domain records have been fully synchronized with the upgraded system, all new .eth registrations will seamlessly shift to the new architecture. However, Johnson has issued a technical advisory warning participants that new registrations will be temporarily unavailable on either version for a duration of several hours during the critical synchronization window. This brief downtime is designed to ensure data integrity and a smooth handoff between the legacy and modern systems.
For the vast majority of current participants, the upgrade has been designed with maximum convenience and backward compatibility in mind. Existing domain holders are not required to undergo any mandatory migration process to keep their names secure. According to the text of the proposal, current names will continue to function entirely normally without disruption. To alleviate any anxiety regarding the safety of valuable digital assets, ENS Labs has proactively reserved existing .eth names for their current owners on the upgraded system. This thoughtful measure guarantees that users can choose to migrate their assets at their own pace and convenience when they feel fully ready to do so.
Presently, the activation proposal firmly resides in the draft stage of the governance lifecycle. Before any code can be executed on the network, the initiative must successfully advance through the formal community discussion phase and proceed to an onchain DAO vote. The decentralized nature of the project means that the ultimate fate of the upgrade rests squarely in the hands of the token holders and community members who participate in the governance process.
Under the established governance rules governing the ENS ecosystem, executing proposals of this magnitude is subject to strict participation and approval thresholds. Specifically, the rules require at least 1% voter participation—representing a minimum threshold of 1 million ENS votes—alongside a clear majority approval during the designated seven-day voting period. Should the proposal clear this vital hurdle and secure the necessary majority, the upgrade will not take effect immediately. Instead, it will be subjected to a mandatory minimum two-day timelock period before final execution on the mainnet, providing a final safety buffer for the community. As of the submission of the draft, an official voting date has not yet been formally announced to the public, leaving stakeholders to monitor the discussion forums for upcoming scheduling updates.
