The Name Wrapper is a new contract for ENS that allows you to "wrap" any ENS name into a ERC-1155 NFT.
Without the Name Wrapper
Before the Name Wrapper, only .eth 2LDs (second-level names, like ens.eth) had ERC-721 NFTs associated with them, unless the owner created a separate custom contract.
⚠ ENSv2 Notice: We recommend waiting for ENSv2 before locking names with Fuses — locked names may have some restrictions when upgrading. [Learn more → ENSv2 Hub]"
With the Name Wrapper
 | There are two types of Fuses:Parent-Controlled Fuses:
Example: By burning
Owner-Controlled Fuses:
Example: By burning Subname Fuses:
The parent owner has the power to burn Fuses when creating subnames. Deciding what perks, permissions, or guarantees to give to subname owners. |
With this new contract, you can wrap:
Any .eth name or subname
Examples:name.eth,sub.name.ethAny DNS name or subname
Examples:name.com,sub.name.com
Unwrapped .eth 2LDs have the concept of a separate Owner (Registrant) and Manager (Controller).
This changes after you wrap the name, because there is only a single account that serves as both the Owner and Manager for the wrapped name.
Wrapping and Unwrapping
When wrapping a .eth 2LD, you transfer the Owner (Registrant) of the ERC-721 NFT to the Name Wrapper contract.
The contract will then automatically take over the Manager (Controller) for the name as well.
You can do this by calling the wrapETH2LD method. Or, you can directly transfer the ERC-721 NFT to the Name Wrapper contract. In return, the contract issues you an ERC-1155 NFT.
When wrapping any other ENS name, you transfer the Manager (Controller) of the name to the Name Wrapper contract. You can do this by calling the wrap method. In return, the contract issues you an ERC-1155 NFT.
As the owner of the wrapped name, you can unwrap at any time by calling either unwrapETH2LD or unwrap. You can do this as long as the permission to unwrap has not been revoked.
Related Articles