A reference implementation of a verifiable credentials platform for digital trade and traceability. Please review this verifiable credentials white paper to understand the business context for this work.
VCs exemplify a decentralized model for high integrity digital data exchange. There is no central data hub. Instead there is a global ecosystem of thousands or millions of issuers, verifiers, and holders. A critical success factor is to reduce the cost of entry into the ecosystem so that it is cheap, fast, and simple for new issuers and verifiers to empower their communities with high integrity digital credentials. This project aims to provide free tools and guidance to facilitate uptake.
If you are an organisation that issues any kind of credential such as a permit, certificate, accreditation, license, or other "claim" of value to your community or constituency, then this project is for you. VCkit provides the tools to equip your existing business systems with the ability to issue your existing credentials as high integrity, standards based, and interoperable VCs that your constituents (VC holders) can present to any party that needs to verify them.
VCs issued by VCkit tooling can be verified using any mobile device camera to scan a QR code. This is important so that uptake can remain compatible with today's paper processes. There is no requirement for verifiers of credentials to adopt any new new technology in order to verify a credential. However, if you are an organisation that is likely to be verifying at scale or you wish to extract the digital data in a credential for use in your business systems then VCkit is also for you. It provides an advanced multi-protocol verification capability that can be integrated with your systems.
The vckit is built on top of the Veramo agent framework. Veramo is a modular agent framework for creating self-sovereign identity (SSI) enabled applications. It is a great place to start if you are new to SSI. The vckit is a set of Veramo plugins that are configured to work together to provide a complete VC issuance and verification capability.
⚠️ Notice: You should install the pnpm package manager globally on your machine by using the npm package manager. You can install pnpm by running the following command:npm install -g [email protected]. Using Corepack to install pnpm that will have some conflicts with the project dependencies that are using yarn package manager to install and build.
This project has been tested and optimized for Node.js version v20.12.2 and pnpm version 8.14.1. Please note that using a Node.js version later than v20.12.2 may result incorrect functionality and potential bugs. It is strongly recommended to use these specific versions for running and testing the project. Deviating from these versions may result in unforeseen compatibility issues or unexpected behavior.
# Install dependencies
pnpm install
# Copy the .env.example file to .env for the demo explorer
cp packages/demo-explorer/.env.example packages/demo-explorer/.env
# Build
pnpm build
# Initialize the agent configuration
pnpm vckit configThe pnpm vckit config command will create a agent.yml file in the root of the project. This file contains the configuration for the Veramo agent. You can edit this file to configure the agent to your needs. The default configuration is sufficient to get started.
# Start the api server
pnpm vckit server
# Start the web server
cd packages/demo-explorer && pnpm devNow you can open the demo explorer at http://localhost:3000. And you can check the api documentation at http://localhost:3332/api-docs.
# Navigate to the documentation folder
cd documentation
# Install dependencies
npm install
# Start the documentation server
npm startNow you can open the documentation at http://localhost:3030.
This Dockerfile is optimized for deploying the VCkit API in production environments. It leverages Docker multi-stage builds to separate the build environment from the runtime environment, resulting in a smaller final image size and enhanced security.
Run the following command in the directory containing the Dockerfile:
docker build -t vckit-api .You can customize the Docker image build process by specifying a custom configuration file path for the VCkit API.
Ensure that you have the custom configuration file (<config_path>) ready. This file should contain the necessary settings and configurations for the VCkit API.
Use the --build-arg flag to specify the DATABASE_TYPE, DATABASE_USERNAME, DATABASE_PASSWORD, DATABASE_NAME, DATABASE_HOST, DATABASE_PORT, DATABASE_ENCRYPTION_KEY, PORT, PROTOCOL, and API_DOMAIN build arguments when running the docker build command.
docker build \
--build-arg DATABASE_TYPE=postgres \
--build-arg DATABASE_USERNAME=postgres \
--build-arg DATABASE_PASSWORD=postgres \
--build-arg DATABASE_NAME=vckit \
--build-arg DATABASE_HOST=localhost \
--build-arg DATABASE_PORT=5432 \
--build-arg DATABASE_ENCRYPTION_KEY=29739248cad1bd1a0fc4d9b75cd4d2990de535baf5caadfdf8d8f86664aa830c \
--build-arg PORT=3332 \
--build-arg PROTOCOL=http \
--build-arg API_DOMAIN=localhost:3332 \
-t vckit-api .Replace the values of the build arguments with your desired configurations.
Execute the following command:
docker run -p 3332:3332 vckit-apiThis will expose the VCkit API on port 3332 of your Docker host.
You can use Docker Compose to manage your VCkit API along with a PostgreSQL database. Docker Compose simplifies the process of orchestrating multiple containers and their dependencies.
Run the following command to start the containers:
docker-compose upThis command will build the Docker images (if not already built) and start the containers defined in the docker-compose.yaml file. The VCkit API will be accessible at http://localhost:3332.