ENS Labs asks DAO to activate ENSv2 on Ethereum and freeze new .eth registrations on v1

ENS Labs asks DAO to activate ENSv2 on Ethereum and freeze new .eth registrations on v1

N
News Editor
2026-10-12 16:18:10
ENS Labs has asked the ENS DAO to switch on ENSv2 on Ethereum mainnet and freeze new .eth registrations on the original v1 registrar, shifting future sign-ups to the new system. ENS founder Nick Johnson, posting as nick.eth, submitted the executable proposal on the ENS governance forum on Oct. 11. The proposal bundles 15 calls from the DAO timelock into one atomic transaction, removing all five currently authorized controllers on the v1 BaseRegistrar and restoring only two: ETHRenewerV1, which handles renewals for names already reserved on v2, and a Graveyard contract that can claim names left expired past grace. Existing .eth holders would not need to take any action, and the proposal says there is no deadline to migrate. ENSv2 would shorten the post-expiry grace period from 90 days to 28 days, while extending each name’s v2 expiry by 62 days. The post says only one of the five activation stages requires a DAO vote, with the final step set to transfer ENS Labs’ remaining v2 admin powers to the DAO timelock.

ENS Labs has asked the ENS DAO to activate ENSv2 on Ethereum mainnet, a move that would freeze new .eth registrations on the original v1 registrar and shift future sign-ups to the new system.

ENS founder Nick Johnson, posting as 「nick.eth」 on the ENS governance forum, published the executable proposal on Oct. 11. It groups 15 calls from the DAO timelock into a single atomic transaction.

How the proposal changes control of the v1 registrar

According to the forum post, the transaction would remove all five controllers currently authorized on the v1 BaseRegistrar and add back only two:

  • ETHRenewerV1, which handles renewals for names already reserved on v2;
  • a Graveyard contract, which can claim names that stay expired past their grace period.

Ownership of the registrar would then pass to ETHRenewerV1. The post says that contract cannot register new names and cannot add controllers.

The proposal did not include a voting date, and no Tally or Snapshot vote link had been attached as of publication.

What this means for current .eth holders

Existing holders would not need to do anything. If a user already owns a .eth name and takes no action, the name will keep working. The post also says, 「There’s no deadline to migrate.」

Owners can move a name to v2 through the ENS app whenever they choose. Names that have already lapsed past their grace period will not carry over and will instead become available for anyone to register on v2.

ENSv2 shortens the post-expiry grace period to 28 days from 90. To offset that change, the proposal says each name’s v2 expiry will be extended by 62 days.

Registrations on both v1 and v2 would pause after the proposal is executed and before v2 goes live. The post expects that gap to last a few hours.

Only one activation stage needs a DAO vote

The proposal says only one of the five activation stages requires a DAO vote. The final stage would have ENS Labs renounce its admin roles over the v2 contracts and transfer them to the DAO timelock.

Before that happens, ENS Labs plans to re-run its name reservations after the freeze, allow the v2 registrar to accept sign-ups, and route name lookups through v2. The post says those steps are commitments by ENS Labs rather than part of the onchain vote.

Once completed, the DAO would control ENSv2 in the same way it currently controls v1, and ENS Labs would no longer hold any privileged role in either version, according to the post.

Fees and tradeoffs listed in the post

The proposal says registration fees on v2 are paid to the timelock, which has owned the fee-handling contracts since deployment.

The post also outlines tradeoffs. One is the loss of an emergency path on v1 that allows a designated controller to disable a registrar controller without a vote.

It also says the v1 freeze is reversible, while name migration is not. The DAO could restore v1 controllers through another executable proposal, but migrated tokens cannot be moved back.

Background on ENSv2

ENS Labs first introduced ENSv2 in 2024 as a move to a layer 2. The new proposal says the full v2 contract set has already been deployed on Ethereum mainnet.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
7000

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.

ENS Labs asks DAO to activate ENSv2 on Ethereum and freeze new .eth registrations on v1 | Bit.Fan