⚠️ This feature is not yet live on mainnet. The information below describes testnet (Sepolia) behaviour only and should not be acted upon on mainnet. If you have received an email or message urging you to upgrade your name, please be aware this may be a scam — ENS will not prompt you to upgrade via unsolicited messages.
A small number of names cannot upgrade to ENSv2, either because a permission on the name was revoked (also called burning a fuse) or because a subname's parent has not upgraded yet.
Revoked Permissions
Upgrading moves the name to the new contract, and it cannot move a locked-down name cleanly, so a wrapped name cannot upgrade if either of these two permissions shows as Revoked:
"Cannot send this name" (the
CANNOT_TRANSFERfuse). Once this permission is revoked, the name cannot be transferred to a new owner, so the upgrade has nowhere to move it."Cannot change renewal manager" (the
CANNOT_APPROVEfuse). This blocks the upgrade only if the name also has an approved address: a wallet you allowed to renew it for you. With approvals frozen and one still in place, the upgrade cannot clear it, so it fails.
 |  |
How do I check if my wrapped name can't upgrade?
Open your name in the app and go to the Permissions tab. Each row is a permission that can be revoked. A permission that's still active shows a yellow info icon; a permission that's been revoked shows a grey no-entry icon.
 |
If neither is revoked, your name isn't blocked by permissions and should upgrade normally. See What happens to a wrapped name when it upgrades? for what to expect. If you have a subname, there's an additional case covered further down.
Why won't my subname upgrade?
A subname can be blocked for one of two different reasons, and only one of them is fixable.
The fixable case: the subname's parent has not upgraded yet. A subname (for example
sub.name.eth, whose parent isname.eth) cannot upgrade ahead of its parent. Upgrade the parent name first, then come back and upgrade the subname. If the subname has already been sent to someone else, the wallet that holds it does that second step — the parent owner cannot upgrade it for them.The permanent case: the subname has had its own permissions revoked. Before that can happen, the parent has to give up control of the subname; the app does this through the "Give up ownership" step. Only then can "Cannot send this name" or "Cannot change renewal manager" be revoked on the subname. Once they are, the subname is locked like any other name, and it cannot upgrade.
Common questions
Can I undo a revoked permission so my name can upgrade?
No. Revoked permissions are permanent. Once "Cannot send this name" or "Cannot change renewal manager" has been revoked, it can't be restored, so a name blocked for either reason stays on the old system. This is by design: these permissions exist so an owner can deliberately lock a name down, and that lock is meant to be irreversible.
What if my name is in its grace period?
A name in its grace period cannot be transferred, so it cannot upgrade either. Renew it first to bring it back to active registration, then upgrade as normal. Renewing during grace restores the name straight away, so nothing is lost.