Pinned
ENSv2 is coming.
A new foundation for names, built for integrations and subnames at scale.
What will you build?
- ens.eth reposted
Your ENS has been sitting idle in your wallet. Starting today it can do two things at once: > make ENS governance stronger > and earn you rewards from the ENS DAO The ENS Delegation Incentives Program is live. - The Universal Resolver helps ENS feel like one system, even when names and records live in different places. It gives apps one entry point for .eth, DNS names, L2 namespaces and offchain records, with ENSv2 extending that flexibility further.
- Some of the most important parts of ENS are the ones you never have to think about. When you enter a name and the right address, avatar or profile appears, the Universal Resolver is helping make that simple experience possible. 🧵Replying to @ensdomainsThe Universal Resolver is not an ENSv2 feature- it already exists today. But this abstraction becomes even more useful as ENS moves to a more flexible registry architecture. The contract is designed to be upgraded to support ENSv2.The Universal Resolver makes ENS more capable without making it feel more complicated. Most people will never need to know it exists. They’ll enter a name, get the right answer and move on. Docs:
- ENS name ownership has evolved in three stages: → ERC721 for .eth second-level names → ERC1155 through the Name Wrapper → ERC1155Singleton in ENSv2 Each step brought the ownership model closer to the way ENS names actually work.This is more than a change in token standards. The Name Wrapper added broader tokenization and fuses, while ENSv2 brings ownership, roles, and expiry into the registry itself. Learn more:
- Replying to @ensdomainsAt a high level, this is the progression: ENSv1: ERC721 for .eth second-level names Name Wrapper: ERC1155 for wrapped names, with fuses ENSv2: ERC1155Singleton, with ownership on the token and roles/expiry in the registryThe broader story is that ENS ownership has evolved because ENS has evolved. The goal was never just to make names look like NFTs. The goal was to make ownership reflect what an ENS name is, what it can do, and what rights come with it. Read the full article:
- Replying to @ensdomainsThat’s where the Name Wrapper came in. The Name Wrapper allowed ENS names to be wrapped into ERC1155 tokens, including .eth names, DNS names, and subnames. It extended tokenized ownership to more of the ENS naming tree.ENSv2 also uses ERC1155Singleton. The user-facing idea is simple: ENS still needs the flexibility of ERC1155, but names themselves are unique. You don’t need multiple copies of the same name. You need one owner for one name.
- Replying to @ensdomainsENSv2 takes the next step by moving these ideas deeper into the protocol. Instead of one flat registry, ENSv2 uses hierarchical registries. Names are hierarchical, so the registry model becomes hierarchical too.
- Replying to @ensdomainsThe Name Wrapper also introduced fuses. A fuse is a permission that can be permanently revoked for as long as the name stays registered. This made it possible to give subname owners stronger guarantees about what they actually receive. Learn more about fuses:
