The Ethereum Name Service (ENS), one of the most prominent decentralized identity and naming protocols in the blockchain ecosystem, is officially seeking approval from its decentralized autonomous organization (DAO) to activate a major upgraded naming protocol directly on the Ethereum mainnet. This pivotal development marks a significant step forward in the evolution of decentralized digital identities, bringing modernized architecture and enhanced flexibility to millions of human-readable cryptocurrency addresses and decentralized web domains.
Nick Johnson, the founder and lead developer of the Ethereum Name Service, formally submitted an executable draft proposal to the ENS community discussion forums. The proposal outlines the parameters required to activate ENSv2, which represents the next major version of the protocol. If the decentralized community ultimately votes to approve the measure, the upgrade will institute a formal freeze on new registrations occurring on the original ENS registrar contract. However, the proposal ensures a smooth transition and operational continuity by allowing existing domain holders to continue renewing their human-readable names without immediate disruption.
The introduction of ENSv2 brings a heavily redesigned registry architecture designed to optimize domain management and introduce vastly more flexible permissions for users and developers alike. According to the foundational parameters of the upgrade, ENS Labs intends to take a major decentralization step following the activation phase. The development team plans to transfer its remaining administrative control and oversight responsibilities directly over to the upgraded contracts managed entirely by the ENS DAO, further deepening the protocol’s commitment to community-driven governance and decentralized administration.
As part of the technical transition outlined in the draft proposal, brand new ".eth" registrations will permanently migrate to the newly upgraded system once all existing domain records have been fully synchronized between the old and new architectures. Johnson issued a technical advisory warning to the community, noting that new registrations would be temporarily unavailable on either the legacy or the upgraded version of the protocol for a brief period lasting several hours during the migration window. This brief downtime is designed to ensure data integrity and a seamless handoff between the legacy registry and the advanced ENSv2 framework.
For the vast base of current participants and domain investors, the transition has been structured to minimize friction. Existing domain holders are under no immediate obligation to migrate their assets, and their established names will continue functioning completely normally across supported applications and wallets, according to the text of the proposal. Furthermore, ENS Labs has proactively reserved all existing ".eth" names for their rightful current owners on the upgraded system. This thoughtful measure guarantees that users can execute the migration of their assets at their own convenience and when they feel fully prepared to do so, rather than being forced into a rushed timeline.
At present, the activation proposal remains strictly in its draft stage. Before it can be enacted on the blockchain, the initiative must successfully advance through the community pipeline and transition into an official onchain DAO vote for implementation. Under the established governance rules governing the Ethereum Name Service, executable proposals of this magnitude are bound by strict participation thresholds. Specifically, they require a minimum of 1% voter participation—which translates to at least 1 million ENS votes—alongside achieving a clear majority approval during a mandatory seven-day voting period.
Should the proposal successfully pass this rigorous community scrutiny and secure the necessary votes, the upgrade will not take effect instantly. Instead, it will be subject to a mandatory minimum two-day timelock period before final execution on the Ethereum mainnet, providing an additional layer of security and oversight. As of the time of the proposal’s submission, an exact official voting date has not yet been formally announced by the project organizers, leaving community members awaiting further updates regarding the exact timeline for the onchain deployment.
