The decentralized identity and domain protocol Ethereum Name Service (ENS) is taking a decisive step toward its next evolutionary phase. ENS founder Nick Johnson has formally submitted an executable draft proposal to the project’s decentralized autonomous organization (DAO), seeking approval to activate an upgraded naming protocol directly on the Ethereum mainnet. The proposal marks a critical milestone for the infrastructure project, setting the stage for a modernized architecture designed to offer enhanced flexibility, improved permission management, and a complete handover of administrative control to the community.
Under the terms of the draft proposal, the activation of ENSv2 will introduce sweeping structural changes to how human-readable Ethereum addresses are managed, registered, and maintained on-chain. If the community votes to approve the initiative, the upgrade will immediately freeze new domain registrations on the original ENS registrar contract. However, this freeze will not disrupt current users; existing domain holders will retain the full ability to continue renewing their .eth names without interruption, ensuring a stable environment for legacy assets while the new system is phased in.
The core of the upgrade centers on a redesigned registry architecture. This new framework has been built to provide significantly more flexible domain management and advanced permissioning capabilities, addressing structural limitations in the original protocol design. Furthermore, as part of the transition to a fully decentralized operational model, ENS Labs has outlined plans to transfer its remaining administrative control over the upgraded contracts directly to the DAO once the deployment is successfully completed. This move is intended to further entrench the project’s governance within its decentralized community of token holders.
Transition Logistics and User Impact
Managing a protocol upgrade of this scale on a live blockchain requires meticulous timing, and the proposal outlines specific procedures to handle the migration of the .eth namespace. Once the underlying domain records have been fully synchronized with the upgraded system, all new .eth registrations will officially transition to the new architecture.
During the active transition phase, however, users should anticipate a brief operational window where new registrations will be temporarily unavailable on either version of the protocol. Johnson warned the DAO that this synchronization and transition period is expected to last for several hours, during which time the creation of fresh domain names will be paused.
Despite the technical shift, the proposal emphasizes that existing domain holders are under no obligation to migrate immediately. For users who prefer to maintain the status quo, their current names will continue functioning normally under the legacy system parameters. To ensure a seamless user experience and protect existing stakeholders, ENS Labs has proactively reserved all existing .eth names for their current rightful owners on the upgraded system. This precautionary measure allows individual users to choose their own timeline, enabling them to execute their migration to ENSv2 whenever they feel ready, without the pressure of a strict deadline or the risk of losing their domain squatting rights.
Governance Process and Next Steps
Before any of these architectural and operational changes can take effect, the activation proposal must clear several procedural hurdles within the ENS governance framework. Currently resting in the draft stage, the initiative is required to advance through formal community discussion before it can be packaged and submitted for an official onchain DAO vote.
The governance rules governing the ENS DAO dictate stringent criteria for executable proposals of this magnitude. To pass, the proposal must secure at least 1% voter participation—representing a minimum of 1 million ENS votes cast—alongside a majority approval during a strictly mandated seven-day voting period. Should the community vote in favor of the upgrade, the implementation will still be subject to a mandatory minimum two-day timelock period before the code can be executed on the Ethereum mainnet, providing a final safety buffer for the network. As of the submission of the draft, an official voting date has not yet been announced by the core team or community delegates.
