AnonCreds on cheqd


For a full breakdown of how AnonCreds is being supported on cheqd, including relevant timelines for full completion, see the following link:

cheqd AnonCreds Object Method

cheqd intends to directly support AnonCreds using its on-ledger 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.

Why is AnonCreds support important?

Whilst 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.


There are multiple specific AnonCreds transaction types that cheqd needs to support. This documentation will provide guidance and instructions on how equivalent AnonCreds formats can be replicated using cheqd DID-Linked resources, for:
Through creating compatible formats for the above, cheqd will theoretically be able to support AnonCreds request/response/issuance data flows, via existing SDKs and Hyperledger Aries Libraries.