Ethereum Name Service is weighing a proposal that would stop new registrations on its current system and shift control of its next-generation protocol to the community that uses it. The ENSv2 Activation Proposal, as it's called, would halt new ENSv1 registrations while leaving existing .eth holders without a migration deadline. If passed, ENS Labs — the company that has shepherded the naming protocol since its early days — would hand its remaining ENSv2 admin roles to the DAO.
What the proposal actually changes for .eth holders
For anyone who already owns a .eth name, the immediate impact is close to zero. The proposal doesn't set a deadline for migration to ENSv2. There's no forced move, no countdown clock, no window that closes. Existing names would keep resolving on ENSv1 for the foreseeable future. The change is aimed at new registrations: once ENSv2 goes live under this plan, ENSv1 would stop accepting them.
That's a deliberate design choice. It prevents the old and new systems from competing for the same namespace while giving current holders time to move at their own pace. But it also creates a lopsided transition — newcomers would land entirely on ENSv2, while long-time holders could stay on ENSv1 indefinitely. Whether that split causes fragmentation in resolution or wallet support is an open question the proposal doesn't resolve.
ENS Labs gives up the keys
The second half of the proposal is more structural. ENS Labs would transfer its remaining administrative control over ENSv2 to the DAO. That includes roles that today sit with the company, not token holders. In practice, it means decisions about upgrades, parameters, and emergency powers would move to on-chain governance.
It's a notable step for a project that has, until now, kept a fair amount of operational control inside ENS Labs. Handing those levers to the DAO doesn't just change who signs off on changes — it changes how quickly they can happen, who can propose them, and what checks exist if something goes wrong. The proposal doesn't detail a phased handover or a fallback if governance stalls.
Why the DAO vote matters beyond ENS
ENS has been one of the more closely watched experiments in decentralized governance. Its DAO already controls the treasury and has a say in protocol direction. But admin roles are different. They're the unglamorous, high-stakes controls that keep a naming system from breaking — resolver updates, contract ownership, emergency response.
If the DAO takes them on, ENS becomes one of the few major naming or identity protocols where token holders hold those keys directly. That could set a template for other projects weighing a similar move. It also raises the stakes of every future governance vote. A sleepy proposal about a resolver parameter suddenly carries the same weight as a treasury spend.
The unresolved part: no migration deadline
The absence of a migration deadline cuts both ways. It's friendly to existing holders who don't want to be rushed. It's also a liability for anyone building on ENS who needs to know when ENSv1 support will end. Wallets, marketplaces, and dApps that integrate .eth names have no timeline to plan around. They'll have to support both systems for as long as ENSv1 stays live, which could be years.
That ambiguity is likely to draw comments during the proposal's review period. Some holders may push for a soft deadline or at least a stated intention. Others may argue that any deadline is a trap — that the whole point of ENS is permanence, and forcing a migration would undermine it.
What happens next
The proposal now moves through the DAO's governance process. That typically means a discussion period, followed by a vote. If it passes, ENSv1 registrations would close when ENSv2 activates, ENS Labs would begin transferring its admin roles, and .eth holders would face no forced migration. If it fails, ENS Labs keeps its current role and ENSv1 registrations continue alongside ENSv2 development. Either way, the vote itself will be the clearest signal yet of how much control the ENS community actually wants.
