Tweet by @ensdomains on human readable addresses in crypto

ENS names are fundamentally changing. **ENSv2 replaces the single-object model** with hierarchical registries that allow different parts of a namespace to branch into their own permissions, logic, and resolution systems. **Key changes:** - Names are no longer single entries with one owner and resolver - Each name can now have its own registry and permission structure - Different namespace segments can operate independently with custom logic - The hierarchy becomes physically represented through the structure itself This architectural shift makes ownership and delegation more expressive while ENS infrastructure handles the complexity. Names become structured systems built from linked parts rather than isolated setups. The update maintains backward compatibility - existing subnames, CCIP-Read names, and imported DNS names continue working while gaining access to more powerful permissioning capabilities. [Read the full technical details](https://ens.domains/blog/post/names-are-no-longer-single-objects)

**ENS is upgrading its resolver system with ENSv2** The Ethereum Name Service is introducing a Universal Resolver - a single smart contract that can resolve names across multiple environments: - ENSv1 names - ENSv2 names - Layer 2 networks - Offchain names via CCIP-Read **What developers need to know:** Applications using ENS should update their libraries to ensure compatibility with the new Universal Resolver. The system uses CCIP-Read protocol to fetch data from L2s and offchain sources. This consolidation simplifies the resolution process by eliminating the need for separate resolvers for different name types and networks. Developers can find implementation details in the [ENSv2 readiness documentation](https://docs.ens.domains/web/ensv2-readiness/). **Action required:** Review your ENS integration and update libraries to support cross-chain resolution.

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.

A **Trust Resolution Layer (TRL)** has taken first place for establishing verifiable AI agent identity through ENS. The system combines multiple components: - World ID verification - ENSIP-25 agent registration standard - ENSIP-26 context records - Novel AIP manifest system These elements work together to create a **progressive 5-tier trust scoring system** for autonomous agents. This infrastructure addresses a critical need as AI agents increasingly sign transactions, hold assets, and interact with blockchain protocols. The TRL builds on ENSIP-25, which introduced standardized verification that an onchain-registered AI agent is genuinely associated with an ENS name. The solution provides essential identity infrastructure for the growing ecosystem of autonomous agents operating in web3.

The Ethereum Name Service has published its fifth alpha development log for ENSv2, detailing continued improvements to the App and Explorer on the Sepolia testnet. **Key Updates:** - Focus on reliability, flexibility, and overall usability enhancements - Builds on previous fixes including transaction modal layouts and Fuses page improvements - Ongoing polish to search functionality, profiles, notifications, and name management features The ENSv2 testing phase continues on Sepolia as the team iterates on the user experience before mainnet deployment. More updates are expected in upcoming alpha logs.