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
  • Intro
  • NFT DID method
  • NFT DID Method Spec
  • NFT DID Functions - CIP-94
  • Further reading
  1. Non ETH NFT Standards

Ceramics

PreviousL2 NFTsNextNEAR

Last updated 1 month ago

Intro

Ceramics is building Decentralised Identity (DID) open-source solution which can be used across various blockchain solutions for creating, hosting and sharing streams of data https://ceramic.network/

Ceramics uses CIPs - Ceramic Improvement Proposals which are standards for the Ceramic platform, including core protocol specifications…

Why CIPs?

As every network, Ceramics wants to decentralise its power to the community. CIPs are step towards decentralisation of the platform and giving power to the hands of community.

NFT DID method

"NFT is a DID method that uses the Ceramic network to resolve DID documents for NFTs"

"A DID method for any NFT on any blockchain. The DID document is statically generated from on-chain data. The DID associated to the blockchain account of the asset's current owner (using CAIP-10 Links) is the only entity authorized to act on behalf of the NFT DID, authenticate in DID-based systems, and make updates to streams or other data owned by the NFT DID. When ownership of the NFT changes, so does the controller permissions" - author of intro article https://blog.ceramic.network/what-is-ceramic/

NFT DID Method Spec

"The NFT DID Method converts any non-fungible token on any blockchain into a decentralized identifier where the owner of the NFT is the controller of the DID. This is achieved by using the Chain Agnostic Improvement Proposals to describe NFT assets and blockchain accounts, as well as the Ceramic network to find the DID associated with the owner of the NFT."- CIP author

NFT DID Functions - CIP-94

Read / Verify

DID Document Metadata

  • create - populate using the blockchain timestamp from the block when the NFT was created

  • updated - populate using the blockchain timestamp from the block of the most recent owner change

ERC721 API does not provide any way to query this data, you may want to use The Graph protocol to create subgraphs for NFTs that are supported

The following metadata properties MAY be populated (if possible).

  • create - populate using the blockchain timestamp from the block when the NFT was created

  • updated - populate using the blockchain timestamp from the block when the given version owner became owner

  • versionId - integer, should equal the number of owners until the looked up version starts at 0

  • nextUpdate - populate using the blockchain timestamp from the block when the next owner became the owner

Update

Transfer the NFT to another account

Deactivate

Burn it

Further reading

  • Full implementation of CIP-94 : https://github.com/ceramicnetwork/CIP/blob/main/CIPs/CIP-94/CIP-94.md

  • NFT DID Resolver: https://github.com/ceramicnetwork/nft-did-resolver/blob/main/README.md

  • A project that is using NFT DID Resolver: https://github.com/nama-finance/meta-manager

  • Asset Reference for the ERC721 Asset Namespace - CAIP-22: https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-22.md

"Extract the Asset ID from the method specific identifier. From it you can learn which asset on which blockchain to look up the owner of the NFT. Once you have the owner account convert it to a by combining it with the Chain ID from the Asset ID. Using the Ceramic caip10-link doctype we can now look up the DID which this account points to."- CIP author

Learn more about CIPs
CAIP-10 Account ID