Metadium Tech (ENG)
  • Navigation
    • Metadium Overview
    • Metadium Tech (ENG)
    • Metadium Tech (KOR)
  • METADIUM Info
    • Architecture
    • Network Structure
    • Consensus
    • Smart Contract
    • DID
    • EIP-1559
    • Fee Delegation
    • Roadmap
  • Developer
    • Node Start
      • gmet Binary
      • gmet Guide
      • Connect Node
      • Account
    • Install Node
      • End Node
        • Requirements
        • Install Gmet
      • BP Node
        • Requirements
        • Install Gmet
  • Smart Contract
    • Solidity
    • Precompiled Contracts
    • Sample Contracts
  • API Reference
    • API Info
    • Json-RPC
    • Explorer API
      • Accounts
      • Blocks
      • Contracts
      • Transactions
      • Event logs
      • Tokens
  • Wallet
    • Wallet Info
    • Fee
  • FAQ
  • Articles of Foundation
Powered by GitBook
On this page
  • Metadium DID structure
  • Metadium DID Process
  1. METADIUM Info

DID

PreviousSmart ContractNextEIP-1559

Last updated 1 year ago

Metadium DID structure

: DID is a crucial element in managing digital identities for individuals or organizations, facilitating CRUD operations based on DID and DID documents. Users or institutions can create a DID, read its associated information, and update or delete it as needed. These CRUD operations effectively manage digital identity.

Metadium DID Process

: The use of DID for signing contracts and other transactions is executed and recorded on the blockchain through smart contracts, ensuring data integrity and prevention of tampering. Moreover, utilizing only simple DID without including personal information guarantees privacy protection and anonymity, thus preventing the leakage of personal data.

Users create private keys and public keys using the DID App and create DIDs by sending the public key and signature to the smart contract on the blockchain.

After issuing a DID, if you receive proof from the issuer that you are eligible for the user, you will receive a certificate signed with the issuer's private key.

​When using the service, the user sends the certificate to the Verifier, and the Verifier returns that the certificate has been signed by the Issuer utilizing the user’s public key and the Issuer’s registered in the blockchain.

When requesting deletion, the user sends their DID and signature, and the DID smart contract deletes the DID after confirming the user's signature and returns the result.

DID Structure
Create & Read DID
VC Issuance
VC Verification
Delete DID