NFT Standards Wiki
  • NFT Standards Wiki READ.me
  • NFT Basics
    • All things NFTs
    • NFT Usecases
    • NFT API
  • NFT License
  • NFT Platforms
  • NFT Metadata
  • NFT Readings
  • NFT Soulbound Tokens
  • NFT Storage
  • Working Group
    • Workflow Basics
    • Events & Discussions
    • Communications
    • Working draft Structure
    • Roadmap
    • Permits NFT Overview
    • New standard suggestions
    • ERC & EIP Related Links
  • Working Group EIPs and Implementations
    • EIP4494 Permits for ERC721
    • EIP 4907 User And Expires Extension
    • ERC Identify NFT Content Type
    • JSON Metadata Standard
    • Permit Singleton
  • Standards
    • ERC721 Non Fungible Standard
    • ERC1155 Multi token
    • ERC725 Smart Contract Based Account
    • ERC721K zero dependencies for off-chain data
    • EIP2981 Royalty Standard
    • EIP5218 NFT Rights Management
    • EIP5606 Multiverse NFT
    • Versatile NFTs
    • EIP165 Standard Interface Detection
    • EIP1046 Metadata extension
    • EIP2309 Consecutive Transfer Extension
    • EIP-4521: 721/20-compatible transfer
    • ERC20 Token Standard
    • EIP3668 Durin Secure offchain data retrieval
    • ERC864 Divisible NFTs
    • ERC998 Composable NFT
    • ERC1633 Re Fungible NFT
    • ERC2477 Token Metadata Integrity
    • ERC2615 NFT with Mortgage and rental functions
  • NFT Standards on L2s
    • Bridging NFTs across layers
    • L2 NFTs
  • Non ETH NFT Standards
    • Ceramics
    • NEAR
    • RMRK
    • Cosmos
    • LUKSO
    • Tron
  • NFT Security
    • ERC-721 Security
    • EIP2612 Signed token approvals
    • Designing secure smart contracts
    • EIP712 Ethereum typed structured data hashing and signing
    • EIP3009 Transfer with Authorization
    • Multisign
    • Permits
    • Salmonella Contract
  • Frontrun bidding
  • Custom NFT platforms add ons
    • Foundation
    • Zora
    • ERC 721A Azuki
    • ERC223 Token Standard
    • Interactive NFTs & Standardising metadata
    • Lazy Minting OpenSea
    • Uniswap v3 NFT
    • OpenSea
  • Music NFTs
    • NFTs Music Overview
    • Music NFT Metadata
    • Music NFT Standards Considerations
Powered by GitBook
On this page
  • Simple explanantion
  • EIP Explanation
  • Implementation project
  • Further reading
  1. Standards

ERC725 Smart Contract Based Account

Standard for blockchain-based identity associated to ERC735

PreviousERC1155 Multi tokenNextERC721K zero dependencies for off-chain data

Last updated 1 month ago

Simple explanantion

Identity standard for publishing and managing an iddentity via smart contract on an EVM-based blockchain, the identity is represented by its chain address.

Relates to ERC735 which ERC725 supports. deals with management of claims made about ERC725 identity

EIP Explanation

Interface standard for a smart contract based account with attachable key value store

"Standardizing a minimal interface for a smart contract based account allows any interface to operate through these account types. Smart contact based accounts following this standard have the following advantages:

  • can hold any asset (native token, e.g. ERC20 like tokens)

  • can execute any smart contract and deploy smart contracts

  • have upgradeable security (through owner change, e.g. to a Gnosis safe)

  • are basic enough to work for a long time

  • are extensible through additional standardization of the key/value data.

  • can function as an owner/controller or proxy of other smart contracts"- EIP Author

Implementation: https://eips.ethereum.org/EIPS/eip-725

Implementation project

ERC725 implementation is used on Universal Profiles which is live on Test network,

Further reading

  • First impressions with ERC 725 and ERC 735 — identity and claims: https://hackernoon.com/first-impressions-with-erc-725-and-erc-735-identity-and-claims-4a87ff2509c9

  • ERC725 Alliance https://erc725alliance.org/

  • Projects implemented ERC725: https://github.com/ERC725Alliance/ERC725/blob/master/docs/use-cases.md

ERC735
Project link