ERC-725
Smart Contract Standard
Open Standard
Links
Details
License https://github.com/ERC725Alliance/ERC725
Dev Status 🏁 Final
Dev Status Detail Final (ERC-725v2 stabilized; ERC-725Y as standalone key-value store widely implemented)
Owner Fabian Vogelsteller / Ethereum Community
Country Global / Decentralized
Start Year 2017
Stack Solidity / EVM
Funding LUKSO ecosystem / Fabian Vogelsteller; ERC725Alliance community
Last Investigated Mar 9, 2026
Smart Contract Standard Attributes
Origins Proposed by Fabian Vogelsteller (also ERC-20 author) as a foundation for self-sovereign identity on Ethereum; influenced by early W3C DID discussions and the need for a universal identity contract capable of holding keys, claims, and execution rights.
Data Formats ABI-encoded key-value pairs (bytes32 keys, bytes values); LSP (LUKSO Standard Proposals) JSON metadata schemas for profile data; ERC-165 interface detection
Terms CC0
Funds Unknown
Based On ERC-20 (Vogelsteller's prior work); W3C DID concepts; ERC-735 (claim holder, associated standard)
Permissions Permissionless deployment; key-based execution rights; operator/controller patterns
Development Tools erc725.js library, LUKSO tools, OpenZeppelin adaptations, ERC725Alliance reference implementations
Protocol Maturity / Standardization Final; foundational to LUKSO blockchain and Universal Profiles; adopted in ERC-725Y form across identity-focused projects
Trust Framework Key manager contract with role-based execution rights; claim verifier contracts for on-chain attestations; controller key hierarchy
Target Application Domain Decentralized identity, self-sovereign identity (SSI), Universal Profiles, DAO membership, credential management, on-chain reputation
Deployment Model Per-identity contract deployment; each user or entity has a dedicated ERC-725 contract instance
Standard Type Identity Standard
Ecosystem Ethereum; particularly adopted in LUKSO ecosystem