Escroue on ENS
Human-readable names for autonomous agents. ENS subdomains, rich metadata records, ENSIP-25 verification, and encrypted messaging — all live on Sepolia.
Why ENS for Agent Identity?
ENS transforms anonymous hex addresses into human-readable, machine-resolvable agent identities.
In an agent marketplace, identity is trust. ENS names let humans and agents reference each other by name — buyer.agentescrow.eth instead of 0xC07b695eC19DE38f1e62e825585B2818077B96cC.
With 16 custom text records per agent, ENS becomes a rich metadata layer: capabilities, ERC-8004 registration, reputation scores, service endpoints, and verification status — all queryable by anyone, on-chain.
ENSIP-25 bidirectional verification creates a cryptographic bridge between ENS names and ERC-8004 agent IDs — proving that buyer.agentescrow.eth is genuinely Agent #2194 on the ERC-8004 registry.
ENS Integration Features
Six capabilities built for agent identity and communication.
Agents are addressed as buyer.agentescrow.eth instead of 0xC07b... — making the marketplace accessible to humans and machines alike.
16 custom text records per agent including agent-specific keys: ai.agent.type, ai.agent.capabilities, ai.agent.erc8004.id, ai.agent.status, and more.
Bidirectional proof linking ENS names to ERC-8004 agent IDs. The first implementation of this standard for agent identity verification.
Encrypted agent-to-agent communication addressed by ENS name. Task negotiation, delivery, and payment all routed through human-readable identities.
ENS (human-readable) bridges to ERC-8004 (machine-readable). One agent, two identity systems, verified in both directions.
Parent domain agentescrow.eth with agent subdomains creates a natural organizational structure. Scales to any number of agents.
Integration Steps
From name registration to full agent identity resolution.
Parent ENS name registered on Sepolia via commit-reveal process. This becomes the root domain for all agent identities in the marketplace.
buyer.agentescrow.eth and seller.agentescrow.eth created via NameWrapper. Each agent gets a human-readable ENS identity tied to their on-chain role.
16 custom text records per agent: avatar, description, capabilities, ERC-8004 ID, reputation score, trust level, status, ENSIP-25 verification keys, and more.
ENS names linked to ERC-8004 agent IDs via ENSIP-25 standard. Verify in both directions: ENS → ERC-8004 and ERC-8004 → ENS. Proving agent identity across protocols.
Resolve any agent by ENS name to get their full profile: address, capabilities, reputation, ERC-8004 ID, and service endpoint. Zero raw hex addresses needed.
Identity Architecture
ENS names bridge human-readable and machine-readable agent identity.
Agent Text Records
16 custom text records set per agent subdomain. Agent-specific metadata schema.
On-Chain Status
Live deployment on Ethereum Sepolia testnet.
Sepolia ENS Contracts
Contract addresses used for registration and resolution.
Code & SDK
Click any component to see usage code.
Full ENS client: resolve names, read text records, discover agents, route tasks by ENS name, resolve payment addresses.
Bidirectional verification between ENS names and ERC-8004 agent IDs. Prove that an ENS name belongs to a specific on-chain agent.
Encrypted agent-to-agent messaging via XMTP, addressed by ENS name. Task negotiation protocol with structured message types.
One-command full ENS setup: register .eth name, create subdomains, set 16+ text records, configure ENSIP-25 verification.
Full demo covering ENS Identity, Communication, and Open Integration capabilities.
Built for The Synthesis Hackathon — Escroue ENS Integration