-
Notifications
You must be signed in to change notification settings - Fork 26
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
Feat/bifold #79
Feat/bifold #79
Conversation
Signed-off-by: Mirko Mollik <mirko.mollik@fit.fraunhofer.de>
Signed-off-by: Mirko Mollik <mirko.mollik@fit.fraunhofer.de>
Signed-off-by: Mirko Mollik <mirko.mollik@fit.fraunhofer.de>
Signed-off-by: Mirko Mollik <mirko.mollik@fit.fraunhofer.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should add "credentialFormats": ["AnonCred", "SD-JWT-VC"]
.
Thanks you so much for adding this!
@@ -0,0 +1,13 @@ | |||
{ | |||
"capability": ["holder"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The verifier
capability is in preview, but it does exists
Is bifold also supporting other signature algorithms or key managements like |
In one of the calls we said that we will not add white label wallets that are not published as a final solution. However we will add a new column that will allow wallets to point to special requirements like important libraries projects. So speaking of bifold, the BC Wallet would reference the project as one of the dependencies. |
Signed-off-by: Mirko Mollik mirko.mollik@fit.fraunhofer.de