ENS Founder Nick Johnson Files ENSv2 Activation Draft Ahead of Seven-Day DAO Vote

Nick Johnson files ENSv2 activation draft

The Ethereum Name Service (ENS) has put its largest structural change on the table, and the measure is still a draft, not a decided upgrade. ENS founder Nick Johnson submitted an executable proposal to activate ENSv2, the second version of the naming protocol, on the Ethereum mainnet, and the draft now awaits approval from the decentralized autonomous organization (DAO) that governs the system. The proposal text, published on the ENS governance forum, states that activation would freeze new registrations on the original ENS registrar while leaving renewals for existing names untouched. ENS serves as the naming layer of the Ethereum ecosystem: it maps human-readable names such as example.eth to addresses and other records, and each .eth name is held as an NFT, so a registry change touches both resolution and ownership. ENSv2 introduces a redesigned registry architecture with more flexible domain management and permissions. ENS Labs, the development company behind the protocol, plans a change of its own once activation completes: it would transfer its remaining administrative control over the upgraded contracts to the DAO, ending the operational authority it still holds over the system. Clearing the vote is the gate. Under the governance process documented by the ENS DAO, an executable proposal requires at least 1% voter participation, equal to 1 million ENS votes, alongside majority approval during a seven-day voting period. Even a favorable result would not trigger execution immediately: the upgrade faces a minimum two-day timelock before it can take effect. No voting date has been announced, and the draft must still advance to an onchain vote before token holders' approval can be recorded. Until that vote opens and passes, ENSv2 stays where it is today: a published draft awaiting its decision. Spot data shows the ENS price down 5.3% over the past 24 hours.

What activation means for name holders

Existing name holders sit at the center of the transition, and the draft leaves their position unchanged in the short term. Names that are already registered would keep working as they do today, whether or not their owners take any action, and no holder is required to migrate to the new system. ENS Labs has also reserved existing .eth names for their current owners on the upgraded contracts, so anyone who wants to move can do so on their own schedule rather than under deadline pressure. The registration pause is the sharpest edge of the proposal. New .eth registrations would move to the upgraded system only after domain records have been synchronized between the two versions, and Johnson cautioned that registration would go dark on both versions for several hours during that window. Renewals, by contrast, stay open throughout, which limits the practical damage for holders whose names are already live. That split treatment, frozen registrations but open renewals, is the proposal's main concession to holders who rely on their names today. The design choice reflects how the naming system is used in practice: applications read registry and resolver records that any Ethereum blockchain node can verify, so continuity of those records matters more than where new registrations are processed. Users who depend on name lookups daily, from wallet transfers to website configuration, gain little from a rushed switch. Handing administrative control to the DAO also closes out the founding company's operational role: once the upgraded contracts carry the registry, the last administrative authority ENS Labs holds disappears, and decisions over the system rest with token holders. For readers new to the ecosystem, our guide on how to use Ethereum explains how to send transactions and read such records. For holders weighing the change, the practical checklist is short: renew on the normal schedule, decide whether and when to migrate, and expect a registration gap measured in hours, not days, once the transition begins.

Nine days minimum from vote to execution

Our reading of the numbers: the process, not the technology, sets the pace of this rollout. A seven-day voting period plus a two-day timelock puts at least nine days between the moment a vote opens and the moment ENSv2 can activate, and the 1 million-vote quorum asks for sustained participation rather than a thin majority. Readers tracking the token through the wait can follow our ENS technical analysis. For now, no next step is on the record: the draft sits in the governance queue, and activation timing rests entirely with the DAO's token holders.