ENSv2 Rollout

ENSv2 is deployed but not yet live.

This page outlines the stages of the rollout as outlined in the Activate ENSv2 proposal alongside its current status.

This page is updated every 5 minutes.

Checklist

1 of 10 steps done

Stage 1 Deployment and initial pre-migration
✓
Contracts deployed before the vote
ENS Labs
Every live v1 name is reserved on ENSv2 with daily syncs. See Readiness stats.
Stage 2 The DAO proposal executes
v1 registrations frozen
ENS DAO
The proposal removes each old controller from the v1 BaseRegistrar, so none of them can register or renew v1 names.
- Remove ETHRegistrarController (current) as a controller
- Remove NameWrapper as a controller
- Remove RegistrarMigration (2020 permanent-registrar migration) as a controller
- Remove Legacy 4-of-7 ENS Safe as a controller
- Remove ETHRegistrarController (2020) as a controller
ETHRenewerV1 controls v1 renewals
ENS DAO
After the freeze, v1 names can only be renewed through ETHRenewerV1.
- Make ETHRenewerV1 the owner of the v1 BaseRegistrar
- Add ETHRenewerV1 as a controller
- Add the Graveyard as a controller
Universal Resolver switched to the managed proxy
ENS DAO
The public Universal Resolver proxy still points at UniversalResolver (v1), not the managed proxy.
Stage 3 Final pre-migration sync
Final sync run after v1 is frozen
ENS Labs
To be confirmed by ENS Labs.
Stage 4 v2 goes live
Pre-migration sync switched off
ENS Labs
BatchRegistrar can still reserve names on the .eth registry.
Migration open
ENS Labs
v1 owners can move their names to ENSv2 once both migration controllers can claim the reserved names.
- Locked migration controller can claim reserved names
- Unlocked migration controller can claim reserved names
v2 registration open
ENS Labs
New .eth names are registered and renewed on ENSv2 through ETHRegistrar.
- ETHRegistrar can register .eth names
- ETHRegistrar can renew .eth names
Resolution cut over to ENSv2
Security council
The managed proxy still serves UniversalResolver (v1) (the v1 Universal Resolver), not UniversalResolverV2.
Stage 5 Handover to the DAO
Registry admin handed to the DAO
ENS Labs
ENS Labs gives up its admin roles and hands the eth and reverse names to the DAO.
- The ENS Labs deployer holds no root roles on the registries
- The ENS Labs deployer holds no roles on the eth and reverse names
- The eth and reverse names are held by the DAO name-owner Safe

Where these steps come from

