cheqd StudioSupport / Bug Reports
Edit

JSON-LD

Issue and present JSON-LD credentials signed by cheqd Decentralized Identifiers (DIDs), using Credo.

JSON-LD Verifiable Credentials follow the W3C Verifiable Credentials Data Model, enabling decentralized, semantically rich, and interoperable credential exchange.

In Credo, you can issue, verify, and present JSON-LD credentials over DIDComm v2, using the Issue Credential v2 and Present Proof v2 protocols—alongside support for Linked Data Proofs and various signature suites.

Get Started

Issue and present JSON-LD credentials with Credo using the tutorials below:

Issue JSON-LD Credentials

Issue JSON-LD Credentials signed by cheqd DIDs using Credo.

Present JSON-LD Credentials

Present JSON-LD Credentials using Credo.

Why Use JSON-LD?

JSON-LD credentials are ideal for ecosystems that require:

  • Standards-aligned, interoperable credentials

  • Richly structured, linked data

  • Flexible signature types (e.g. Ed25519, BBS+)

  • Integration with W3C-conformant wallets and identity providers

  • Compatibility with OpenID for Verifiable Credentials (OID4VC) and EU Digital Identity Wallet initiatives

Extensibility for cheqd Functionality

Thanks to the flexibility of the W3C VC data model, JSON-LD credentials can be extended to support advanced cheqd-native features, including:

🔗 DID-Linked Resources

  • Credentials can reference schemas, governance frameworks, or legal documents published as DID-Linked Resources on the cheqd ledger

  • Use the termsOfUse or credentialSchema fields to point to cheqd-hosted resources

🏛️ Trust Registries

  • A credential can reference a trust registry (also a DID-Linked Resource) that defines the rules, requirements, or authorisations under which the credential was issued

🚫 Status Lists (Revocation)

  • cheqd-compatible Bistring Status List entries can be referenced using the credentialStatus field, enabling scalable and private revocation

  • These status lists can also be stored as DID-Linked Resources on cheqd

🔧 These extensions follow W3C patterns and require no change to the base data model—making them portable, verifiable, and standards-compliant.

Features Supported in Credo

Feature
Supported in ACA-Py

Issue JSON-LD credentials

✅ Yes

Present and verify JSON-LD credentials

✅ Yes

Support for multiple proof types

✅ Yes (Ed25519Signature2018, Ed25519Signature2020, etc.)

Use of external or on-chain contexts

✅ Yes

Support for DID-Linked Resources

⚠️ Via extensions and custom fields

Supported DID Methods

Credo natively supports signing JSON-LD credentials using DIDs such as:

  • did:key

  • did:web

  • did:cheqd

Last updated

Was this helpful?