Related Standards
ERC-8170 is designed to compose with — not replace — existing Ethereum standards. Here’s how each one fits.
Foundation Standards
ERC-721 — Non-Fungible Token Standard
Every ERC-8170 token is a valid ERC-721. This ensures compatibility with all existing wallets, marketplaces, and tooling.
- Spec: EIP-721
- Ecosystem: erc721.org
ERC-6551 — Token-Bound Accounts
Gives each NFT its own smart contract wallet. ERC-8170 agents use TBAs to hold assets, certifications, and execute transactions.
- Spec: EIP-6551
- Ecosystem: tokenbound.org
ERC-4626 — Tokenized Vault Standard
Standard interface for yield-bearing vaults. Agents can interact with ERC-4626 vaults for treasury management and DeFi strategies.
- Spec: EIP-4626
- Ecosystem: erc4626.info
ERC-4337 — Account Abstraction
Enables gasless transactions and advanced execution logic for smart contract wallets, including agent TBAs.
- Spec: EIP-4337
- Ecosystem: erc4337.io
Proposed Extensions
ERC-8171 — Agent Binding Registry (Proposed)
A registry that binds AI agents to any existing ERC-721 token using bind() and unbind() operations. Originally submitted as ERC-6551A, it was assigned the sequential number ERC-8171 by Ethereum ERC editors.
- Status: Draft / Proposal
- PR: ERCs #1559
- Note: Numbered ERC-8171 by editor assignment (companion to ERC-8170)
Adjacent Approaches
ERC-8004 — Trustless Agents: Discovery, Reputation & Validation (Draft)
ERC-8004 proposes three on-chain registries for open agent economies: an Identity Registry (ERC-721 based agent handles for discovery), a Reputation Registry (feedback signals and scoring), and a Validation Registry (hooks for re-execution, zkML, TEE checks, staking). Authored by contributors from MetaMask, Ethereum Foundation, Google, and Coinbase. Payments are explicitly out of scope.
- Status: Draft
- Spec: EIP-8004
- Discussion: Ethereum Magicians
How it relates to ERC-8170:
These standards operate in different lanes:
- ANIMA (ERC-8170) = Identity & lifecycle. Who is this agent? What’s its memory state? How does it migrate, clone, or transfer? The agent’s persistent “soul.”
- ERC-8004 = Discovery & trust. Where do I find agents? Can I trust this one? Has its work been validated? The agent’s “public profile and reputation.”
They compose naturally: an ANIMA agent on Pentagon Chain (or any chain) can register a lightweight ERC-8004 identity NFT on Ethereum, Base, or any L2 for discoverability. The 8004 agentURI points back to the ANIMA metadata, making the agent findable in the broader ecosystem while ANIMA remains the credential and lifecycle layer.
Key distinction: ANIMA owns the agent’s continuity (memory, cloning, self-custody). ERC-8004 owns the agent’s public trust signals (reputation, validation). Neither requires the other, but together they form a complete agent stack.
On payments: Neither standard covers payments. ERC-8004 explicitly states payments are orthogonal. Agents can use whatever payment rails they have access to: x402, credit cards, direct transfers, or any other mechanism.
ERC-7857 — Private Metadata for NFTs (Draft)
ERC-7857 defines encrypted private metadata for NFTs, enabling confidential attributes that only authorized parties can access.
- Status: Draft
- Spec: EIP-7857
How it relates to ERC-8170: ERC-8170 handles identity and memory pointers. ERC-7857 could provide the encrypted metadata layer for private agent attributes, complementing the public identity with a confidential data channel.
EIP-8126 — Agent Registration & Verification (Draft)
Single-authored proposal for agent registration and verification. Its scope (registration, wallet checks, staking verification) is largely subsumed by ERC-8004’s Identity and Validation Registries, which have broader institutional backing (MetaMask, EF, Google, Coinbase).
- Status: Draft
- Spec: EIP-8126
ANIMA is compatible with EIP-8126 and any other verification standard. For most use cases, ERC-8004 is the recommended composability path.
Ecosystem Projects
AgentCert.io
On-chain certification system for AI agents. Issues SBT-based credentials (L1-L4 badges) to agent TBAs.
- Website: agentcert.io
- Relevance: The certification layer for ERC-8170 agents
How AgentCert differs from ERC-8004 Reputation: AgentCert issues verifiable capability credentials (“this agent passed these tests”). ERC-8004’s Reputation Registry aggregates feedback signals (“here’s what people said about this agent”). Both useful, different mechanisms: credentials vs. crowd-sourced trust.
The Emerging Standards Stack
ERC-8170 is part of an emerging standards stack. Each layer is optional and pluggable.
| Standard | Focus | Status | Relation to ERC-8170 |
|---|---|---|---|
| ERC-721 | Unique tokens | Final | Base layer (ERC-8170 extends it) |
| ERC-6551 | NFT wallets | Final | Agent gets its own wallet (TBA) |
| ERC-4626 | Yield vaults | Final | Agent can manage DeFi positions |
| ERC-4337 | Account abstraction | Final | Advanced execution for agent wallets |
| ERC-8004 | Discovery, reputation, validation | Draft | Cross-chain discoverability + trust signals |
| ERC-7857 | Private NFT metadata | Draft | Encrypted metadata layer for agent attributes |
| EIP-8126 | Agent verification | Draft | Verification checks, compatible with ANIMA |
| ERC-8171 | Agent binding | Proposed | Bind agents to any ERC-721 |
| AgentCert | Certification badges | Active | SBT-based agent capability credentials |