ensVision
The trusted guide to ENS

Wrapped and Unwrapped ENS Names Explained

GuideRead time: 6 min

The Name Wrapper is the part of ENS most often misunderstood, and the source of the most confusing ownership readings in every tool. If a name has ever appeared to be owned by a contract you do not recognise, wrapping is why.

What wrapping means

The Name Wrapper is a contract that allows you to wrap any ENS name into an ERC-1155 NFT. This includes .eth second-level names such as name.eth, DNS names such as name.xyz, and subnames such as sub.name.eth.

When wrapping a .eth name, you transfer the ERC-721 NFT ownership to the Name Wrapper contract, which also takes over the manager role for the name. In return, the contract issues you an ERC-1155 NFT that proves you are the actual owner.

Why anyone wraps a name

Wrapping exists to give names the same functionality as NFTs. A wrapped name can be traded, transferred, and used in any context that understands ERC-1155. It also enables finer grained permissions for subnames, which is why projects issuing subnames wrap the parent.

For a simple holder, wrapping is often not necessary. For a project issuing subnames, or anyone wanting the name to behave as a fully transferable asset, it is the standard route.

Fuses explained

A fuse is the technical term for a permission bit on a wrapped name. Once that bit is flipped on, the fuse is burnt and cannot be unburnt, unless the name expires.

The name of the mechanism is deliberate. A fuse is irreversible, and it exists so that a wrapped name can be handed to someone else with guarantees that certain powers have been permanently relinquished. This is what makes it possible to sell or delegate a name while proving you cannot interfere with it later.

The ownership stack, and why tools disagree

Wrapping creates a layered ownership structure, and this is the practical consequence people run into most often.

Different tools read different layers. A tool reading the registry owner will report the wrapper contract. A tool reading the ERC-1155 holder reports you. Both are correct, and this is why a name can appear to be owned by a contract in one interface and by you in another.

See how the grace period works for why the wrapped expiry sits 90 days later.

The expiry date that confuses people

For .eth second-level names, the end of the name's grace period from the registrar is used as the expiry inside the Name Wrapper. If the registrar expiration date is 1 January, the expiry reflected in the Name Wrapper is that date plus the ninety day grace period.

So a wrapped .eth name can legitimately show two different expiry dates depending on where you look. Neither is wrong. One is the date you must renew by, the other is the point at which the name is truly released.

Unwrapping

As the owner of a wrapped name you can unwrap at any time. If you are wrapping to issue ENS subnames with finer permissions, that is the usual reason. by unwrapping an ERC-721 name or the equivalent call for other name types. You can do this as long as the permission to unwrap has not been revoked.

If a fuse has been burnt that removes the ability to unwrap, you cannot reverse it before expiry. This is worth checking before accepting a wrapped name from anyone else.

Renewal still works normally

Wrapping does not remove your ability to renew. The eth node is locked in the registrar contract and the Name Wrapper is approved as a controller, so .eth second-level names can be renewed directly by their owners.

What to check on a wrapped name

Next steps

Browse the ENS learning hub for the other guides. Read the registry, registrar and controller guide for the contracts beneath this, or the subnames guide if you plan to issue subnames.

Sources