VC verify should accept a VP without `verifiableCredential` property
See original GitHub issueThe verifiableCredential
property is not required (https://www.w3.org/TR/vc-data-model/#presentations-0).
https://github.com/digitalbazaar/vc-js/blob/master/lib/vc.js#L399
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Verifiable Credentials Data Model v1.1 - W3C
A verifier can verify verifiable presentations from any holder, containing proofs of claims from any issuer. Verification should not depend ...
Read more >Verifiable Credentials – how does it work? Understanding key ...
VC metadata describes properties such as type, expiration and issuer of a credential. VC proof is used to verify the integrity of a...
Read more >vc-api/verification.md at main · w3c-ccg/vc-api - GitHub
This attempts a general description of the process whereby a relying party checks whether they will accept Verifiable Credential or Verifiable Presentation. An ......
Read more >Decentralized Identity: Verifiable Credentials Deep Dive
The subject property isn't needed in a VP, because the issuer is asserting a thing about itself, in other words a JWT-VC is...
Read more >19 FAQs on Verifiable Credentials and Self-Sovereign Identity
Verifiable credentials, or VCs in short, are tamper-evident credentials that can be verified cryptographically. There are three essential components of ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Reuse of this lib. There’s no reason to have to keep reimplementing code that creates VPs in every lib when this lib will do just fine.
@dlongley What’s the argument for being able to create a VP without a
verifiableCredential
, in this lib? (I can sort of understand the argument for verify() being able to do it, for future compatibility with ZKPs etc.) But why create?