ENSIP-25: AI Agent Registry ENS Name Verification#61
Merged
adraffy merged 9 commits intoensdomains:masterfrom Feb 18, 2026
Merged
ENSIP-25: AI Agent Registry ENS Name Verification#61adraffy merged 9 commits intoensdomains:masterfrom
adraffy merged 9 commits intoensdomains:masterfrom
Conversation
This ENSIP defines a standardized method for verifying ENS names associated with AI Agent registries using text records with the format "agent-registry:<ERC-7930 based chain ID>". Key features: - Enables bidirectional verification between AI agent registries and ENS names - Supports multichain agents using ERC-7930 based chain ID format - Uses CAIP-350 address format with EIP-55 checksumming for Ethereum - Defines both registry-to-ENS and ENS-to-registry verification flows - Allows single ENS name to reference multiple agent registries across chains - Includes examples for Ethereum, Polygon, Avalanche, and Solana
- Change double quotes to backticks for format specification in Abstract - Update verification method to use 'ERC-7930 based chain ID' consistently
Major changes: - Switch from text records to ENSIP-24 data() records - Use prioritized keys: agent-registry and agent-registry: N (N = 1, 2, 3, ...) - Store full ERC-7930 address (chain + address) in record value - Require minimum 5 keys to check (agent-registry through agent-registry: 4) - Add TOON format attribution for key structure - Update examples with ERC-7930 spec-compliant bytes - Clarify discovery vs verification flows
- Change from ENSIP-24 data() records to text records for human readability - Use ERC-8127 Token Identifier format (<agentId>@<registry>) for values - Add verify-agent-registry parameterized key for direct lookup without iteration - Add raffy.eth as contributor
|
Is there a reference implementation or demo available that shows this working end-to-end? |
Contributor
Author
https://github.com/unruggable-labs/agent0-ts/tree/feat/add-verifyENSName We have a PR ready to go for Agent0. We also made a small addition to ENSIP-25 and will update this code to use it as well. |
ENSIP-25 Revision
adraffy
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds ENSIP-25, which defines a standardized method for verifying ENS names associated with AI agent registries using text records. The specification enables bidirectional verification between AI agent registries and their corresponding ENS names, and provides a direct lookup method for efficient verification without iteration.
Key Features
<agentId>@<registry>)agent-registryandagent-registry: N(where N = 1, 2, 3, ...) for multiple registry entries with explicit priority orderverify-agent-registry: <agentId>@<registry>parameterized key for direct lookup without iterating over listsSpecification Details
agent-registry(highest priority) andagent-registry: Nusing ERC-8119 format for structured keys<agentId>@<registry>(e.g.,167@0x00010000010114...)verify-agent-registry: <agentId>@<registry>with any non-empty valueReferences