Canton Project Overview

Background

ChainSafe runs and manages two mainnet validators and one devnet validator on the Canton network. The objective is to generate Canton Coins (CC) by maintaining validator uptime and operating Canton applications.

Architecture Overview

Network Components

Infrastructure Stack

Kubernetes Infrastructure

• Managed Kubernetes on AWS EKS
  • Development Environment:
    • Cluster: infra-dev
    • AWS Account: infra-dev
  • Production Environment:
    • Cluster: infra-prod
    • AWS Account: infra-prod
  • Infrastructure as Code: EKS Cluster Setup

Deployment Management

• GitOps with ArgoCD
  • Development: ArgoCD Dev Console
  • Production: ArgoCD Prod Console
  • Application Configurations: ArgoCD Apps Repository

Service Inventory

• Canton UI Infrastructure Inventory

Deployment and Operations

Upgrade Process

1. Prepare the change (Dev)
   • Update the Helm chart targetRevision for the dev environment.
   • Open a PR against main. For example: Sample PR #21.
2. Deploy to Dev
   • ArgoCD Dev Console will automatically sync changes merged to main.
3. Validate in Dev
   • Perform smoke tests for validator pods, RPC endpoints, and dashboards.
   • Confirm validator metrics are healthy and CC balance increases over the observation window.
4. Promote to Prod
   • Create a PR from main to prod-main to roll out the change to prod. For example: Sample PR #22.
   • After merge, verify ArgoCD sync and that the rollout completed successfully in the prod cluster.
5. Post-deployment checks
   • Re-verify validator health, metrics, and uptime alerts in prod.
   • Announce completion in #validator-operations.

Rollback Procedure

• Dev: revert the Helm chart targetRevision via a PR to main and let ArgoCD sync, or use the ArgoCD app history to roll back to the previous revision.
• Prod: revert the prod-main PR (or submit a follow-up PR restoring the previous targetRevision) and confirm ArgoCD rolls back; alternatively, use ArgoCD app history to roll back to the last healthy revision.

Monitoring & Observability

• Metrics:
  • Infrastructure, node performance, and validator metrics are collected and sent to the infrastructure metrics platform.
• Uptime:
  • BetterStack monitors public endpoints and UI components for availability.
• Logging:
  • Application and infrastructure logs are shipped to the centralized logging backend.

Documentation & Resources

Essential Documentation

• Validator Documentation
• Utility UI Documentation
• 5N Network Explorer

Links

Apps	DevNet	Chainsafe Mainnet	Round13 Mainnet
Wallet UI	wallet-validator-dev1.01.chainsafe.dev	wallet-validator-prod1.02.chainsafe.dev	wallet-validator-round13.02.chainsafe.dev
CNS UI	cns-validator-dev1.01.chainsafe.dev	cns-validator-prod1.02.chainsafe.dev	cns-validator-round13.02.chainsafe.dev
Utility UI	utility-validator-dev1.01.chainsafe.dev	utility-validator-prod1.02.chainsafe.dev	utility-validator-round13.02.chainsafe.dev
Cantara	cantara-testnet.thetie.io	cantara.thetie.io	cantara.thetie.io
5N dashboard	5n-dashboard-validator-dev1.01.chainsafe.dev	5n-dashboard-validator-prod1.02.chainsafe.dev	5n-dashboard-validator-round13.02.chainsafe.dev
Cantara Data App	canton-data-app-validator-dev1.01.chainsafe.dev	canton-data-app-validator-prod1.02.chainsafe.dev	canton-data-app-validator-round13.02.chainsafe.dev

Communication Channels

• Validator Operations: #validator-operations
  • Primary channel for validator-related discussions
  • Update announcements
• Utility Operations: #utility-ops
  • Utility UI and DARS related communications
  • System updates and changes