Ensure you are running the same splice version on your node as is run on the primary validator and other covalidating node(s), keeping up to date with the Canton Foundation schedule.
Create / configure the validator node which you will use as your covalidating node. If creating a new node, follow the Canton Network Validator Onboarding Process.
2. Create GitHub App for Reading DAR Repository
Before deploying the service, first a GitHub App must be created within your organization’s GitHub account in order to access the shared DAR repository.
Creating a GitHub App requires GitHub Organization Owner permissions.A single GitHub App can be reused for multiple Covalidation Service deployments within the same organization.
The GitHub App setup process entails:
Create a GitHub App in your organization
Navigate to:
Organization Settings → Developer Settings → GitHub Apps
Select New GitHub App.
Use the following settings.
Repository Permissions
Configure the following permissions.
Installation Scope
Select:
Any account
Then create the application.
After the application has been created, save the following values.
Generate Private Key
Generate a Private Key and store it as a Kubernetes Secret in the namespace where the chart will be installed.
Example:
Share Your GitHub App Details with Primary Validator
After creating the GitHub App:
- Send the Public Link to the primary validator.
- Ask them to install the application into the DAR repository.
- Request the Installation ID from the primary validator.
Primary Validator installs GitHub App into Organization of DAR repository and Provides Installation ID
Once installed, the primary validator will provide you the Installation ID, which is required when configuring the Helm chart.
- Gather details from the Primary Validator and Covalidating operator on DAR repository, GitHub App installation ID and participant IDs so that each co-validator can be configured correctly.
- Configure and Install the Covalidation Service Helm Chart
Install the Covalidation Service Helm Chart
Before installing Covalidation Service, ensure you have:
Prerequisites
- Access to your GitHub organization
- A primary validator willing to share DARs
- A Kubernetes cluster
- A Kubernetes namespace for the deployment
- Helm 3.x (> 3.17.0)
- Kubernetes Secrets containing:
- GitHub App private key
- Participant OIDC client secret
Deploy the service using Helm.
Configuration
A minimal configuration looks like the following.
Configuration Reference
GitHub
DAR Repository
Participant
Replication
Monitoring
Log
Sync Interval
Kubernetes Secrets
The chart expects existing Kubernetes Secrets.
GitHub Private Key
Participant Client Secret
Deployment Flow
Uninstall
Remove the deployment with Helm.
This removes the Kubernetes resources created by the chart but does not delete Kubernetes Secrets or the GitHub App.
Release Notes
Notable changes to the Helm chart are documented below.
2026-08-13
- Party Topology Polling Change party topology polling default to 30s, and make it configurable through
syncInterval configuration in helm chart.
- Party Topology Acceptance Only auto-accept new party topology onboardings, but do not accept topology changes for existing parties.
- Multi-platform Docker Image Support The produced image is now multi-platform and can run on either ARM or AMD Linux platforms.