-
Notifications
You must be signed in to change notification settings - Fork 134
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
Support the new JWT-VC 2.0 format #1132
Comments
Yes, we do plan to adopt the new spec as well. The work will be mostly in did-jwt-vc, but we'll also have to make sure that everything works here too |
Hi, curious if there's any updates on this front. Or curious how vermao plans to implement JWT2 support. Will there be a config option to use v1.1 or v2 or will the library switch to support only v2? Any estimated timeframes or other dependencies that you are waiting on? Thanks |
Yes, we will be adding support for v2. It's still too early to talk about that support now or how that would look like in practice. |
What is the state with this? |
wow, it's been a while. If you'd like to raise a PR with an implementation, please say so :) |
There's a newly released native JWT VC representation spec, Version 2, here:
https://w3c.github.io/vc-jwt/#version-2
Some context available in this post here:
https://self-issued.info/?p=2316
Any plans to support this in the @veramo/credential-w3c ? Or is this a question better asked in the underly package, did-jwt-vc?
The text was updated successfully, but these errors were encountered: