Usage of VC

With Verifiable Credential technology, users would have full control over the information they share. Indeed, they can decide with whom to share, to what extent and so on. In this section, we show three types of VC disclosures:

• Digest Disclosure, which aims to prove someone owns a certain cType verifiable credential without revealing any credential details

• Selective disclosure, makes it possible to choose exactly which data is disclosed.

• All Credential Content Disclosure, helps users to offer the full details of a credential.

Check Use Case for more details and experience our demo website which help illustrate this concept.

Digest Disclosure

This kind of disclosure only contains unprivate info, such as cType, Attester, ClaimHash, Owner. Here, Digest indicates that this kind of disclosure implies some info about credential.

As an instance, assuming cType C1 is created by zCloak, and the purpose of creating this cType is to issue a 'zCloak Membership Credential'. Only the user who is a member of zCloak Membership could own such a C1 Credential.

So, if a user can show a Digest Disclosure of a valid Credential, which 'cType' is C1, 'Attester' is zCloak, then we can confirm that the user is a member of zCloak without looking into the whole credential which may contain more personal details.

In a word, Digest Disclosure is normally used when the valid existence of credential is what we care most, rather than the details.

Digest Disclosure

Developers can request for Digest Disclosure via the API (VC Request Method) we provided, click to check more specification.

Selective Disclosure

Unlike the first case, Claimer can select one or more pieces of information to share. For example, in the case of verifying an identity, this method allows the user to share only their ID Number, without necessarily revealing their date or place of birth. This feature of digitized credentials makes the platform more targeted to privacy protection by providing individuals with granular control over the information shared with various institutions and entities.

Selective Disclosure

Developers can request for Selective Disclosure via the API (VC Request Method) we provided, click to check more specification.

All Credential Content Disclosure

Through this kind of disclosure, the service provider has access to all pieces of the credential information if the Claimer chooses to share them all. This is the highest trust level of presentation, since the Claimer needs to reveal all information of that credential.

All Credential Content Disclosure

Developers can request for All Credential Content Disclosure via the API (VC Request Method) we provided, click to check more specification.