Add ERC: Agent Onchain Metadata Extension (ERC-8004 Compatible) #1532
+149
−0
Conversation
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
Define standard onchain metadata keys for ERC-8004 agent registries, including , , , , and per-endpoint keys like and . Onchain values override the corresponding fields in the ERC-8004 registration JSON (or data URLs), and provides a more flexible account identifier than the reserved , including support for counterfactual and CAIP-10 style addresses. Co-authored-by: Cursor <cursoragent@cursor.com>
Rename _metdata_extension to _metdata_extension.md so the draft follows the ERCs repo markdown conventions. No content changes beyond the filename. Co-authored-by: Cursor <cursoragent@cursor.com>
Add snake_case keys for x402_support, active, and supported_trust, map them to their corresponding ERC-8004 JSON fields, and document a simple sync guideline between per-key onchain metadata and agentURI while keeping onchain values authoritative when both are present. Co-authored-by: Cursor <cursoragent@cursor.com>
Collaborator
File
|
|
The commit 9e45aee (as a parent of c807d4b) contains errors. |
abcoathup
reviewed
Feb 11, 2026
| @@ -0,0 +1,149 @@ | |||
| --- | |||
| eip: XXXX | |||
Contributor
There was a problem hiding this comment.
Suggested change
| eip: XXXX | |
| eip: 8156 |
Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.
Please also update the filename.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR introduces an onchain metadata extension for ERC-8004 agent registries. It defines a set of standard snake_case keys (name, description, image, agent_account, x402_support, active, supported_trust, and endpoint/ / endpoint//version) stored via ERC-8004’s existing getMetadata / setMetadata functions. Each key maps directly to a specific field in the ERC-8004 registration JSON, so the full JSON payload can be mirrored onchain when desired.
The extension is fully compatible with ERC-8004: existing agents that don’t use onchain metadata continue to work unchanged via agentURI, and registries don’t need new contracts or storage layouts. When both onchain values and an agentURI JSON exist, clients following this ERC are required to treat the per-key onchain values as authoritative overrides of the corresponding JSON fields, while agentURI maintains compatibility with ERC-8004.