Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define and implement the objects exchange by the issuer and holder during credential issuance #6

Open
swcurran opened this issue Nov 12, 2023 · 0 comments
Labels
AnonCreds v2 To Do Needed as part of AnonCreds v2

Comments

@swcurran
Copy link
Member

In AnonCreds v1, there are credential-offer and a credential-request objects that must be exchanged in order to issue a credential.

Define the purpose of the objects and the objects themselves, including any correctness proofs that must be included in the message. At minimum, the process must define how the holder can provide a blinded link secret to bind the credential to the holder. Based on the credential schema types, there may be additional information to flow between the issuer and holder.

@swcurran swcurran added the AnonCreds v2 To Do Needed as part of AnonCreds v2 label Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AnonCreds v2 To Do Needed as part of AnonCreds v2
Projects
None yet
Development

No branches or pull requests

1 participant