-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Description
Missing update-credential command
Problem
Currently there's no way to update an existing credential after it's been issued. The workflow supports:
bind-credential- create credential templateissue-credential- sign and publish credentialrevoke-credential- invalidate credential- Missing:
update-credential- modify existing credential
Use Case
Real-world scenario from today:
- Issued Proof-of-Human credential to subject
- Subject revealed it to their manifest
- Realized evidence text was too candid for public consumption
- No way to update the credential - had to issue entirely new one
This creates:
- Multiple credential DIDs for the same attestation
- Confusion about which version is "current"
- Wasted credentials in the registry
Expected Behavior
# Update existing credential with new claims/evidence
npx @didcid/keymaster update-credential <credential-did> <updated-file>This should:
- Retrieve the existing credential
- Validate issuer permissions
- Update the credential document
- Re-sign with new proof
- Publish updated version
- Maintain same credential DID
Alternative Workarounds
If updating same DID isn't possible due to immutability:
- Add
supersedesfield to credentials issue-credential --supersedes <old-did>marks old credential as replaced- Holders can re-publish updated credential over old one
Context
- Discovered during credential issuance workflow testing
- Related to privacy controls (publish vs reveal)
- Affects user experience when iterating on credential content
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels