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 issues do DID-Linked Resources solve?
  • Centralisation
  • Link Rot and Longevity
  • Semantic Linkage
  • Use cases for DID-Linked Resources
  • New use cases enabled by DID-linked Resources

Was this helpful?

Edit on GitHub
Export as PDF
  1. Decentralised Identity

What are DID-Linked Resources?

Learn about digital resources written on cheqd

Last updated 7 months ago

Was this helpful?

cheqd has built a Resources Module to extend the functionality of our decentralised identity network, providing capabilities not found on other self-sovereign identity networks.

A DID-Linked Resource is a blob of information stored on-ledger, discoverable through the same syntax that is widely used within the SSI industry.

What issues do DID-Linked Resources solve?

Centralisation

Many SSI resources such as schemas currently reference web URLs such as . Other areas where this can be issues are:

  • DID methods, such as and , where trust is based on Web 2.0 infrastructure

  • Revocation lists maintained on servers, such as

If, for example, any of the infrastructure listed above was to experience downtime due to technical faults, a dDoS attack or a failure of a cloud hosting provider, this could hugely disrupt the proper use of Verifiable Credentials in a production environment.

Link Rot and Longevity

Such web URLs as described above are also single-points of failure due to .

Credential schemas, once defined, should be able to be used and referenced for many years, without being changed. For this reason, keeping an up-to-date version of the links themselves is crucial. Moreover, if the schema locations are moved and the links are broken, the Credentials issued become far less trustworthy.

Semantic Linkage

The way schemas are currently referenced from web URLs (e.g., schema.org/Person) is not immutable. Schemas may be changed and previous schema definitions may be purged from the database. This means if you had a Verifiable Credential issued in 2015 which referred to a particular schema in 2022, that schema definition may have significantly changed.

On the other hand, solutions that do currently store schemas on ledger (e.g., Hyperledger Indy) don't have semantic linkage between old and new versions. In this instance, current ledgers allow new versions to be made but don't offer an easy way for client apps to discover linkages as they evolve over time.

Use cases for DID-Linked Resources

The use of Resources is potentially very broad; they can provide many different roles, such as:

  • A schema, such as Camenisch-Lysyanskaya ("CL") schema ‘CL’, JSON-LD schema, JSON schema etc.

  • A document, such as a Governance Framework

  • An branding elements, such as a company logo, brandmark, etc which can be pulled directly by block explorers and other Web3 applications

  • A revocation registry for revoking already-issued credentials.

Through extending the use of DIDs to identify other on-ledger resources, trust can begin to be chained.

New use cases enabled by DID-linked Resources

Audience
Quick wins
Longer term strategic objectives

SSI Community

Web 3.0 community

Enable Web3 Companies to use on-ledger Resources to fetch company information (such as logos, token info, relevant token APIs) to populate Block Explorers and Exchanges, rather than through Keybase or manual processes.

You can think of it as a hyperlink for #Web3. But unlike a hyperlink, it is possible to specify the type of resource to be retrieved, and reject anything unexpected.

A visual representation, such as , , , etc

Create a much more secure, resilient and decentralised format for storing schemas than

Lay the technical foundations for supporting compatible Verifiable Credentials on cheqd, in addition to support for JSON and JSON-LD

Extend the , enabling DIDs to act as #Web3 hyperlinks for any on (or off) ledger URL, Resource, file, or content

Decentralized Identifier (DIDs)
Schema.org
did:web
did:github
Status List 2021
link rot
Overlays Capture Architecture (OCA)
Apple Wallet PassKit
Google Wallet Passes
schema.org
AnonCreds
Trust over IP Resource Parameter Specification