Implmentation of Verifiable Credential Extension Registry

[Vishwas1]

Please refer to this discussion #140

A Verifiable Credential Extension Registry [VC-EXTENSION-REGISTRY] exists that contains available status schemes for implementers who want to implement verifiable credential status checking.

• revocation
• suspend
• dispute

The identity node can resolve the status of a verifiable credential with an LTO DID URL as credential status. Resolving the status results in a credential status list https://w3c-ccg.github.io/vc-csl2017/

https://w3c-ccg.github.io/vc-extension-registry/
https://docs.ltonetwork.com/protocol/identities/verifiable-credentials#associations
https://docs.ltonetwork.com/protocol/identities/verifiable-credentials

[Vishwas1]

Creation of VC registry

message : { 
   "claim": {
      "id": "credential Id",
      "currentStatus": "Revoke",  // | Live | Revoke
      "statusReason": "Disciplinary action" // comment
    },
    "issuer": "did or issuer",
    "issued": "2017-12-05T14:27:42Z",
   }     

What is proof?

const messageBytes = bytes of message;
const signed = ed25519.sign(privateKeyMultibase,  messageBytes ); 

const proof = {
    "type": "Ed25519Signature2020",
    "created": "2022-05-20T04:07:17Z",
    "verificationMethod": "did:hs:092fe5aa-1e27-4705-9ed2-b389b962cd83#z3Cn3AXpHMBWBfV14KSBwGqWnBdHEAf6zP74SR4JWuANT",
    "proofPurpose": "assertionMethod",
    "proofValue": signed 
}

What you store in blockchain:

key <> value
vc_id <> message  + proof (?)

Value

const value = 
    { 
   "claim": {
      "id": "credential Id",
      "currentStatus": "Suspended",  // | Live | Suspended
      "statusReason": "Disciplinary action" // comment
    },
    "issuer": "did or issuer",
    "issued": "2017-12-05T14:27:42Z",
     "proof":   {
            "type": "Ed25519Signature2020",
            "created": "2022-05-20T04:07:17Z",
            "verificationMethod": "did:hs:092fe5aa-1e27-4705-9ed2-b389b962cd83#z3Cn3AXpHMBWBfV14KSBwGqWnBdHEAf6zP74SR4JWuANT",
            "proofPurpose": "assertionMethod",
            "proofValue": signed 
        }
   } 

Retrival

1. Given credentialid -> fetch the metadata / status
2. Fetch list of all metadatas based on pagination

[Vishwas1]

-------Node side-------------------------------

• Add a field "credentialHash" in Credstatus obj
• add a field "updatedAt" is credProof object
• update the fields "issued" to "issuanceDate" in Credstatus obj
• add field expirationDate in Credstatus obj

Credstatus types:

• Live: A new credenital issued with Live status. statusReason is optional
• Suspend: A credentail can be temporarly suspened within expiration period. statusReason must be provided. It can be made Live in furture.
• Revoke: A credential can be revoked permanetly within expiration period. statusReason must be provided. Once revoked it can not made Live.
• Expired: A credential automatically is expired after expirationDate

-------SDK side-------------------------------

How would you produce the 'credentialHash' at the SDK:?

credentialHash = HASH(credential)

What will be the algrightm of producing this HASH?

Depends on SDK