Skip to content

VC Service

The purpose of this documentation is to help you understand how to configure various schemas and create Issuers and Verifiers for your own scenarios using:

TIP

If you want to engage in lower-level development, read the protocol standard together with the source code in SSI SDK.

Introduction

We have learned about VC and the basic process for applying VCs.

Before we get into the implementation details, we can familiarise ourselves with the terms that we will encounter in the real communication process of Wallet, Verifier and Issuer.

TermDefinition
HolderHolders are entities that have one or more verifiable credentials in their possession. Holders are also the entities that submit proofs to Verifiers to satisfy the requirements described in a Presentation Definition.
IssuerA role an entity can perform by asserting claims about one or more subjects, creating a verifiable credential from these claims, and transmitting the verifiable credential to a holder.
VerifierVerifiers are entities that define what proofs they require from a Holder (via a Presentation Definition) in order to proceed with an interaction.
Verifiable CredentialIs a tamper-evident credential that has authorship that can be cryptographically verified. Verifiable credentials can be used to build Verifiable Presentations, which can also be cryptographically verified. The claims in a credential can be about different subjects. PEX accepts Verifiable credential in 3 forms: 1. JSON_LD which is know in our system as IVerifiableCredential, 2. JWT-Wrapped VC which is known in our system as JwtWrappedVerifiableCredential or string which is a valid Verifiable credential jwt
Verifiable Presentations a tamper-evident presentation encoded in such a way that authorship of the data can be trusted after a process of cryptographic verification.
ManifestCredential Manifests are used to describe which credentials are available for issuance.
ApplicationThe format provided by Holder to Issuer, including
Presentation DefinitionPresentation Definitions are objects that articulate what proofs a Verifier requires.
PresentationData derived from one or more verifiable credentials, issued by one or more issuers
SubmissionTBC
DefinitionTBC
SchemaAll different Manifest, Application, Credential, Presentation, Definition need to define Schema with JSON. The service will verify the correctness of submitted data and then go into business process.

Reference

The following reference materials come from the SSI SDK project.

Specifications

Here are a set of references to specifications that this library currently supports. It is a dynamic set that will change as the library evolves.

Signing Methods