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

Add support for 0453: Issue Credential v2 #352

Closed
TimoGlastra opened this issue Jul 3, 2021 · 6 comments
Closed

Add support for 0453: Issue Credential v2 #352

TimoGlastra opened this issue Jul 3, 2021 · 6 comments
Assignees
Labels
AIP 2.0 Tasks related to AIP 2.0 support Protocol Tasks related to an Aries Protocol Type: Enhancement
Milestone

Comments

@TimoGlastra
Copy link
Contributor

https://github.com/hyperledger/aries-rfcs/tree/b3a3942ef052039e73cd23d847f42947f8287da2/features/0453-issue-credential-v2

@TimoGlastra TimoGlastra added Type: Enhancement Protocol Tasks related to an Aries Protocol AIP 2.0 Tasks related to AIP 2.0 support labels Jul 3, 2021
@jakubkoci
Copy link
Contributor

Is there any difference between the link to a particular hash and the link to main branch like this https://github.com/hyperledger/aries-rfcs/blob/main/features/0453-issue-credential-v2/README.md?

@TimoGlastra
Copy link
Contributor Author

See my comment in the present proof issue

@NB-MikeRichardson
Copy link
Contributor

I have started the development of this RFC.

@NB-MikeRichardson
Copy link
Contributor

Can someone assign this to me?

@TimoGlastra
Copy link
Contributor Author

You got it!

@NB-MikeRichardson
Copy link
Contributor

NB-MikeRichardson commented Nov 29, 2021 via email

@TimoGlastra TimoGlastra added this to the 0.2.0 milestone Mar 1, 2022
@TimoGlastra TimoGlastra linked a pull request May 4, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AIP 2.0 Tasks related to AIP 2.0 support Protocol Tasks related to an Aries Protocol Type: Enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants