ENSv2 activation proposal and its effect on .eth names.

ENS

ENSv2 activation proposal and its effect on .eth names

Nick Johnson’s October 11 draft asks the ENS DAO to execute one on-chain transaction that freezes new .eth registrations on ENSv1, authorizes a renew-only contract for names that have not migrated, and routes resolution through a proxy prepared for ENSv2. The proposal is a draft; the supplied coverage says voting has not started. ENS DAO proposal

Existing names

Owners can leave names on v1: they continue to resolve as before and can be renewed, with no migration deadline. Renewing also extends the name’s v2 reservation. Owners may migrate through the ENS app when ready, but migration is irreversible; wrapped names retain their locked permissions. Names already beyond their grace period are not carried over and become available to register on v2. Proposal details

New registrations and timing

If the DAO executes the proposal, v1 registrations stop. ENS Labs then plans a final sync to reserve live v1 names for their owners, enable v2 registration, switch resolution to v2, and transfer its remaining v2 admin roles to the DAO. The draft expects a gap of a few hours between execution and v2 launch; during it, no new registrations or renewals would be possible, while other v1 name operations continue. Proposal details

How the upgrade works

ENSv2 replaces the flat name registry with hierarchical registries, allowing names to use their own registry and resolver implementations and to assign more specific permissions to subnames. The draft says the DAO would control privileged roles on both versions after Labs completes the handover. Proposal details

Further reading

ENS DAO draft · The Defiant coverage

Ask your own