Identity for Apps, Agents & More
summary
ENS turns hex addresses into human-readable names and augments them into portable profiles with avatars, multi-chain addresses and arbitrary text records so a name like greg.eth as portable profile resolves across chains via forward and reverse resolution to form a primary name. Workshop demos show ENSIP-25 verification using the ERC-7804 agent registry, interoperable addresses with on.eth interoperable chain names, decentralized sites via Omnipin + IPFS, Durin-issued subdomains, Fluidkey stealth-address privacy, CCIP read for off-chain records, and two hackathon tracks with $500/$750/$1,250 prizes.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:39What Is ENS
- 1:33ENS as a User Experience Protocol
- 2:21ENS Profiles and Portable Identity
- 3:42Connect Wallet UX With and Without ENS
- 4:58Examples in the Wild: Snapshot and Matcha
- 5:24ENS for Transaction History and Sending Assets
- 7:11Users Should Never See Hex Addresses
- 7:41How ENS Works: Forward and Reverse Resolution
- 9:04Primary Names and Reverse Registrars
- 9:56Using ENS for AI Agents
- 10:29Agent Namespaces and Subname Hierarchies
- 11:51Agent Metadata in Text Records
- 12:15ENSIP-25: Verification with ERC-7804 Registry
- 13:23Names for Chains: Interoperable Names with on.eth
- 14:51Decentralized Websites with Omnipin and IPFS
- 16:37Naming Smart Contracts and Smart Accounts
- 17:32Subnames for Onboarding Users
- 18:00Durin: Issuing Subdomains on Any EVM Chain
- 18:53Custom Text Records as Decentralized Storage
- 19:24Building Blocks for Different App Types
- 21:46ENS Improves Existing Apps
- 22:39Hackathon Prize Tracks
- 23:30Q&A: Encrypted Data and Fluid Key Privacy
- 25:26Q&A: Killer Use Cases and Verification
- 27:19Q&A: Custom Metadata and Text Records
- 28:36Q&A: CCIP Read and Decentralized Websites
- 31:16Closing
