ENSv2 - Identity for Apps, Agents & Beyond
summary
ENSv2 turns addresses into bidirectional names with forward and reverse resolution, introduces a hierarchical registry so subtrees can be remounted, and makes custom resolvers cheap to deploy via a factory proxy. Builders can optionally tokenize subnames with registries, enforce roles and granular permissions, and use mutable ERC-1155 token IDs that regenerate on permission or expiry changes to invalidate stale listings. Features include aliasing and agent namespaces, Sepolia testing, and remaining audits and migration before mainnet.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 0:17Meet Kevin Krone and ENSv2
- 0:40What Is Ethereum Name Service?
- 1:03Human-Readable Wallet Addresses
- 1:58ENS as an Onchain Profile
- 2:52ENS Integration Examples
- 4:03Replace Hex Addresses With ENS Names
- 4:22Forward Resolution Across Chains
- 5:12Reverse Resolution and Primary Names
- 5:36Why ENSv2 Redesigns the Protocol
- 6:26From a Flat Registry to a Hierarchy
- 7:13Registry Contracts and Name Labels
- 8:00Moving Subtrees Across the Hierarchy
- 8:13ENSv2 Resolvers and Subname Registries
- 8:35Deploying Custom Resolver Contracts
- 9:35Tokenizing Subnames With Registries
- 10:11Creating Data-Only Subnames
- 11:18When Subname Tokenization Makes Sense
- 11:33Roles and Granular Permissions
- 12:09Soulbound and Transferable Subnames
- 13:40Mutable ERC-1155 Token IDs
- 14:13Protecting Buyers When Permissions Change
- 15:30Why Builders Should Use ENSv2
- 16:10ENSv2 Documentation and Code Examples
- 16:25Permissioned Records for AI Agents
- 17:36Aliasing and Shared Records
- 18:10ENS Namespaces for Agents
- 18:32Building Wallets, Social Apps, and Websites
- 19:14Hackathon Prize Tracks
- 20:04Continuity Track and Sepolia Integration
- 21:14Audits, Migration, and Mainnet Readiness
- 21:39Closing and Final Questions
