Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Register JwtProof2020 or warn users not to use this library
See original GitHub issueRegister it here:
its 2021, where is the full IRI for JwtProof2020 ?
https://w3id.org/did/v1 does not define JwtProof2020…
https://www.w3.org/ns/did/v1 does not define ANY proof formats (only verification methods)…
You should review https://w3c.github.io/vc-data-model/#dfn-context
and define a context which you control, where you can define all your terms for your users… see:
https://w3c.github.io/did-spec-registries/#schnorrsecp256k1verificationkey2019 https://w3c.github.io/did-spec-registries/#gpgverificationkey2020
Feel free to register your extensions in did spec registries as well.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
awesome looks like #56 is headed in the correct direction.
🎉 This issue has been resolved in version 1.1.0 🎉
The release is available on:
Your semantic-release bot 📦🚀