-
Notifications
You must be signed in to change notification settings - Fork 9
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 for W3C ed25519-2020 verification key #113
Comments
This would be nuts (in a good way)! +1 |
Do you need it for DID documents, Verifiable Credentials or both? If you need it for DID documents, it should be relatively easy to add support for it. For Verifiable Credentials, I don't think there's anything in this library that prevents you from using it, as it doesn't create or verify signatures. We're in the process of redesigning the Verifiable Credential part of this library to support upcoming new credential formats (e.g. SD-JWT) with more flexibility. Part of that exercise will also be introducing a separate library for Verifiable Credential handling (probably will be named something like |
@reinkrul, thanks for redirecting me to this issue! |
I've added the support for did in this PR #114 , but it looks like that the method is now deprecated as per https://www.w3.org/TR/vc-di-eddsa/#ed25519verificationkey2020 |
Note that this specification is still a draft, but chances are good the multikey requirement won't change. I think we'd welcome Multikey support, if it doesn't add too many/large dependencies. |
Since it's derived from multibase, which has been along for quite some time, it's probably relative stable. Only side note I could find is that the IETFis going to standardise it. We won't deny any PR's for it, that's for sure. |
thank you for the inputs, I'll raise a PR for Multikey support then. |
ed25519 (2020) VMs are now supported in 0.14.0 |
Hello, I wonder if there will be support for the W3C ed25519-2020 verification keys as shown here soon if planned at all? What is the current state of planning for this support?
W3C ed25519-2020 verification key specification: https://www.w3.org/community/reports/credentials/CG-FINAL-di-eddsa-2020-20220724/#dfn-ed25519verificationkey2020
The text was updated successfully, but these errors were encountered: