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
  • Architecture
  • Core
  1. Protocol

Resolver

PreviousOpenAPI For DfinityNextKYC

Last updated 2 years ago

Resolver records the DID user personal information (eg: name, avatar, blockchain address). DID user can display the personal information by resolver contract. all of the information is optional.

Architecture

Core

The tokenId is used as the core to bind all information together. TokenId and DID are one-to-one mappings relationship in the DID contract. DID is essentially a non-transferable NFT. Setting DID resolver information is equivalent to setting additional metadata for NFTS.