The Ethereum Name Service (ENS) is taking a major step toward its next evolutionary phase, as founder Nick Johnson has submitted an executable draft proposal to the project’s decentralized autonomous organization (DAO) to activate ENSv2 on the Ethereum mainnet.
The proposal marks a pivotal moment for the widely utilized Web3 naming protocol, setting the stage for a modernized architecture designed to offer enhanced flexibility in domain management and permissions. If the community votes to approve the upgrade, it will introduce a series of structural changes to how .eth domains are registered and managed, while implementing careful transition protocols to safeguard existing users and their digital assets.
Under the terms of the newly submitted executable draft, the activation of ENSv2 would immediately freeze new domain registrations on the original ENS registrar. However, the proposal ensures continuity for the existing user base by allowing current domain holders to continue renewing their .eth names without being forced into an immediate migration. This design aims to mitigate user friction and prevent the kind of widespread disruption that major smart contract upgrades can sometimes trigger across decentralized networks.
Redesigned Architecture and Administrative Handover
The core motivation behind ENSv2 lies in its redesigned registry architecture. The upgrade introduces a more flexible framework for domain management and permissions, positioning the protocol to better scale and adapt to future demands within the broader blockchain ecosystem.
As part of this architectural shift, ENS Labs plans to relinquish its remaining administrative control over the upgraded smart contracts, transferring full authority directly to the ENS DAO. This move aligns with the project’s long-term commitment to full decentralization, ensuring that governance and protocol evolution remain entirely in the hands of the community.
The transition process itself has been mapped out to balance technical efficiency with user convenience. According to the proposal, new .eth registrations will be shifted over to the upgraded system once all existing domain records have been successfully synchronized. However, founder Nick Johnson has issued a technical warning regarding the exact moment of activation: new registrations will be temporarily unavailable on either the old or the new version for a period of several hours while the system transition is actively underway.
Protection for Existing Domain Holders
One of the central concerns for any protocol upgrade involving digital identities is the safety and continuity of existing holdings. The ENSv2 proposal explicitly addresses this by confirming that current domain holders are under no obligation to migrate their names immediately. Existing .eth domains will continue to function normally on the legacy system without interruption.
Furthermore, ENS Labs has proactively reserved existing .eth names for their current owners within the upgraded system architecture. This ensures that users retain exclusive rights to their specific domain names on the new network layer, allowing them to complete the migration process at their own convenience and when they feel fully prepared to do so.
The DAO Governance and Voting Process
Before any of these changes can take effect, the activation proposal must successfully navigate the ENS DAO’s established governance framework. The initiative currently sits in the draft stage on the community governance forum, where stakeholders can review, discuss, and debate the technical parameters of the upgrade.
To transition from a draft to active implementation, the proposal must advance to an onchain DAO vote. ENS governance rules dictate strict criteria for executable proposals of this magnitude. Specifically, the vote requires a minimum voter participation threshold of 1%—representing at least 1 million ENS votes—alongside a majority approval during a mandatory seven-day voting window.
Should the community vote to pass the proposal, the upgrade will not take effect immediately. Instead, it will be subject to a mandatory minimum two-day timelock period before the execution code can be deployed on the Ethereum mainnet. As of publication, an official date for the start of the governance vote has not yet been announced by the project team.
