Add ERC: AI Agent Memory Access Rights#1752
Conversation
This ERC defines an interface for user-controlled access to AI agent memory records, including read, write, delete, and export functions.
File
|
| @@ -0,0 +1,234 @@ | |||
| --- | |||
| eip: XXXX | |||
There was a problem hiding this comment.
| eip: XXXX | |
| eip: 8264 |
Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.
Please also update the filename.
| title: AI Agent Memory Access Rights | ||
| description: An interface for user-controlled read, write, delete and export of AI agent memory records stored by any on-chain or off-chain memory provider. | ||
| author: Clavote (@clavote-boop) | ||
| discussions-to: https://ethereum-magicians.org/c/ercs/57 |
There was a problem hiding this comment.
Please create a topic on Eth Magicians for this ERC, with a link to this PR.
Per editor review on ethereum#1752: - eip: XXXX -> eip: 8264 (number assigned by editors) - rename erc-draft-ai-agent-memory-access-rights.md -> erc-8264.md - fix internal link ./eip-165.md -> ./erc-165.md Clears the EIP Walidator filename error and the Jekyll eiptable sort error (both caused by the non-numeric eip header / filename).
Resolves EIP Walidator errors on PR ethereum#1752: - description trimmed to <=140 chars - cite only merged ERCs by number: link ERC-8183 and ERC-173; drop references to ERC-8259/8239/8888 (those proposals are still open PRs with no merged file, so they cannot be linked and are not citable by number yet) - replaced with descriptive prose - title comment IERC-XXXX -> IERC-8264 Remaining: discussions-to must point to an Eth Magicians thread (topic pending creation).
ethereum/ERCs builds the site by renaming erc-*.md -> eip-*.md, so internal links must use ./eip-NNNN.md (matches every other ERC). Also link the "ERC-165 Support" heading so the first occurrence of the ERC-165 reference is a link (eipw markdown-link-first). Remaining CI item: discussions-to (Eth Magicians topic pending).
|
Thanks @abcoathup. Applied the assigned number:
CI is green except |
ERC-8264 discussion thread created: https://ethereum-magicians.org/t/erc-8264-ai-agent-memory-access-rights/28584 Clears the last EIP Walidator error on PR ethereum#1752.
|
@abcoathup — Eth Magicians discussion topic created and https://ethereum-magicians.org/t/erc-8264-ai-agent-memory-access-rights/28584 That clears the last EIP Walidator item. CI should now be green. |
|
Update — public CC0 reference implementation now live The reference implementation for this ERC is now public at https://github.com/clavote-boop/rmem-gateway. Contents:
cc @g11tech @jochem-brouwer @SamWilsn @xinbenlv — gentle ping for the one outstanding reviewer slot. Happy to address any composition concerns; the spec is intentionally orthogonal to ERC-8004, ERC-8183, EIP-7702, and ERC-7857. |
Documents a second reference implementation, RmemMemoryRegistry, deployed on Sepolia (11155111) and Base Sepolia (84532) at 0x2cf251859d172e292aa6a4ef4bbf7621b8117e4e. The interface is unchanged; the contract demonstrates the storage-layer and authorisation-layer freedoms the spec explicitly leaves to implementors (keccak256-commitment storage and subject-controlled on-chain Body-Lease delegation). Source: https://github.com/clavote-boop/rmem-gateway/tree/main/contracts (CC0).
|
The commit 951c012 (as a parent of 9330169) contains errors. |
eipw's markdown-rel-links rule forbids non-relative links and <url> autolinks in ERC text. Strip the etherscan/basescan/github links; keep the addresses and the source repo name as plain text. Renderers / reviewers can resolve them from context.
Third deployment of RmemMemoryRegistry. Same canonical address as Sepolia + Base Sepolia (deterministic from deployer EOA + nonce 0). All three pass supportsInterface(0x13a642d4) and supportsInterface(0x01ffc9a7).
|
Update — RmemMemoryRegistry deployed and live on three testnets (2026-05-22). Linked addresses for reviewer convenience (block explorer pages — kept out of the ERC text itself because eipw's
Each contract responds Source: This reference impl is a second, lease-aware extension alongside the in-spec |
3 participants
Summary
This PR introduces a new draft ERC: AI Agent Memory Access Rights — a minimal four-function on-chain interface (
readMemory,writeMemory,deleteMemory,exportMemory) through which an Ethereum address asserts sovereign control over AI agent memory records that reference that address.Motivation
AI agents on EVM-compatible networks accumulate memory about their principals (conversation history, preferences, delegated context). No standardised on-chain mechanism currently allows a principal to read, correct, delete, or port those records. This gap has direct GDPR implications (Articles 15–20) and is structurally identical to the problem solved for token ownership by ERC-20/721 — but for data rights.
Relationship to existing ERCs
This ERC addresses user data rights over stored memory inputs, not agent outputs, identity, skills, or commerce. It is composable with all four.
Interface surface
Four functions + two events. No storage layout mandate. No backend opinion. ERC-165 support required. Analogous in size to ERC-165 itself.
Checklist
requires: 165declareddiscussions-topoints to Ethereum Magicians ERCs category (to be updated with thread URL once TL1 reached)Notes for editors
The
discussions-tofield currently points to the ERCs category (https://ethereum-magicians.org/c/ercs/57). A dedicated thread will be posted and the field updated via a follow-up commit once the account reaches Trust Level 1. This is consistent with the approach taken by ERC-8259 (PR #1730).