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
  • What is Selective Disclosure?
  • The Significance of Selective Disclosure
  • SD-JWTs: A Mechanism for Selective Disclosure
  • How it Operates

Was this helpful?

Edit on GitHub
Export as PDF
  1. Decentralised Identity
  2. What are Verifiable Credentials?
  3. Types of Verifiable Credential

SD-JWT

Last updated 1 year ago

Was this helpful?

Much of the work in this page is influenced, iterated or directly replicated from our .

What is Selective Disclosure?

Selective disclosure empowers an individual to decide which specific pieces of information, contained within a Verifiable Credential, will be disclosed to a verifier. This stands in contrast to the conventional practice of revealing all the data present in a Verifiable Credential.

For instance, Alice could selectively share only her age to confirm eligibility for purchasing products on an e-commerce platform, without divulging other personal details found in her Verifiable ID document used for verification. This approach enhances privacy and provides individuals with greater control over their personal data.

The Significance of Selective Disclosure

Selective disclosure is a crucial element of Self-Sovereign Identity (SSI) because it allows individuals to share only the essential personal information required for a transaction or interaction. This minimizes the risk of identity theft and various forms of fraud.

SD-JWTs: A Mechanism for Selective Disclosure

A Selective Disclosure JSON Web Token (SD-JWT) is a subtype of JSON Web Token wherein the claims within the body are hashed, rendering them unreadable without proper disclosure. The original values of the claims can be unveiled by providing the necessary disclosures.

How it Operates

When presenting a conventional credential via JWT, the claims are plainly visible to the verifier. In contrast, with an SD-JWT credential, claims are encrypted in a hashed format, ensuring their unreadability. The holder can then choose which claims to reveal to the verifier by providing plain text key-value pairs (referred to as disclosures) alongside the SD-JWT. The verifier can hash these disclosures and compare them to the values in the SD-JWT, thereby verifying the inclusion of the claim in the SD-JWT. Additionally, SD-JWTs allow for the inclusion of decoy hashes in the credential, serving as dummy values to obfuscate the actual number of claims in the credential.

partner Walt.id's docs on SD-JWT