The Ethereum Name Service (ENS), the leading decentralized domain name provider in the Web3 ecosystem, is moving closer to a major infrastructural evolution. Nick Johnson, the founder and lead developer of ENS, has officially submitted an executable draft proposal to the project’s decentralized autonomous organization (DAO) to activate ENSv2, the highly anticipated next iteration of the protocol on the Ethereum mainnet. The proposal marks a pivotal step in modernizing the architecture behind human-readable Ethereum addresses, promising enhanced flexibility, refined permission structures, and long-term scalability for millions of domain holders across the globe.
If the decentralized community grants its approval, the sweeping upgrade will introduce substantial structural modifications to how .eth domain names are registered, managed, and maintained. Most notably, the activation of ENSv2 would immediately freeze new domain registrations on the original ENS legacy registrar. However, to ensure a seamless and disruption-free experience for the existing user base, current domain holders will retain the uninterrupted ability to renew their existing names directly on the legacy system without being forced into an immediate migration.
At the heart of the ENSv2 upgrade is a completely redesigned registry architecture. This new system is engineered to provide developers and users with vastly more flexible domain management capabilities and granular permission controls. As part of this architectural shift and the broader decentralization roadmap, ENS Labs has outlined intentions to relinquish its remaining administrative control over the upgraded smart contracts, transferring full authority directly to the ENS DAO once the transition is successfully finalized.
The mechanics of the transition have been carefully mapped out by the protocol’s core developers to minimize friction while safeguarding user assets. According to the proposal, brand-new .eth registrations will eventually transition over to the newly upgraded system, but this shift will only occur once all existing domain records have been fully and securely synchronized between the old and new architectures. Johnson has issued a technical advisory warning to the community, noting that new registrations will be temporarily paused and unavailable on either version of the protocol for a brief window lasting several hours during the peak of the cutover transition.
Despite this brief operational pause for incoming registrations, the thousands of individuals and organizations currently holding .eth names face no immediate pressure to alter their workflows. The proposal explicitly guarantees that existing domain holders are under no obligation to migrate their assets immediately. Their existing names will continue to resolve and function normally under the current infrastructure. Furthermore, to protect user interests and prevent front-running or loss of valuable domain assets, ENS Labs has reserved all existing .eth names for their rightful current owners within the upgraded system. This thoughtful grace period ensures that users can comfortably migrate their domains to the new framework at their own convenience and discretion, rather than rushing through a mandatory deadline.
Before any of these structural changes can be written onto the blockchain, the activation proposal must successfully navigate the DAO’s established governance pipeline. The initiative currently sits in the draft stage and must formally advance to an official onchain DAO vote before implementation can commence.
Governance within the ENS ecosystem is governed by strict, transparent rules designed to ensure that major protocol changes reflect genuine community consensus. Under the current governance guidelines established by the DAO, executable proposals of this magnitude require a minimum voter participation threshold of at least 1%, which translates to 1 million ENS votes cast. Additionally, the proposal must secure a majority approval from participating voters during a mandatory seven-day voting period. If the community ultimately votes in favor of the upgrade, the deployment will still be subject to a strict minimum two-day timelock period before the execution code can be triggered on the mainnet. As of press time, an exact date for the commencement of the onchain vote has not yet been formally announced by the core team.
