Skip to main content

Name Wrapper: Change Name Wrapper Permissions

Modify Name Wrapper permissions on your ENS name. Guide to burning fuses and locking capabilities.

Warning: burning Fuses is permanent. Revoking a permission is a one-way transaction that cannot be reversed until the name's expiry is reached. ENSv2 replaces Fuses with roles, and migration is the recommended path — don't burn new Fuses; migrate instead. Locked names may have upgrade limits under ENSv2. See What happens to a wrapped name when it migrates? and More on ENSv2.

Before changing any permissions on your name, review the Name Wrapper sections of the documentation at docs.ens.domains:

  • Overview

  • Wrapped States

  • Fuses

  • Expiry

  • Approved Operators

Permissions tab

Once your name is wrapped in the Name Wrapper, you have access to the Permissions tab in the ENS App:

You can only change permissions on a name that has been Emancipated by the parent — otherwise you'll see a warning instead. "Emancipation" means the parent owner can no longer control the name. All .eth 2LDs (like myname.eth) are automatically emancipated when they are first wrapped. See What Are Wrapped, Unwrapped, and Emancipated Names?

Changing permissions on your own name

  1. Click Change Permissions. A dialog warns you about the changes you're about to make. Click I understand to proceed.

  1. Lock the name if prompted. To burn owner-controlled Fuses on a name, the name must be Locked first — meaning you will no longer be able to unwrap it. Click "Revoke permission" to select it, then Next. See What Are Fuses in the Name Wrapper?

  1. Select the permissions to revoke. For example, revoking "Send this name" makes the wrapped NFT non-transferrable. If you only want to Lock the name, click Skip; otherwise select permissions and click Revoke.

  1. Approve the transaction. The dialog shows your selections. Click Open Wallet, approve in your wallet, then click Done once the transaction is confirmed.

The Permissions tab updates to show which permissions you have revoked. From there you can click Change permissions to burn additional Fuses, or click Revoke permission in the top section to completely "lock" the name — revoking the "permission to revoke permissions" itself, so the permissions on your name can never be changed again.

Changing subname permissions as the parent owner

If a subname has not been Emancipated, then as the parent owner you can delete it at any time:

If your parent name is Locked (meaning it can't be unwrapped), you can change permissions on any subnames underneath it — for example, click Change permissions and burn the extend-expiry fuse so the subname owner can extend their own expiry.

To Emancipate a subname:

  1. Click Give up parent control in the top section. A dialog warns you about the changes. Click I understand, then click "Give up ownership" to select it, and Next.

  1. Set an expiry. When you burn Fuses on a name you must also set an expiry for it at the same time — see How Does Expiry Work for Wrapped Names? The maximum is the expiry of the parent name (select Max), or select Choose an earlier date. Click Next.

  1. Select any other permissions to change. Once you give up control over the subname, you can no longer change any of its permissions. Some permissions are greyed out by default — revoking them also requires Locking the subname at the same time (click "Revoke permission to: Unwrap this name" first, then select the others). If you only want to Emancipate the name, click Skip; otherwise select permissions and click Revoke.

  1. Approve the transaction. The dialog shows your selections. Click Open Wallet, approve in your wallet, then click Done once confirmed.

The subname's Permissions tab updates to show what you revoked. In this example, the subname was Emancipated and Locked, meaning:

  • The parent owner can no longer control the subname.

  • The subname can no longer be unwrapped.

The Extend Expiry permission was also granted, meaning the subname owner can now extend their own expiry. And the Create Subnames permission was revoked, meaning the subname owner cannot create further subnames underneath their name (like further.sub.name.eth).

On the subname's Profile tab, you'll also see that you no longer have the ability to delete the subname:

See also: Name Wrapper Overview

Related Articles
Did this answer your question?