ENSv2 Introduces Shared Registries for Scalable Namespace Management
ENSv2 Introduces Shared Registries for Scalable Namespace Management
đź”— Shared registries arrive
ENSv2 brings a major architectural shift to namespace scalability. Instead of requiring each ENS name to maintain its own isolated registry setup, the new version allows registries to be shared across multiple identities.
Key improvement:
- Shared registries reduce overhead and enable more efficient namespace management at scale
- Builds on ENSv2's hierarchical architecture where names are structured systems rather than single entries
Context: This follows ENSv2's move from a flat registry model to a hierarchical system of linked registries. The upgrade maintains backward compatibility with existing subnames, CCIP-Read names, and imported DNS names while introducing more powerful permissioning and delegation capabilities.
The change supports ENS's evolution from a niche crypto tool to infrastructure serving millions of names across ecosystems, wallets, and applications.
ENSv2 makes ownership and delegation more expressive under the hood, while ENS infrastructure abstracts away the complexity. Names are no longer single entries. They’re structured systems built from linked parts. Read more: ens.domains/blog/post/name…
ENS names can carry arbitrary records, making them the perfect vessel for an agent's full trust stack. One name holds everything: identity, discoverability, code integrity, capabilities. Query it and you get a score back: none, registered, discoverable, verified, full. That's
What’s actually changing with subnames in ENSv2? ENSv2 replaces the old flat registry model with a hierarchical registry system. Instead of everything living in one shared registry, each name gets its own registry and permission structure.
One of the biggest ENSv2 questions we’ve seen is about subnames. What happens to names like .base, .uni, imported DNS names, and CCIP-Read names? Here’s what changes, and what doesn’t 🧵
ENS is no longer a niche tool for crypto power users. Millions of names now exist across ecosystems, wallets, apps, and DNS integrations. ENSv2 is designed to support that kind of scale without losing the openness that made ENS useful in the first place.
Call registerAgentIdentity() and your agent gets a subname, an on-chain passport, and cryptographic proof linking to its owner. ENS is the anchor that makes it human-readable and resolvable. That's ENS as the entry point for agent identity.
ENSv2 replaces a flat registry with a hierarchy of linked registries, making ownership and delegation explicit onchain. Learn more: ens.domains/blog/post/name…
ENSv2 is coming, and with it, one big question: What happens to my name? Here’s everything you need to know about the upgrade 🧵
The tl;dr? ↪ Existing subnames keep working ↪ CCIP-Read names keep working ↪ Imported DNS names keep working ↪ ENSv2 introduces more powerful permissioning and delegation for subnames Keep an eye out for more FAQs on ENSv2!
ENSv2 is coming. A new foundation for names, built for integrations and subnames at scale. What will you build?
One of the most requested ENSv2 features is simpler payments. So can I buy ENS names with stablecoins? Yes. ENSv2 will support buying names with USD-denominated stablecoins (like USDC) from any EVM chain.
ENSv2 makes namespaces far more scalable. Instead of every ENS name maintaining its own isolated setup, registries can now be shared across many identities.
In ENSv2, the hierarchy becomes explicit. You open the eth vault and find every .eth name inside it. Open nick, and you can find sub nested within. The relationship between names is no longer implied. It is physically represented through the structure itself.
One thing became pretty clear this weekend: Agents need identity, discovery, permissions, reputation, coordination, and interoperable naming. A lot of builders reached for ENS to provide that foundation.
How will ENSv2 name pricing work? ENSv2 will make name pricing more predictable by setting registration and renewal costs in USD and supporting payment with stablecoins.
🏆 ETHesis Wins Runner-Up for AI Agent Integration with Onchain Research Funding
**ETHesis** secured second place in the Best ENS Integration for AI Agents category at a recent competition. The project addresses research funding transparency by enabling: - Researchers to launch **tokenized research ventures** - Communities to **fund projects directly onchain** - Autonomous auditor agents to **verify milestone completion** through ENS-linked attestations ETHesis joins a growing ecosystem of ENS-native AI agent projects, including first-place winner **ACL** (which uses ENS for agentic commerce discovery) and **Siren** (third place, focusing on ENS identity verification). The competition highlighted diverse use cases: from **EthTwin's** voice-first crypto interface to **Brainpedia's** knowledge network and **ENSign's** passkey-controlled smart accounts—all leveraging ENS as core infrastructure for agent coordination and identity.
ENS Dominates ETHPrague: 45% of Projects Built on Naming Protocol
**ETHPrague Results** ETHPrague concluded with 64 projects delivered over the weekend. ENS integration reached a new high: - **29 projects built on ENS** (45% of all submissions) - **4 teams won prizes** across two ENS-specific tracks This follows ETHGlobal Open Agents the previous week, where 177 of 468 projects (38%) integrated ENS. **What This Means** The increasing adoption rate—from 38% to 45%—shows developers are prioritizing human-readable naming in their applications. ENS provides the infrastructure for mapping readable names like 'alice.eth' to blockchain addresses and other identifiers. The protocol's presence at consecutive hackathons demonstrates its position as essential infrastructure for Ethereum development.
ENS Splits Into Two Apps: Management and Protocol Explorer
**ENS launches dual-app architecture with ENSv2** The Ethereum Name Service has restructured its interface into two separate applications, both currently in alpha testing on Sepolia: - **App**: Handles name management and user experience - **Explorer**: Provides deeper protocol-level visibility and data The original ENS application remains functional during the transition. This split architecture becomes possible through ENSv2, which enables the new dual-app experience. Both applications are accepting user testing and feedback on the Sepolia testnet before mainnet deployment.
ENS Launches registerAgentIdentity() for On-Chain Agent Verification
ENS has introduced `registerAgentIdentity()`, a new function that provides AI agents with on-chain identity infrastructure. When called, agents receive: - A human-readable ENS subname - An on-chain passport - Cryptographic proof linking the agent to its owner This builds on ENS's evolving role beyond simple name resolution. The system now supports: - **Arbitrary records** that carry an agent's full trust stack - **Identity scoring** (none, registered, discoverable, verified, full) - **Programmable resolvers** that execute logic like token swaps or privacy routing ENS serves as the accountability layer, transforming raw cryptographic keys into verifiable, human-readable identities. One ENS name can hold everything: identity, discoverability, code integrity, and capabilities. The infrastructure makes agents resolvable and accountable while maintaining the flexibility to chain complex actions through custom resolver logic.