Documentation for agents: an index at /llms.txt, every docs page in one file at /llms-full.txt, and Markdown for any docs page by adding .md to its URL.

Skip to Content
ensforgeSDK

What wrapped names are

Learn what the ENSv1 Name Wrapper does, how it changes who controls a name, and what happens to wrapped names on ENSv2 later.

This page is about ENSv1 only. The Name Wrapper is an ENSv1 contract that turns a name into an ERC-1155 token and adds fuses: permissions that can be burned, for good, until the name expires. ENSv2 has no Name Wrapper. Wrapped names migrate to ENSv2 like unwrapped ones.

You never need to wrap a name to use ensforge. Wrapping matters when you want the token form or want to give up powers permanently.

What wrapping changes

UnwrappedWrapped
Token.eth names: an ERC-721 registrar token. Others: none.An ERC-1155 token in the NameWrapper.
Who controls itA registrant (the registrar token holder, for .eth names) and a manager (the registry owner).One owner: the NameWrapper token holder.
FusesNone.Yes.
SubnamesThe manager creates them freely.Created with fuses and an expiry.

On a wrapped name there is no separate manager. name.get reports the token holder as owner.

Fuses and name states

A fuse is a permission that can be burned. A burned fuse cannot be unburned before the name expires. Two states matter:

  • Emancipated (parentCannotControl burned): a subname its parent can no longer control. The parent can only extend it, until it expires.
  • Locked (cannotUnwrap burned): a name that stays in the NameWrapper until it expires. Every other owner-controlled fuse needs it first.

See Lock permissions with fuses for the full list.

What ensforge does for you

Renewal

.eth names still on ENSv1, wrapped or not, renew through ETHRenewerV1, which also extends the wrapped name's expiry. registration.renew picks it for you. See Renew a name.

To wrap or unwrap a name, see Wrap and unwrap a name.

Was this page helpful?