Add ERC: Delayed Metadata Update Extension#1561
Open
Cyberpaisa wants to merge 4 commits intoethereum:masterfrom
Open
Add ERC: Delayed Metadata Update Extension#1561Cyberpaisa wants to merge 4 commits intoethereum:masterfrom
Cyberpaisa wants to merge 4 commits intoethereum:masterfrom
Conversation
This proposal defines an optional extension to ERC-8004 that introduces a delayed metadata update mechanism for agent identity records, preventing immediate mutation after verification.
Collaborator
File
|
eip-review-bot
changed the title
abcoathup
reviewed
Feb 23, 2026
ERCS/erc-8407.md
Outdated
| @@ -0,0 +1,124 @@ | |||
| --- | |||
| eip: 8407 | |||
Contributor
There was a problem hiding this comment.
Suggested change
| eip: 8407 | |
| eip: 8172 |
Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.
Please also update the filename.
Author
There was a problem hiding this comment.
Hi @abcoathup, thanks for the review. Both changes are done:
- Renamed to ERC-8172 per your assignment (file and preamble updated)
- Created the discussion topic: https://ethereum-magicians.org/t/erc-8172-delayed-metadata-update-extension/27808
- Updated the discussions-to field in the preamble
Let me know if anything else is needed.
Contributor
There was a problem hiding this comment.
@Cyberpaisa you need to fix the validator issues (references to ERC-8004) and then wait for an ERC editor to review (which I am not).
abcoathup
reviewed
Feb 23, 2026
ERCS/erc-8407.md
Outdated
| title: Delayed Metadata Update Extension | ||
| description: Optional extension for ERC-8004 to prevent post-verification mutation attacks | ||
| author: Cyberpaisa (@Cyberpaisa) | ||
| discussions-to: https://ethereum-magicians.org/t/erc-8004-trustless-agents/25098 |
Contributor
There was a problem hiding this comment.
Please create a discussions topic for this ERC.
Author
|
[image: Captura de pantalla 2026-02-22 a la(s) 7.49.01 p.m..png]
Hi Andrew,
Regarding your request to create a discussion topic for the ERC, I am
experiencing an issue with the forum. It is not allowing me to post;
whenever I try, I receive an error message.
Could you please help me or guide me on how to resolve this? I would
appreciate your assistance.
Best regards,
Cyberpaisa
El dom, 22 feb 2026 a las 19:46, Andrew B Coathup ***@***.***>)
escribió:
… ***@***.**** commented on this pull request.
------------------------------
In ERCS/erc-8407.md
<#1561 (comment)>:
> @@ -0,0 +1,124 @@
+---
+eip: 8407
+title: Delayed Metadata Update Extension
+description: Optional extension for ERC-8004 to prevent post-verification mutation attacks
+author: Cyberpaisa ***@***.***)
+discussions-to: https://ethereum-magicians.org/t/erc-8004-trustless-agents/25098
Please create a discussions topic for this ERC.
—
Reply to this email directly, view it on GitHub
<#1561 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6OIWURSIOQRYZY55B6EPLL4NJEW5AVCNFSM6AAAAACV34AH3KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTQMZYG42TINRUGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Contributor
I've bumped your permissions so you should be able to create a new topic. |
Updated discussions-to link for ERC-8172.
|
The commit d01b0e5 (as a parent of 279dcc0) contains errors. |
Cyberpaisa
added a commit
to Cyberpaisa/super-sentinel
that referenced
this pull request
Feb 23, 2026
Layer 1 (active): Listens for URIUpdated events on the ERC-8004 registry, tracks change frequency per agent, pre-scans new URIs, and generates alerts for suspicious patterns. Integrates with TRACER as "uri-stability" sentinel feeding the Trust dimension. Layer 2 (future): Types and ABIs prepared for ERC-8172 Delayed Metadata Update Extension (ethereum/ERCs#1561) with block-based cooldown — PendingURIChange, PendingURICancelled, URIChangedWithoutCooldown events ready for when the contract adopts the standard. 42 new tests, 165 total passing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
abcoathup
reviewed
Feb 26, 2026
ERCS/erc-8172.md
Outdated
|
|
||
| ## Abstract | ||
|
|
||
| This proposal defines an optional extension to [ERC-8004](./erc-8004.md) that introduces a delayed metadata update mechanism for agent identity records. The extension prevents immediate mutation of agent metadata after verification by introducing a pending state and activation delay. |
Contributor
There was a problem hiding this comment.
Suggested change
| This proposal defines an optional extension to [ERC-8004](./erc-8004.md) that introduces a delayed metadata update mechanism for agent identity records. The extension prevents immediate mutation of agent metadata after verification by introducing a pending state and activation delay. | |
| This proposal defines an optional extension to [ERC-8004](./eip-8004.md) that introduces a delayed metadata update mechanism for agent identity records. The extension prevents immediate mutation of agent metadata after verification by introducing a pending state and activation delay. |
abcoathup
reviewed
Feb 26, 2026
ERCS/erc-8172.md
Outdated
|
|
||
| ## Motivation | ||
|
|
||
| [ERC-8004](./erc-8004.md) allows agents to update metadata instantly via URI changes. While this provides flexibility, it also creates a risk where an agent can pass verification and then immediately swap its endpoint or configuration. |
Contributor
There was a problem hiding this comment.
Suggested change
| [ERC-8004](./erc-8004.md) allows agents to update metadata instantly via URI changes. While this provides flexibility, it also creates a risk where an agent can pass verification and then immediately swap its endpoint or configuration. | |
| [ERC-8004](./eip-8004.md) allows agents to update metadata instantly via URI changes. While this provides flexibility, it also creates a risk where an agent can pass verification and then immediately swap its endpoint or configuration. |
abcoathup
reviewed
Feb 26, 2026
ERCS/erc-8172.md
Outdated
|
|
||
| ## Rationale | ||
|
|
||
| The proposal introduces minimal additional storage and events. It does not mandate a specific cooldown duration or update policy. This preserves [ERC-8004](./erc-8004.md)'s flexibility while providing stronger guarantees for ecosystems requiring higher trust signals. |
Contributor
There was a problem hiding this comment.
Suggested change
| The proposal introduces minimal additional storage and events. It does not mandate a specific cooldown duration or update policy. This preserves [ERC-8004](./erc-8004.md)'s flexibility while providing stronger guarantees for ecosystems requiring higher trust signals. | |
| The proposal introduces minimal additional storage and events. It does not mandate a specific cooldown duration or update policy. This preserves [ERC-8004](./eip-8004.md)'s flexibility while providing stronger guarantees for ecosystems requiring higher trust signals. |
abcoathup
reviewed
Feb 26, 2026
ERCS/erc-8172.md
Outdated
|
|
||
| ## Backwards Compatibility | ||
|
|
||
| This extension is fully optional. Contracts not implementing it remain compliant with [ERC-8004](./erc-8004.md). Clients SHOULD monitor new events when available but MUST remain compatible with legacy behavior. |
Contributor
There was a problem hiding this comment.
Suggested change
| This extension is fully optional. Contracts not implementing it remain compliant with [ERC-8004](./erc-8004.md). Clients SHOULD monitor new events when available but MUST remain compatible with legacy behavior. | |
| This extension is fully optional. Contracts not implementing it remain compliant with [ERC-8004](./eip-8004.md). Clients SHOULD monitor new events when available but MUST remain compatible with legacy behavior. |
Fix ERC-8004 references to use eip-8004.md per reviewer feedback
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
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 proposal defines an optional extension to ERC-8004 that introduces a delayed metadata update mechanism for agent identity records, preventing immediate mutation after verification by adding a cooldown period for metadata updates.