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.

Sign up for GitHub

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

fix: cleanup #104

Merged
merged 5 commits into from
Nov 18, 2024
Merged

fix: cleanup #104

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6edfb53
feat: add IssuerService to dcp.jsonld context
arnoweiss Nov 18, 2024
70e0125
fix: remove iatp prefix
arnoweiss Nov 18, 2024
de2714a
fix: remove duplicate dcp context object
arnoweiss Nov 18, 2024
b32314b
fix: align on "verificationMethod" as mandated by did-core
arnoweiss Nov 18, 2024
f077bb5
chore: harmonize table layout in VPP with CIP
arnoweiss Nov 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix: align on "verificationMethod" as mandated by did-core
  • Loading branch information
@arnoweiss
arnoweiss committed Nov 18, 2024
commit b32314b259e716c611730214f41bcb2a830b1be7
6 changes: 3 additions & 3 deletions specifications/credential.issuance.protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,13 +247,13 @@ The following is a non-normative example of a `CredentialStatus` response object
create [=Verifiable Credential] proofs. Key rotation and revocation may be supported in the following way:

1. After a defined `cryptoperiod`, a rotation is initiated, a new key pair is generated and the public key is added
to a `verficationMethod` in the [=Credential Issuer=] DID document. The new private key is used to sign newly
to a `verificationMethod` in the [=Credential Issuer=] DID document. The new private key is used to sign newly
issued [=Verifiable Credential=] proofs.
2. The old private key is decommissioned (archived or destroyed). However, `verificationMethods` in
2. The old private key is decommissioned (archived or destroyed). However, `verificationMethod` in
the [=Credential Issuer=] DID document are retained so existing issued [=Verifiable Credentials=] may be verified.
3. At some point before existing [=Verifiable Credentials=] are set to expire, an [=Credential Issuer=] may make
credential offers for new [=Verifiable Credentials=] to [=Holders=].
4. After a defined period, revocation will be performed where the public key's `verificationMethods` will be removed
4. After a defined period, revocation will be performed where the public key's `verificationMethod` will be removed
from the [=Credential Issuer=] DID document. At this point, any existing [=Verifiable Credentials=] with proofs
signed by the revoked key will not verify.

Expand Down