Skip to content

Commit

Permalink
Bump
Browse files Browse the repository at this point in the history
  • Loading branch information
lucemans committed May 24, 2024
1 parent 82f0846 commit 560252d
Showing 1 changed file with 13 additions and 9 deletions.
22 changes: 13 additions & 9 deletions docs/ensip/draft-vc.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ export const meta = {
}
};

# ENSIP-XX: Verifiable Credentials / Presentations
# ENSIP-XX: Verifiable Credentials & Presentations

### Abstract

Expand All @@ -22,18 +22,18 @@ With the increasing prevalence of self-custodial digital identity & attestation

### Specification

#### Verifications in Profiles

Defines the use of the `verifications` record.
This record aims to store a list of verifiable credentials or did's, pointing towards certain credentials

#### Draft
#### Very Rough Draft

did/url links to vc
vc contains **metadata** **claims** & **proof**
implementations choose what "proof"s they support (aka, what credentials they accept/trust)
claims are the actual data thats being attested

#### Verifications in Profiles

Defines the use of the `verifications` record.
This record aims to store a list of verifiable credentials or did's, pointing towards certain credentials

#### Example

An example of a verifiable credential
Expand Down Expand Up @@ -101,8 +101,12 @@ f

Verifiable Credentials are meant to be used as long-lived documents.
However this does not mean that they can't be revoked or expired.
In a similar manner to physical documents, a credentials validity can be checked by contacting the issuer.
The implementation of verification is specific to each issuer, however can be inferred from `verificationMethod` in the credential.
In a similar manner to physical documents, a credentials validity can be checked by contacting the issuer (Think of how a store might only look at your drivers license, while a car dealership would run it through a computer).

The implementation of verification is specific to each issuer, and can be inferred from `verificationMethod` in the credential.
In addition to the `expirationDate` field, which causes the credential to invalidate after a certain date.

This means that identity platforms can allow users to revoke (or expand) credentials without needing to modify the records in ENS.

### Backwards Compatibility

Expand Down

0 comments on commit 560252d

Please sign in to comment.