ENSv2 - Identity for Apps, Agents & Beyond
summary
ENSv2 replaces a flat namehash registry with visible hierarchical registries and deployable subregistries, letting apps mint subnames, enforce granular permissions via role-based access control, and deploy per-name proxy resolvers from a verifiable factory. Transfers that change permissions burn and remint names so mutable token IDs update when roles change. Agent support uses ENSIP-25 with ERC-8004 and stores discoverable endpoints via ENSIP-26 text records; examples include wallets, IPFS sites, games, and branded loyalty subnames.
AI-written summary · about
chapters (26)
- 0:00Introduction to ENSv2 Identity
- 1:21Decentralized Naming on Ethereum
- 2:01Onchain Profiles and Multichain Records
- 3:20Reverse Resolution for Better UX
- 4:36Forward and Reverse Name Matching
- 5:38Primary Names Explained
- 6:42ENSv1 Flat Registry Structure
- 7:40ENSv2 Hierarchical Registries
- 8:16Custom Resolvers and Shared Resolvers
- 8:49Verifiable Factory Deployments
- 9:24Subregistries and Wildcard Resolution
- 10:15Registering Application Subnames
- 10:36Granular Permissions for Subnames
- 11:22Mutable Token IDs in ENSv2
- 13:27Role-Based Permission Controls
- 13:51Record-Level Aliasing
- 14:20Registry-Level Aliasing
- 15:10AI Agents as ENS Namespaces
- 15:45ENSIP-25 and ERC-8004
- 16:22ENSIP-26 Agent Endpoints
- 17:40Decentralized Websites With IPFS
- 17:54ENSv2 Hackathon Prizes
- 19:34Nested Registries and Subnames
- 21:13Game Profiles With ENS Subnames
- 23:21Loyalty Programs and Wallet Identity
- 25:03Paymasters and the ENS Resolution Layer
