⚡AnonCreds Object Method

cheqd AnonCreds Object Method Specification.

cheqd AnonCreds Object Method

cheqd intends to directly support AnonCreds using its DID-Linked Resource module in an AnonCreds Object Method. With its resource module, cheqd will identify each on-ledger resource with a DID Core compliant DID URL. This DID URL will be able to be dereferenced in order to fetch the resource and associated metadata.

Get started

Schemas

Create Schemas using DID-Linked Resources to support AnonCreds on cheqd.

Credential Definitions

Create CredDefs using DID-Linked Resources to support AnonCreds on cheqd.

Revocation Registry Definitions

Create Revocation Registry Definitions using DID-Linked Resources to support AnonCreds on cheqd.

Revocation Status Lists

Create Revocation Status Lists using DID-Linked Resources to support AnonCreds on cheqd.

Get started with AnonCreds

cheqd fully supports AnonCreds in multiple SDKs, including issuance, verification and revocation. See our documentation below to get started.

Credo

Credo is an SDK which supports the European Architecture and Reference Framework (ARF) standards as well as AnonCreds with full cheqd support for DIDs.

ACA-Py

ACA-Py (Aries Cloud Agent Python) is an SDK that can issue AnonCreds, JSON-LD and SD-JWT credentials with full cheqd support.

Partner SaaS products

You can use SaaS products from our partners to issue AnonCreds as well, with cheqd DID support under the hood!

Paradym

Paradym by Animo Solutions fully supports EU Architecture & Reference Framework standards with cheqd under the hood.

Hovi

Hovi provides an all-in-one platform for issuing and managing Verifiable Credentials with cheqd DIDs supported.

Why is AnonCreds support important?

While AnonCreds are only one flavour of Verifiable Credentials, they are currently in a functional state and are heavily used by cheqd's partners. Other Credential types, such as JSON-LD with BBS+ signatures, can provide a lot of equivalent functionality, but are currently not production ready.

Therefore, it is important for cheqd to provide support for AnonCreds in order to enable partners with existing clients using AnonCreds to use cheqd and existing Indy ledgers concurrently, within existing applications.

What does AnonCreds support look like?

Our aim is to support the functionality enabled by identity-domain transactions in by Hyperledger Indy into cheqd-node. This will reach the goal of allowing use cases of existing SSI networks on Hyperledger Indy to be supported by the cheqd network.

Importantly, we want to make sure that this work is done in a manner which brings AnonCreds closer to W3C compliance and wide-scale interoperability.