HashKey DID
  • Introduction
  • FAQ
  • Terminology
  • Developers
    • Guides
      • Register
      • Query
      • Libraries
      • Credential API Rule
    • API Reference
      • OpenAPI
      • OpenAPI For Dfinity
  • Protocol
    • Resolver
    • KYC
    • Multi-Chain
    • Credential
    • DID as NFT
    • Deployment
    • Contract API Reference
      • Registry
      • BasicInfo
      • PublicResolver
      • KYC
      • LayerZero
      • Credential
  • How to
    • Become an issuer
    • Edit issuer info
    • Issue a credential
      • Step 1: Deploy a contract
      • Step 2: Create a credential and submit
        • Claim rules
      • Step 3: Issue a credential
    • Manage your credentials
  • Support
    • Brand Kit
Powered by GitBook
On this page
  • Metadata
  • Display
  1. Protocol

DID as NFT

PreviousCredentialNextDeployment

Last updated 2 years ago

HashKey DID contract is based on , meaning that .key registrations have their own metadata in their tokenURIs including name, description, image, etc. But the DID can not be transferred so far.

Metadata

Metadata is a json string which includes the basic data of an NFT.

The metadata can be found by curl https://api.hashkey.id/did/api/nft/metadata/{tokenId}.

{
  "name": "chingizyanik.key",
  "description": "Your Passport in the Metaverse",
  "image": "https://api.hashkey.id/did/api/file/avatar_117e6412-ba3f-4acd-a5a3-b171e5acfb17.png",
  "ipfs_url": "https://arweave.net/ySMzJkoSdbM9jWsmm4W6Glsk1HapTluMVG1oyi5QpaA"
}

Display

HashKey DID's main contracts is deployed on , so the DID NFT can be found on the HashKey DID DAPP and platforms that support PlatON such as .

ERC721
PlatON
tofu