Skip to content

Add ERC: Inheritable Agent Mandates - #1930

Open
adn-ia wants to merge 7 commits into
ethereum:masterfrom
adn-ia:add-erc-inheritable-agent-mandates
Open

Add ERC: Inheritable Agent Mandates#1930
adn-ia wants to merge 7 commits into
ethereum:masterfrom
adn-ia:add-erc-inheritable-agent-mandates

Conversation

@adn-ia

@adn-ia adn-ia commented Aug 5, 2026

Copy link
Copy Markdown

This PR submits a new Standards Track ERC: Inheritable Agent Mandates.

It defines an on-chain mandate — a small bundle of limits (a spend cap, an expiry, a reproduction budget, an optional life-lease, an allowed-payee set, and a freeze flag) that is welded into an agent's on-chain identity, inherited automatically by every child the agent spawns, and non-strippable: altering any clause changes the identity. Inheritance is one-directional and narrowing (child ⊆ parent on every clause); the generation counter (a "telomere") can only decrease, and a freeze on any ancestor cascades to the whole subtree.

Discussion (Ethereum Magicians): https://ethereum-magicians.org/t/inheritable-agent-mandates-a-non-strippable-inherited-leash-for-on-chain-agents/29275

A reference implementation is deployed on Base Sepolia with reproducible on-chain proofs of the inheritance, freeze-cascade, expiry, and non-strippability properties (see the Reference Implementation section of the ERC).

@eip-review-bot

eip-review-bot commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

File ERCS/erc-8370.md

Requires 1 more review from Editors: @g11tech, @jochem-brouwer, @samwilsn, @xinbenlv

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

The commit cc18ba6 (as a parent of d5cfbdc) contains errors.
Please inspect the Run Summary for details.

@github-actions github-actions Bot added the w-ci label Aug 5, 2026
@github-actions github-actions Bot removed the w-ci label Aug 5, 2026
Attribue le standard à son auteur nommé plutôt qu'au seul handle de
l'organisation. Le format `Nom (@handle)` reste conforme à EIP-1.
Comment thread ERCS/erc-8367.md Outdated
Comment thread ERCS/erc-8370.md Outdated
@adn-ia

adn-ia commented Aug 6, 2026

Copy link
Copy Markdown
Author

Thanks @abcoathup — all three addressed. Renamed erc-8367.md to erc-8370.md and set eip: 8370 (19a39b9). Updated discussions-to to the ERC-8370 topic slug in f5b9d49 (https://ethereum-magicians.org/t/erc-8370-inheritable-agent-mandates/29275), applied as a fresh commit since the suggestion couldn't auto-apply after the rename. Retitled the Ethereum Magicians thread to "ERC-8370: Inheritable Agent Mandates". EIP Validator and Link Check are green — happy to make any further changes.

adn-ia added 2 commits August 7, 2026 08:56
… ERC-8004, not assumed

My justification was wrong. I wrote that transferring an ERC-8004 identity detaches
whatever was tied to it. Tested against the deployed Identity Registry, that is not
what happens: transfer clears only the reserved `agentWallet` key. Arbitrary metadata
— including a mandate written there — survives the transfer intact.

The real risk is different, and worse: the clauses persist but become rewritable by
whoever now holds the token. Acting as the new owner, a single `setMetadata` call reset
a declared spend cap from 1000 to 999,999,999 and a generation counter from 3 to 255,
with no refusal.

A leash whose setting is controlled by the holder is not a leash. The conclusion is
unchanged — non-transferability remains load-bearing — but for a sounder reason than
the one I had written.

No contract changed. This edits the Rationale prose only.
@adn-ia

adn-ia commented Aug 19, 2026

Copy link
Copy Markdown
Author

All three review items from @abcoathup are applied, and both threads are now
resolved: the file was renamed to erc-8370.md with eip: 8370 (19a39b9), and
discussions-to was updated to the ERC-8370 topic (f5b9d49).

All nine checks are green on 4fa8967, including EIP Walidator.

Nothing is outstanding on my side. The PR has been in this state since 10 August
and is waiting on editor review. Happy to make any further change — just say what.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants