agentNames

.agent is cool, but agent.eth is cooler

cooked up a small ENSIP-25 demo to experiment with agent ↔️ ENS attestations. builders working with agents might find this helpful 👨‍🍳

We’ve released an interactive ENSIP-25 demo app. It shows how ENS names can verify their association with onchain AI agents registered in ERC-8004 registries, and lets you experiment with the verification flow. Try it here → ensip25.ens.domains

Your agent just got an identity, a voice, and a wallet in one SDK. 8004 for identity. A2A for communication. x402 for payments. Live now on agent0 SDK. Here's how it works ↓

@7777eth stop

@AgentNameServ agentcard.sol🔥

🚨 ENS COMPONENTS 🚨 Plug-and-play React components for ENS: → Name registration → Subname registration (onchain/offchain) → Profile & record editing → Playground for testing Add ENS to any React app in minutes - 🧵👇 enscomponents.com

ENS will win

New blockchain naming systems launch .whatever extensions faster than anyone can track. .crypto .wallet .agent .nft Minting strings is easy. Building naming infrastructure that works across wallets, dApps, exchanges, and the web is the hard part. That distinction matters. ens.domains/blog/post/ens-…

Launching a new .whatever namespace is easy. Building naming infrastructure that works across wallets, apps, exchanges, and the web is much harder. Why ENS chose to extend the existing internet namespace instead of inventing new roots ⤵️ ens.domains/blog/post/ens-…

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.

The agentic economy has a naming problem. As AI agents move into production, capable of holding wallets, signing transactions, and operating autonomously across days and weeks, the infrastructure underneath them has not kept pace. Agents can act. What they can't do is prove who they are across time, across contexts, and across the counterparties they interact with. Without persistent, verifiable identity, agents can't build reputation, can't be credentialed, and can't participate in systems that require accountability.

The Signal: AI Identity with Premm from Unruggable x.com/i/broadcasts/1…

@8004_scan up and to the right

Fresh ecosystem update and the growth curve is picking up real speed 📈 • 49,283+ registered AI agents (+130%) • 39,490+ feedback signals submitted (+149%) • 37,476+ active users (+67%) • 18 networks supported Agent count has more than doubled. Feedback activity is up nearly 1.5x. User participation keeps climbing..

Agentic Commerce is here! Most people don’t see it yet. But AI agents are about to become the biggest economic actors on the internet. 🧵

Starting today, agents can autonomously access blockchain data across 100+ networks, paying in @USDC via @coinbase's x402 standard. No human required. 🧵

Here is what we've been working on the past couple weeks. It's become clear to me that agents, especially in crypto, need their own hardware to fulfill their full potential. And this is fully open-source, LLM is verifiably private (no one can read your inputs and outputs), plus you can choose to run the model locally. LFG!

When I sat down with @provenauthority I was skeptical about whether proof of humanity matters. If AI actors have financial resources, who cares whether your site visitor - your customer - is a person or a machine? Mechanisms like CAPTCHA screen against bots, but only make sense in a world where bots aren't valuable (because they don't control assets) and humans are. The need easily dissolves when agents have their own money. Boy was I wrong. AI is going to be a Sybil attack on every human system. It's already begun. Agent activities are going to overwhelm our legal system, for one, which will need new approaches to understand who's responsible for what. A machine can't make a decision because a machine can't be held responsible... until, of course, through identity, it can be. If you haven't met Evin before - true to her handle - she is the ultimate authority on blockchain identity. We have shared a long journey, almost 10 years now, working together at @Consensys before she started @billions_ntwk. On the episode she also shares the exact architecture of Billions and how it takes a different approach from competing platform like World. No eyeballs were harmed in the making of this video. Please enjoy, subscribe, and comment! ✨

Need to share this. Summary from just last ENS x AI call: • @Esk3nder proposed Minimal Verifiable Agent Identity for ENS - learn more 👉 docs.google.com/document/d/1IS… • ENSIP-25 - officially merged - AI agent registry .eth name verification (first ever AI-related IP, shoutout to @nxt3d) - learn more 👉 docs.ens.domains/ensip/25 • ENSIP-26 - in-discussion - introduces universal agent context record - learn more 👉 github.com/ensdomains/ens… • Relevant ERCs mentioned: • ERC-8121: Cross-Chain Function Calls via Hooks - learn more 👉 eips.ethereum.org/EIPS/eip-8121 • ERC-8122: Minimal gas efficient Agent Registry - learn more 👉 eips.ethereum.org/EIPS/eip-8122 • ERC-8048: Onchain Metadata for Token Registries - learn more 👉 eips.ethereum.org/EIPS/eip-8048 • Organizational Metadata proposal mentioned as a solution for Agent identity (shoutout to @1a35e1 and @jkm__eth - learn more 👉 github.com/ensdomains/ens… • Created a public doc for defining Problem / Solution statements related AI agents (accepting community contributions) - learn more 👉 #heading=h.j36h3m7hnhcz" target="_blank" rel="nofollow noopener">docs.google.com/document/d/1--… • ENS registration agent built by @schmidsi (test and provide feedback) - learn more 👉 ens-registration.oskamai.com • @estmcmxci is taking the initiative to add an "AI" category on the ENS forum. • Exploring GoDaddy's ANS (Agent Name Service). • ...and a ton of great discussion and projects. You feel me? TG is public - "ENSxAI" Contributors, builders - welcome ⛩️ See you there 🫡