[Support for issuing and verifying anoncreds using different blockchain providers ]

[AlexAndrei98]

Support AnonCreds Interfaces to issue and verify credentials

• The issuance flow has 13 interactions between holders and issuer
• The presentation flow has 9 interactions
• The revocation flow describes the step that need to happen to a revocable credential.

Define AnonCreds Objects that need to be on the ledger

The objects required to exists for an AnonCred are the following:

• Schema
• Credential Definition
• Credential Revocation List
• Credential Revocation Entry
  Maybe the did-provider can be in charge of doing the actual writing of these objects?

AnonCreds have a specific flow on when events happen that are blockchain agnostic data-flows

• The issuance flow is slightly different from LD credentials, since you need to create a credential definition and a revocation registry with tails file
• The verification flow is also different from either WACI or OIDC4VP

Notes and some useful links
AnonCreds currently uses CL Signatures for doing selective disclosure so that might be required to do beforehand.
We can do a first implementation without the revocation ability as it might simplify things!
AFJ Interfaces Implementation
Specification
Indy blockchain implementation
Cardano implementation to write objects to the ledger in TS
Cheqd implementation in Aries framework JavaScript
Project status