-
Notifications
You must be signed in to change notification settings - Fork 8
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
Identity - Proofs of Identity and Verifiable Claims #11
Comments
An identity, represented by its DID, should be able to prove its authenticity. To do so, the identity might disclose a set of claims that can then be verified by the interested party, usually called "inspector". The way those claims and proofs are modelled should be standardized so that many peer dApps could build upon it. More specifically, having a standard model will make it easier to build the UI/UX necessary for users to trust others. There's a working group that is working on this, called "Verifiable Claims": https://www.w3.org/2017/vc/WG/. We should analyze it and consider adopting it as part of our foundations for building dApps. |
To get a better feel for what VCs look like, you can check the VC playground: https://w3c-vc.github.io/playground/ |
We should also look at JSON Web Tokens, it's what uPort is using: https://jwt.io |
This issue tracks the proofs-of-personhood discussion, related to #9
The text was updated successfully, but these errors were encountered: