Disco Docs
DiscoDashboardGithubDiscordIRLCampaigns
  • Welcome
    • βšͺWelcome to Disco
      • πŸŽ’Data Backpacks
      • 🧱About DIDs and VCs
      • ♻️Lifecycle of Credentials
    • ⚑️ Quickstart Guide
  • Getting Started
    • πŸ–ŒοΈCustomize Credential Branding
    • πŸ”‘Generate an API Key
    • πŸ“ŠDashboard
    • ⛓️Onchain Data
    • πŸ“ Select a Credential Schema
    • πŸš€Build & Issue Credentials
    • πŸ“–Credential Data Model
    • βš™οΈDisco APIs
      • Programmatically Issue a Credential
      • Retrieve a Credential
      • Verify a Credential
      • Personas
    • βš™οΈDisco SDK: Selective Disclosure
      • Implementation
  • Learn more
    • πŸ‘‹Data Backpacks for Holders
      • ♻️The 3-Sided Marketplace of Verifiable Data
      • πŸŽ’Create a Data Backpack
      • πŸ“§Send a Credential to Another Person
      • βš™οΈLinked Accounts
        • X (Twitter) Account
        • Lens, ENS or .box Domains and Data Backpacks (coming soon)
    • πŸ“‘DIDs and VCs Explained
    • πŸ”“Wallets
    • ❓FAQs
    • πŸ“’Glossary
      • Detailed Glossary
  • Demos
    • πŸ’…Chipped Nails by Kiki.World x Gossip Protocol
    • πŸ’§Programmatic Issuance: Campaigns
Powered by GitBook
On this page
  • Let's take a look at an example.
  • Parties Involved πŸ₯‚
  • πŸ›οΈ Issuer
  • πŸŽ’ Recipient
  • 🏫 Verifier
  1. Learn more
  2. Data Backpacks for Holders

The 3-Sided Marketplace of Verifiable Data

Issuer > Holder > Verifier

PreviousData Backpacks for HoldersNextCreate a Data Backpack

Last updated 1 year ago

Let's take a look at an example.

Degen University is the and issues a diploma in the form of a Verifiable Credential (VC) to Alex as the for their graduation on a specific date. They use Disco to accept the credential and apply for a job. The employer, acting as a , who will verify the credential via Disco's API endpoints.

In this scenario, the inherent trust model comes into play in three ways:

  1. Alex can prove who issued the credential, as Degen University's DID is unique to them.

  2. Alex owns the credential and is the subject of the claim (i.e. their Degree in Arts).

  3. The credential is valid, and the cryptography has not been tampered with.

Parties Involved πŸ₯‚

πŸ›οΈ Issuer

Whoever is issuing a claim, or credential. This could be any governing body, entity, university, or organization! They’ll sign the claim with their public and private key-pairs so it’s legit.

πŸŽ’ Recipient

Whoever is receiving a claim, or credential. They will ultimately own these credentials and control how it’s shared. They’ll have a DID so it’ll be unique to that address only.

🏫 Verifier

An entity that verifies if the credential is authentic and valid. Typically, they’ll ensure that it is legitimate, tamper-proof, and is still relevant on the requested date.

πŸ‘‹
♻️
Issuer
Recipient
Verifier