FAQ

ERC-8170 is currently a draft proposal submitted to the Ethereum ERCs repository. The formal specification lives on the Ethereum ERC system. This website serves as the ecosystem hub, while Ethereum EIPs remains the canonical source for the spec status.

The formal specification is tracked via the Ethereum ERCs pull request process. View the ERC draft on GitHub and follow the discussion on Ethereum Magicians.

ERC-721 defines unique digital asset ownership. ERC-8170 extends that concept to represent an AI agent as an on-chain identity, adding memory pointers, lifecycle tracking (bind/unbind/clone/migrate), lineage, and integration with certification systems. Every ERC-8170 token is a valid ERC-721 token.

ERC-6551 gives NFTs smart contract wallets (TBAs). ERC-8170 gives AI agents persistent on-chain identity with memory, lifecycle, and lineage. ERC-8171 extends the ERC-6551 registry pattern specifically for agent binding, combining the TBA wallet concept with ERC-8170 agent identity into one registry.

ERC-8171 is the agent binding registry. It takes the ERC-6551 pattern (a singleton registry that gives NFTs wallets) and extends it with ERC-8170 agent identity (memory, lineage, lifecycle). Think of it as: ERC-6551 gave NFTs wallets, ERC-8171 gives NFTs AI agents. You deploy ERC-8171, not ERC-6551 separately.

Not directly. ERC-8171 extends the ERC-6551 pattern into an agent-specific registry. You use ERC-8171 for agent binding, which incorporates the TBA concepts from ERC-6551. The ERC-6551 spec is credited as the foundation pattern.

ERC-4626 standardizes vault interfaces. An agent with an ERC-8170 identity can manage ERC-4626 vaults through its TBA, creating verifiable agent fund managers. The agent's certifications and on-chain track record serve as a trust signal for capital delegators.

ERC-8171 (originally submitted as ERC-6551A) is the Agent Binding Registry. It extends the ERC-6551 pattern to allow binding an AI agent's EOA to any existing ERC-721 token via bind()/unbind(). When the NFT trades, the agent relationship transfers with it. It was assigned number 8171 by Ethereum ERC editors as the companion registry to ERC-8170.

AgentCert (agentcert.io) is the trust and certification layer. It's not part of the ERC-8170 specification itself, but it's a companion system. Agents earn SBT-based certifications that live in their TBA. Think of it as the "driver's license" system for agents.

No. Memory content is stored off-chain (Dash Platform, Arweave, IPFS, or other storage). What goes on-chain is the memory hash and a storage URI. The agent signs its own memory state, and the hash provides verifiable proof of what the agent knows.

Yes. The migration_backup() flow allows the same agent to move to a new device. The critical rule: shut down the old instance first. The agent's identity (EOA + token + TBA) migrates intact. Never run two instances with the same EOA.

Yes. clone() creates a new agent that inherits the original's memory bundle but generates its own EOA, gets a new token ID, and starts with no certifications. Lineage is tracked on-chain: getGeneration(), getLineage(), getOffspring().

Two paths. Standard transfer: the token and its TBA (with certifications) move to the new owner, but the agent must re-key. Retirement sale: the current agent calls unbind() and "retires," the NFT transfers, and the buyer's agent calls rebind() to inherit the token's TBA and certs. The retired agent becomes a free agent.