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

How do new claims and their signatures get generated from a collection of existing VCs #119

Closed
r-soltani opened this issue Feb 20, 2018 · 0 comments
Assignees

Comments

@r-soltani
Copy link

My understanding of verifiable claim (or more specifically verifiable credentials) is that it is made of many components including a 'Proof' attribute that describes the signature of the claims.

When an identity holder is required to share one or a number of the claims that are in his possession with a Verifier, how does the signature attaches to the new verifiable claim (or I guess the correct term is verifiable profile) is calculated on the spot? Does this new signature require the original key material of the issuer?

Is the VC standard assuming the use of approaches such as Idemix to generate the new signature for the verifiable claims passed from owner to verifier?

@r-soltani r-soltani changed the title How are verifiable claims (ex. proof of age) maintain a signature How do verifiable claims (ex. proof of age) maintain authenticity Feb 20, 2018
@r-soltani r-soltani changed the title How do verifiable claims (ex. proof of age) maintain authenticity How do new verifiable claims generated from a collection of VCs maintain their authenticity Feb 20, 2018
@r-soltani r-soltani changed the title How do new verifiable claims generated from a collection of VCs maintain their authenticity How do new claims and their signatures get generated from a collection of existing VCs Feb 20, 2018
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

No branches or pull requests

2 participants