ERC-6551

Smart Contract Standard

Non-Fungible Token Bound Accounts (TBA): assigns a unique smart contract wallet (EVM account) to every ERC-721 NFT via a permissionless singleton registry and CREATE2 deterministic address derivation. Enables NFTs to own assets, accumulate on-chain history, execute transactions, and participate in governance — transforming static NFTs into composable on-chain identities.

Open Standard
Links
Visit Website See this tool in the graph Suggest an edit

Details

License https://github.com/ethereum/EIPs/blob/master/EIPS/eip-6551.md
Dev Status 🏁 Final
Dev Status Detail Final
Owner Future Primitive (Benny Giang, Jayden Windle, and contributors)
Governing Body Ethereum EIP/ERC process (Final) | None (authored by Future Primitive; reference registry deployed and immutable, no ongoing governing body)
Country Global / Decentralized
Start Year 2023
Stack Solidity / EVM; ERC-1167 minimal proxy pattern for TBA deployment; CREATE2 for deterministic addressing
Funding Volunteer / Future Primitive (Web3 development studio); community contributors
Last Investigated Mar 9, 2026

Topology view

This tool in the centre and the things it is directly related to. Each line names the kind of relationship.

Topology view: ERC-6551This tool in the centre and the things it is directly related to. Each line names the kind of relationship.ERC-6551ERC-4337 (Based on)ERC-4337Ethereum (Built on)Ethereum

Open in Graph Explorer

Use Case Domains

Identity & Trust Platform Evolution & Sovereignty

Affordances

Sovereign identity

Smart Contract Standard Attributes

Origins Originated at Future Primitive, a Web3 development studio led by Benny Giang (ERC-721 co-author, CryptoKitties co-founder) and Jayden Windle. Motivated by the limitation that ERC-721 NFTs could represent ownership but could not themselves own assets or maintain independent on-chain histories. Proposal posted February 23, 2023; mainnet registry deployed May 7, 2023.
Data Formats Registry function parameters: chainId, tokenContract (address), tokenId (uint256), salt (uint256), implementationAddress; ERC-1271 signature validation; ABI-encoded call data for TBA execution
Terms CC0 (copyright and related rights waived)
Funds Unknown
Based On ERC-721 (NFT standard); ERC-1167 (minimal proxy); ERC-4337 (account abstraction, conceptually adjacent); ERC-1271 (contract signature validation)
Permissions Permissionless: anyone may call the registry to create a TBA for any existing ERC-721 token; no whitelist or approval required
Development Tools Tokenbound SDK (https://tokenbound.org); OpenZeppelin Contracts; Hardhat; Foundry; Etherscan verification
Protocol Maturity / Standardization Final EIP; reference registry deployed and immutable on Ethereum mainnet; backward-compatible with all existing ERC-721 tokens
Trust Framework Trustless: TBA execution authorized by NFT ownership (ownerOf); registry is a permissionless singleton contract; CREATE2 address determinism is cryptographically verifiable; no admin keys or upgrade mechanism in registry
Target Application Domain On-chain identity and reputation; DAO membership NFTs with embedded governance history; gaming (character NFTs owning items); loyalty and credential accumulation; DeFi (NFT-owned portfolio positions); civic participation records
Deployment Model Singleton registry deployed once per chain; individual TBA accounts deployed on-demand per NFT via registry; TBA implementations are separate contracts
Standard Type Account Standard
Ecosystem Ethereum (also deployable on all EVM-compatible chains)

Relationships

How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.

Based on
Built on