ENS Launches registerAgentIdentity() for On-Chain Agent Verification
ENS Launches registerAgentIdentity() for On-Chain Agent Verification
🤖 Agents get passports
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.
Under the hood, a custom ENS resolver does more than return an address. It can execute logic like swapping tokens, routing into Railgun, or chaining actions. Your ENS name becomes programmable. That's ENS as a privacy primitive, not just a name. Congrats to @TBlackicon and
🏆 ETHesis Wins Second Place for AI Agent Integration with Transparent Research Funding
**ETHesis** has secured second place in the Best ENS Integration for AI Agents category by building a transparent onchain research funding platform. **How it works:** - Researchers launch tokenized research ventures - Communities provide funding directly onchain - Autonomous auditor agents verify milestone completion - Verification happens through ENS-linked attestations The project demonstrates how ENS can serve as infrastructure for **decentralized research coordination**, combining tokenization, community funding, and automated verification in a single system. ETHesis joins a growing ecosystem of ENS-native projects exploring agent commerce, identity verification, and decentralized coordination—from ACL's agent marketplace to Siren's trust certificates.
ENS Dominates ETHPrague: 45% of Projects Built on Naming Protocol
**ETHPrague Results** ETHPrague concluded with 64 projects delivered over the weekend. ENS emerged as the dominant infrastructure choice: - **29 projects built on ENS** (45% of all submissions) - **4 teams won prizes** across two ENS-specific tracks This follows strong momentum from the previous week's ETHGlobal Open Agents event, where 177 of 468 projects (38%) integrated ENS. The consistent adoption rate across consecutive hackathons demonstrates ENS's position as core infrastructure for Ethereum developers building identity and naming solutions.
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 Turns 9: The Reverse Record Issue #5 Drops
**The Reverse Record Issue #5 is now available**, featuring coverage by @saniyamore on several key developments: - **ENS celebrates its 9th anniversary** - marking nearly a decade of decentralized naming on Ethereum - **ENSv2 progress updates** - the latest advancements in the next version of the protocol - **Architectural shift explained** - why ENS names are no longer treated as single objects and what this means for the ecosystem - **Ecosystem highlights** - notable updates from across the ENS community *Fair warning: Contains more Star Wars references than strictly necessary.* This follows previous issues covering the ENS offsite in Taipei and broader shifts in the naming landscape.