The checklist follows the five stages in nick.eth's "[Executable] Activate ENSv2" post. ENS Labs' migration runbook (contracts-v2 PR #465) splits the same work into eight phases, one per run of its migration script.

Stage 2's three checks happen when the DAO proposal executes: it removes the five old v1 controllers, makes ETHRenewerV1 the owner of the v1 registrar, and points the public Universal Resolver at a managed proxy.
Stages 4 and 5 are carried out after the vote. ENS Labs switches off the pre-migration sync, opens migration and v2 registration, and hands registry admin to the DAO. The security council upgrades the managed proxy to UniversalResolverV2 (the resolution cutover).
Stages 1 and 3 leave nothing on-chain that shows they've finished, so their rows are ticked by hand.
The proposal doesn't enforce the steps after the vote. Until the handover, the DAO holds only minor roles on the registries, so it has no on-chain way to remove the deployer.

Who controls the ENSv2 registries

Roles over the whole contract. In ENSv2, roles are granted on a resource. Each registered name is its own resource, so a name's owner holds roles over just that name. A registry also has one resource for itself as a whole, called the root. An address holding a role on the root can use it on every name in that registry. These tables list those addresses and the roles each one holds.
Admin roles. Every role has an admin version, which lets the holder grant that role to any address, its own included. So "REGISTRAR admin only" means the holder doesn't have REGISTRAR right now, but could give it to itself at any moment. The "Can grant itself more" flag marks this.
Dangerous root roles. A few root roles let the holder act on names other people own: unregister a name, change its resolver, point it at a different subregistry, control whether its token can be transferred, or upgrade the registry's code. The contracts treat these as the roles that break emancipation, the guarantee that once you own a name nobody above you can take it or change it.

Root registry0x2553…a91e

Holder	Roles held	Flags
ENS Labs deployer (EOA) 0x85a7…5c20	REGISTRAR + adminREGISTER_RESERVED + adminSET_PARENT + adminRENEW + adminSET_URI + adminCAN_NAME + admin	-
ENS DAO timelock 0xfe89…44b7	SET_URICAN_NAME	-

.eth registry0xf60a…85e2

Holder	Roles held	Flags
ETHRenewerV1 0x56c4…cb68	RENEW	-
ENS Labs deployer (EOA) 0x85a7…5c20	REGISTRAR admin onlyREGISTER_RESERVED admin onlySET_PARENT + adminRENEW admin onlySET_URI + adminCAN_NAME + admin	Can grant itself more
BatchRegistrar (ENS Labs' daily pre-migration sync) 0xf0cc…9721	REGISTRARRENEW	-
ENS DAO timelock 0xfe89…44b7	SET_URICAN_NAME	-

ETHRegistrar0xd6d8…cc81

Holder	Roles held	Flags
No roles: ETHRegistrar is controlled by its owner, the ENS DAO timelock.

The eth and reverse names

Roles on these names are potentially dangerous as some allow the address in question to modify ownership and/or expected resolution.

Name	Token held by	Roles held	Flags
`eth`	ENS Labs deployer (EOA) 0x85a7…5c20	REGISTRAR + adminREGISTER_RESERVED + adminSET_PARENT + adminUNREGISTER + adminRENEW + adminSET_SUBREGISTRY + adminSET_RESOLVER + adminCAN_TRANSFER + adminWAS_RESERVED + adminSET_URI + adminCAN_NAME + adminUPGRADE + admin	Can replace .eth registry Can delete .eth
`reverse`	ENS Labs deployer (EOA) 0x85a7…5c20	REGISTRAR + adminREGISTER_RESERVED + adminSET_PARENT + adminUNREGISTER + adminRENEW + adminSET_SUBREGISTRY + adminSET_RESOLVER + adminCAN_TRANSFER + adminWAS_RESERVED + adminSET_URI + adminCAN_NAME + adminUPGRADE + admin	Can replace reverse registry Can delete reverse

Permission changes

This table outlines every role grant and revocation on the ENS v2 smart contracts. Roles in ENSv2 take advantage of Enhanced Access Control.

Date	Where	Account	Change
2026-10-13	.eth registry root	ETHRenewerV1 (superseded) 0xe038…62b1	Revoked RENEW
2026-10-13	.eth registry root	ETHRenewerV1 0x56c4…cb68	Granted RENEW
2026-10-13	Root registry reverse token	ENS Labs deployer (EOA) 0x85a7…5c20	Granted REGISTRAR + adminREGISTER_RESERVED + adminSET_PARENT + adminUNREGISTER + adminRENEW + adminSET_SUBREGISTRY + adminSET_RESOLVER + adminCAN_TRANSFER + adminWAS_RESERVED + adminSET_URI + adminCAN_NAME + adminUPGRADE + admin
2026-10-13	Root registry eth token	ENS Labs deployer (EOA) 0x85a7…5c20	Granted REGISTRAR + adminREGISTER_RESERVED + adminSET_PARENT + adminUNREGISTER + adminRENEW + adminSET_SUBREGISTRY + adminSET_RESOLVER + adminCAN_TRANSFER + adminWAS_RESERVED + adminSET_URI + adminCAN_NAME + adminUPGRADE + admin
2026-10-13	Root registry root	RootBatchRegistrar 0xe467…b164	Revoked REGISTRARRENEW
2026-10-13	Root registry root	RootBatchRegistrar 0xe467…b164	Granted REGISTRARRENEW
2026-10-13	Root registry root	ENS DAO timelock 0xfe89…44b7	Granted SET_URICAN_NAME
2026-10-13	Root registry root	ENS Labs deployer (EOA) 0x85a7…5c20	Granted REGISTRAR + adminREGISTER_RESERVED + adminSET_PARENT + adminRENEW + adminSET_URI + adminCAN_NAME + admin
2026-10-08	.eth registry root	Locked migration controller (superseded) 0x4d51…2e17	Revoked REGISTER_RESERVED
2026-10-08	.eth registry root	Unlocked migration controller 0xab82…eb64	Revoked REGISTER_RESERVED
2026-10-02	.eth registry root	Locked migration controller (superseded) 0x4d51…2e17	Granted REGISTER_RESERVED
2026-10-02	.eth registry root	BatchRegistrar (ENS Labs' daily pre-migration sync) 0xf0cc…9721	Granted REGISTRARRENEW
2026-10-02	.eth registry root	ETHRenewerV1 (superseded) 0xe038…62b1	Granted RENEW
2026-10-02	.eth registry root	Unlocked migration controller 0xab82…eb64	Granted REGISTER_RESERVED
2026-10-02	.eth registry root	ENS DAO timelock 0xfe89…44b7	Granted SET_URICAN_NAME
2026-10-02	.eth registry root	ENS Labs deployer (EOA) 0x85a7…5c20	Granted REGISTRAR admin onlyREGISTER_RESERVED admin onlySET_PARENT + adminRENEW admin onlySET_URI + adminCAN_NAME + admin

Checked Wed, 21 Oct 2026 16:41:06 GMT.