Learning Docs
Product DocsTechnical DocsLearning & GovernanceUseful Links
  • Learn about cheqd
  • Getting Started
    • ♟️What is cheqd?
    • ✋What is Creds?
  • Decentralised Identity
    • 🟢Start here
    • What are DIDs?
      • What is a DID?
      • What is a DID method?
      • What is a Verifiable Data Registry?
    • What are Verifiable Credentials?
      • What is a Verifiable Credential?
      • Types of Verifiable Credential
        • JSON (JWT)
        • JSON-LD
        • AnonCreds (ZKCreds)
        • SD-JWT
      • What is a Verifiable Presentation?
    • What are DID-Linked Resources?
  • $CHEQ
    • 🟢Start here
    • 📈Tokenomics
      • Tokenomics: Part 1
      • Tokenomics: Part 2
      • Tokenomics: Part 3
      • Tokenomics: Part 4
      • Circulating Supply Explained
      • Network Parameters
    • ✍️Identity writes
    • ♻️Credential Payments
      • Verifier pays Issuer
      • Holder pays Issuer
  • Governance
    • 🟢Start here
      • Introduction to Governance
      • Introduction to Entropy
      • Governance Principles
        • Foundational Principles
        • General Principles
    • 📚Learn
      • 🍎Core concepts
        • Staking
        • Slashing
        • Validating
        • Voting
        • Community Pool
      • ✏️Terminology
      • 📖Glossary
    • 🍍How to Participate
      • How to stake
      • How to vote
      • Making Network Changes
        • Minor Network Changes
        • Major Network Changes
    • ⚡Advanced
      • What is a Liquidity Pool?
        • How do liquidity pools work?
        • How to take part in a Liquidity Pool
      • CHEQ-ERC20 wrapped token
        • Why did we decide on a bridge to Ethereum?
        • What is the Gravity Bridge?
        • Why did we decide to use the Gravity Bridge?
        • What other bridging options did we explore?
        • How to send tokens to Ethereum with Gravity Bridge
        • How to add CHEQ tokens to UniSwap Liquidity Pools
        • How to send CHEQ tokens from Ethereum to cheqd
  • ⚖️ Legal
    • License
    • Code of Conduct
    • Security Policy
    • Legal Disclaimer
  • 🆘Support
    • System Status
    • Slack Channel
    • Discord
Powered by GitBook
LogoLogo

General

  • Website
  • Blog
  • Get $CHEQ

Product Docs

  • Product Docs
  • cheqd Studio
  • Creds.xyz

Technical Docs

  • Node Docs
  • GitHub
  • Block Explorer

Learning Docs

  • Learning Docs
  • Governance Docs
  • Governance Forum
  • Governance Explorer
On this page
  • Types of Verifiable Data Registries
  • Blockchain
  • Web domain
  • Sidetree
  • KERI
  • Further reading

Was this helpful?

Edit on GitHub
Export as PDF
  1. Decentralised Identity
  2. What are DIDs?

What is a Verifiable Data Registry?

Last updated 1 year ago

Was this helpful?

A Verifiable Data Registry ("VDR"), in the context of decentralised identity, is a place where Decentralised Identifiers (DIDs) can be anchored to.

Types of Verifiable Data Registries

Blockchain

Commonly, VDRs are blockchains, like cheqd. This is because they are great places to store data immutably.

Web domain

However, a VDR could also be a web domain, like . We could store a public DID on this website, because only the admins of cheqd have the ability to edit this.

This is largely secure, but is not as resilient as a blockchain, because, for example, the hosting provider for the website could take it down.

Sidetree

New innovations in decentralised identity have tried to create a more flexible storage layer for DIDs. Sidetree is a technology which stores DIDs and DID Documents in a temporary Layer 2 storage layer called Sidetree. This data is stored in IPFS, batched and anchored to blockchains in rollups. This minimises the amount of transactions necessary to be made to the Layer 1 blockchain.

Hypothetically, by storing DIDs in a temporary storage Layer 2, with backups in IPFS, the DID could also be updated from being stored on one VDR to another VDR. This is currently the exploratory work of did methods such as did:orb.

KERI

KERI, meaning Key Event Rotation Infrastructure, is another emerging innovation in decentralised identity. Rather than anchoring a DID to a specific location or block within a chain, KERI relies on nodes witnessing Key Event Logs (KELs). A KEL may hold an authoritative source of truth about what the latest keys related to a DID are, and who holds them.

In simple terms, KERI's logs are not immutable like a blockchain, but rely on the law of large numbers, and trust that KERI witnesses will act in a trustworthy fashion - providing the most up to date KELs with the correct Key events.

Further reading

http://cheqd.io

DID Core Spec

Dive into the W3C DID Core Recommendation to fully grasp the power of DIDs.

DID Resolution Spec

Learn about how DIDs can be resolved or dereferenced from the W3C DID Resolution Spec.

DID Spec Registries

Explore the different DID methods registered within the DID Spec Registries.

cheqd DID Method

Learn specifically about cheqd's DID Method and how it works on the cheqd Network.