ENSIP-25 introduces a standardized method to verify that AI agents registered onchain are genuinely associated with their claimed ENS names.
Why it matters:
- AI agents are now signing transactions, holding assets, and participating in governance autonomously
- Without verification, there's no way to confirm an agent actually controls the ENS name it claims
- Wallets can now display verified ENS names for AI agents instead of raw addresses
How it works:
- Defines a standardized ENS text record linking registry entries (like ERC-8004) to specific ENS names
- Enables users to independently confirm agent authorization
- Provides consistent human-readable identity for autonomous onchain behavior
ENS extends its identity layer beyond individuals, DAOs, and organizations to include software agents, establishing itself as a neutral identity infrastructure for both human and machine actors on Ethereum.
ENSIP-25 defines a simple, deterministic answer. It introduces a standardized ENS text record that links a specific registry entry, such as one in ERC-8004, to a specific ENS name.
AI agents are no longer just experiments. They are registering identities, participating in governance, executing strategies, and coordinating across applications without direct human initiation. As this becomes more common, a fundamental question emerges: how do you verify
ENS already provides identity continuity for individuals, DAOs, and organizations. ENSIP-25 extends that same model to software agents, reinforcing ENS as a neutral identity layer for Ethereum, whether the actor is human or machine. Read more about ENSIP-25 and how it works 猬囷笍
This enables wallets to display verified ENS names for AI agents instead of raw addresses. It allows users to independently confirm that researchbot.eth is actually authorized by that ENS name. Applications can consistently attach human-readable identity to autonomous onchain
ENSIP-25 introduces a standardized way to verify that an AI agent registered onchain is genuinely associated with an ENS name. As autonomous agents begin signing transactions, holding assets, and interacting with protocols, verifiable identity becomes essential infrastructure.
ENS App Adds Native Browser Notifications for Real-Time Updates
The **ENS App** has introduced **native browser notifications**, allowing users to receive important updates directly in their browser without needing to check the app manually. This follows the February addition of built-in notifications for **name expiration reminders** via email, Telegram, or browser. **Key benefits:** - Stay informed about critical ENS updates automatically - Reduce risk of losing domain names to expiry - Multiple notification channels available (email, Telegram, browser) These updates make managing Ethereum Name Service domains more convenient by bringing alerts directly to users rather than requiring active monitoring of the application.
ENS Explorer Launches Resolver Dashboard for Simplified Node Management
The ENS Explorer has introduced a new **Resolver dashboard**, providing users who own resolver nodes with a centralized view of their configurations. **Key Features:** - Dedicated page for resolver node owners - Consolidated view of all configurations in one location - Simplified management of technical setups behind ENS names This update follows the February dashboard redesign, which overhauled the entire ENS interface to provide clearer views of names, settings, and activity. The new resolver dashboard continues this trend of improving user experience and preparing the infrastructure for ENSv2 and future developments. The addition makes it easier for technical users to monitor and adjust their resolver configurations without navigating through multiple pages or interfaces.
ENS Launches Alpha Log Series for v2 Development Updates
The Ethereum Name Service has introduced the **ENSv2 Alpha Log**, a recurring update series tracking development progress on their new App and Explorer on Sepolia testnet. The team is sharing regular updates on: - New features being added - Performance improvements - Bug fixes during the alpha phase This follows recent launches including the **ENS Explorer Alpha** (Feb 24), which provides complete onchain records of any ENS name, and a **streamlined registration flow** (Feb 23) that reduces the steps needed to register names. Users can test both tools now: - App: [app.ens.dev](http://app.ens.dev) - Explorer: [explorer.ens.dev](http://explorer.ens.dev)
ENS Explains Why It Extended Internet Namespace Instead of Creating New Roots
**ENS addresses a common misconception about naming infrastructure.** While launching a new .whatever namespace appears simple, ENS highlights the complexity of building naming infrastructure that functions seamlessly across wallets, apps, exchanges, and the web. **Key decision:** - ENS chose to extend the existing internet namespace rather than invent new roots - This approach prioritizes interoperability and real-world usability - The decision reflects the technical challenges of creating truly functional naming systems The [blog post](https://ens.domains/blog/post/ens-was-here-first) details the reasoning behind this architectural choice and why compatibility with existing internet infrastructure matters for adoption.