Skip to main content

Why can't I migrate my wrapped name or subname?

Some wrapped names can't migrate because a permission was revoked or a parent hasn't migrated. How to tell which, and what's possible.

A small number of names cannot migrate to ENSv2 contracts — because a permission on the name was revoked (burned), or because a subname's parent hasn't migrated yet.

Revoked Permissions

Migration moves the name to the new contract, and a locked-down name can't be moved cleanly — so a wrapped name can't migrate if either of these two permissions shows as Revoked:

  • "Cannot send this name" (the CANNOT_TRANSFER fuse). When this is revoked, the name can no longer be transferred to a new owner, so migration has nowhere to move it.

  • "Cannot change renewal manager" (the CANNOT_APPROVE fuse). This blocks migration only when an approved address is also set on the name. With approvals frozen and an approval still in place, migration can't clear it, so it fails.

How to check if my wrapped name can't migrate?

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 migrate normally — see What happens to a wrapped name when it migrates? for what to expect. If you have a subname, there's an additional case covered further down.


Why won't my subname migrate?

A subname can be blocked for one of two different reasons, and only one of them is fixable.

  1. The fixable case: the subname's parent hasn't migrated yet. A subname three or more levels deep (for example sub.name.eth) can't migrate ahead of its parent. Migrate the parent name first, then come back and migrate the subname.

  2. 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 first — 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 can no longer migrate.


FAQ

Can I undo a revoked permission so my name can migrate?

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?

If your name has expired and is in its grace period, it can't be moved — so it can't migrate. Renew it first to bring it back to active registration, then migrate as normal. Renewing during grace restores the name straight away, so nothing is lost.

Did this answer your question?