ENSv2 is now live on mainnet. Upgrading old .eth names is voluntary, not mandatory, and has no deadline. But before you click upgrade, you need to check several status items one by one, because names in different states follow completely different migration paths — and some cannot be upgraded at all in the current phase.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
First, confirm which wrapper state your name is in
The ENSv2 migration path is determined by the wrapper state of the name in v1, not by which name you hold. Open the ENS App or ENS Explorer and check the token type and permission status of that name.
Unwrapped: This is a BaseRegistrar ERC-721 token. Migration goes through UnlockedMigrationController and is relatively straightforward. This is the simplest path.
Unlocked Wrapped: This is a NameWrapper ERC-1155 token, and CANNOT_UNWRAP has not been burned. It also migrates through UnlockedMigrationController. The controller first verifies the name is not locked, then unwraps it and promotes it to v2.
Locked: The name has burned CANNOT_UNWRAP. These restrictions are irreversible, and migration must preserve them. Second-level names (2LDs) go through LockedMigrationController. Third-level names and above (3LD+) must first wait for the parent name to complete migration, then migrate through the parent's WrapperRegistry. If the parent name has not been upgraded yet, you cannot upgrade the subname on your own.
If a name is locked and has burned CANNOT_APPROVE, but there is an uncleared approval from before the transfer, the migration will revert (FrozenTokenApproval). This is a specific obstacle to check before upgrading: make sure there are no leftover approvals on locked names.
Check the resolver and records being migrated
During migration, the v1 resolver is cleared, and the v2 name uses the new resolver you provide at migration time — unless CANNOT_SET_RESOLVER has been burned.
If CANNOT_SET_RESOLVER has been burned, the new resolver you provide will be ignored, and the v1 resolver will be carried over to v2 as-is. The official documentation adds: if the carried-over resolver is a known PublicResolver, it will be replaced with PublicResolverV2.
This means you need to confirm two things before upgrading: which resolver your name currently uses, and whether you have burned CANNOT_SET_RESOLVER. If you have not burned this permission, you can specify a new resolver at migration time, but make sure the resolver address you enter is the one you actually want to use. If you have burned it, you cannot change the resolver during migration and can only accept whatever is carried over to v2.
Check dependencies between subnames and parent names
If you hold a third-level name or above (such as sub.name.eth) and it is locked, the parent name must complete migration first before you can upgrade it through the parent's WrapperRegistry. The upgrade order cannot be reversed.
If you hold name.eth and it has subnames underneath, upgrading the parent name will replace its original subname registry. Fuse-based subname permissions set through NameWrapper in v1 will be converted to v2 role-based permissions during migration. Before migrating, it is worth confirming whether the control relationships of your subnames match your expectations — especially if you have granted management rights over certain subnames to others.
Expiry date and grace period: upgrading is not renewing
This is an easy point to misunderstand. ENSv2 shortens the grace period from v1's 90 days to 28 days. To compensate for this change, the registration expiry of migrated names is extended once by 62 days, so that "expiry date + 28-day grace period" still equals the original release date.
The 62-day adjustment is a rule-based compensation, not a renewal. If you want more valid time after upgrading, you still need to perform a separate renewal. Also, names currently in the grace period cannot be upgraded directly. If your name has already expired and entered the grace period, renew it first to restore valid status, then consider upgrading.
Fees and irreversibility
The upgrade itself requires paying Ethereum mainnet gas fees, and the exact amount depends on network conditions at the time. The ENSv2 commemorative NFT also requires gas to claim, and is limited to one per wallet.
One thing to be clear about: after upgrading, the App has no option to go back to v1. Although unupgraded v1 names will continue to resolve and renew normally, once you complete the migration, the operation is irreversible in the current frontend. For names holding many subnames or complex permission configurations, take screenshots or write down the current permission structure (fuses, approvals, resolver, subname control relationships) before upgrading — this will serve as a reference if anomalies appear later.
A practical judgment
If you simply hold an ordinary name.eth with no locking, no complex subname authorizations, and a standard PublicResolver, the upgrade process itself will not hit structural obstacles. The only things to pay attention to are gas costs and the fact that you cannot roll back after upgrading.
If you hold a locked name, or have subname dependencies, or have burned CANNOT_SET_RESOLVER, it is worth spending time before upgrading to confirm each of the status items listed above. Any one of these conditions could make the expectation of "just click upgrade" fall through, or produce a result different from what you expected. ENSv2 does not force migration, which means you can keep the status quo until you are sure — v1 names still resolve and can still be renewed.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
References
- ENS Documentation·Migration, 2026-10-31
- ENS Documentation·Migration (GitHub source), 2026-10-31
- Foresight News·ENSv2 officially launches on Ethereum mainnet, 2026-10-31
- Foresight News·ENS founder submits draft proposal to activate ENSv2 on Ethereum mainnet, 2026-10-31
- Huobi·After ENSv2 upgrade you get 62 extra days, how to check renewal dates? Existing .eth names, 2026-10-31
- ENS Documentation·ENSv2 Smart Contracts Overview, 2026-10-31
