Skip to content
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

Implement issuing a verifiable presentation #59

Closed
sgreenbury opened this issue Jan 23, 2023 · 2 comments · Fixed by #116
Closed

Implement issuing a verifiable presentation #59

sgreenbury opened this issue Jan 23, 2023 · 2 comments · Fixed by #116

Comments

@sgreenbury
Copy link
Collaborator

Include functionality for transforming from a VC to a VP. This process relates to the W3C VC API. See work in didkit for reference.

@sgreenbury
Copy link
Collaborator Author

@edchapman88
Copy link
Collaborator

Updates:

  • Changes to Issuer.sign() and Holder.sign_presentation() to include Option<LinkedDataProofOptions> in the api.
    • For Issuer.sign(): if None, the default is used (which sets ProofPurpose::AssertionMethod).
    • For Holder.sign_presentation(): if None, ProofPurpose::Authentication is set along with the other fields from Default::default().
  • Change to sign_presentation() to ensure the holder field is set on presentations before they are signed.
  • Presentation.generate_proof() attempts to resolve a DID provided in the holder field of the presentation.
    • This has implications for supporting the partial verification of presentations in the cases where the holder DID is either non-resolvable or non-verifiable.
    • It is not currently possible to sign presentations with non-resolvable DIDs

@edchapman88 edchapman88 linked a pull request Sep 4, 2023 that will close this issue
edchapman88 added a commit that referenced this issue Sep 6, 2023
Verifiable presentation API for ION attestor #59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants