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.

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.

ERC-4626 — Tokenized Vault Standard

Standard interface for yield-bearing vaults. Agents can interact with ERC-4626 vaults for treasury management and DeFi strategies.

ERC-4337 — Account Abstraction

Enables gasless transactions and advanced execution logic for smart contract wallets, including agent TBAs.

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-7857 — Private Metadata for NFTs (Draft)

ERC-7857 defines encrypted private metadata for NFTs, enabling confidential attributes that only authorized parties can access.

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)

EIP-8126 focuses on agent registration and verification, including wallet, endpoint, contract, and staking checks, with optional provider-based risk scoring.

How it relates to ERC-8170:

These standards answer different questions:

  • ERC-8170 answers: What is this agent on-chain? How does it persist? What does it control? How does it migrate or evolve?
  • EIP-8126 answers: Has this agent been checked? By whom? Against what criteria? What risk signals were produced?

ERC-8170 is the identity-focused approach. EIP-8126 is the verification-focused approach. They are complementary rather than competing: an agent could have an ERC-8170 identity and also be registered in an EIP-8126 verification registry.

Ecosystem Projects

AgentCert.io

On-chain certification system for AI agents. Issues SBT-based credentials to agent TBAs.

  • Website: agentcert.io
  • Relevance: The trust and certification layer for ERC-8170 agents

The Emerging Standards Stack

ERC-8170 is part of an emerging standards stack around agent identity, token-bound accounts, vault integration, and verification. The ecosystem includes a mix of mature standards (ERC-721, ERC-4626) and still-evolving proposals (ERC-6551, EIP-8126, ERC-8170 itself).

StandardFocusStatusRelation to ERC-8170
ERC-721Unique tokensFinalBase layer (ERC-8170 extends it)
ERC-6551NFT walletsReviewAgent gets its own wallet
ERC-4626Yield vaultsFinalAgent can manage DeFi positions
ERC-4337Account abstractionFinalAdvanced execution for agent wallets
ERC-7857Private NFT metadataDraftEncrypted metadata layer for agent attributes
EIP-8126Agent verificationDraftVerification checks, complementary to identity
ERC-8171Agent bindingProposedBind agents to any ERC-721
AgentCertTrust/certsActiveAgent reputation and certification