-
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
Introduce VC spec #3
base: master
Are you sure you want to change the base?
Conversation
87d1a02
to
29c5e29
Compare
Deploying ensips with Cloudflare Pages
|
05f1d5a
to
f9bb90e
Compare
9e3e84b
to
dae0ddd
Compare
"type": ["VerifiableCredential"], | ||
"issuanceDate": "2024-05-21T00:00:00Z", | ||
"credentialSubject": { | ||
"id": "did:ens:luc.eth", // the subject's ens name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it might be useful to add the address here as well, as the ens owner can change and render the credential invalid. so it might look something like that:
"did:ens:luc.eth#0x225f137127d9067788314bc7fcc1f36746a3c3B5"
|
||
Note the requirement for `id` to be `did:ens:luc.eth` in order to prevent credential spoofing. | ||
|
||
```json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wouldn't the issuer and Proof be needed here as well?
We also worked on a fix for the ens did resolver library and are currently using it at JustaName. We will open a PR with the fix, and potentially publish the lib if needed...
Introduces the verifiable Credential Specification.
This specification allows for W3C Verifiable Credentials to be stored inside ENS profiles
PS; This PR is also used for testing the ensip flow