Skip to content
Documentation/canton-foundation/Canton FoundationView on canton-foundation
canton-foundation/Canton Foundation

Validators - Canton Foundation

Ecosystem

Canton Validators

Getting Network Access

There are several ways to become a validator in the Canton Network

The fastest way to participate in the Canton Network is through a white-label validator node professionally operated by an approved Canton Node-as-a-Service provider. This option gives you immediate access without needing to deploy or maintain your own infrastructure. To get started, reach out to any of the listed operators to discuss pricing, key management, and next steps.

Benefits to Network Access

  • Join the network quickly with minimal setup.
  • Rely on expert operators who manage security, uptime, and compliance.
  • Maintain your own secure identity and permissions within the network.
  • Have the flexibility to transition to operating your own validator in the future.
 

Become a Validator

Apply to operate a Validator Node. The Tokenomics Committee will review your application, with a typical turnaround of about two weeks.

For any questions, please contact operations@canton.foundation

 

 

Validator Node As a Service Provider

To maintain a consistent, secure, and reliable standard across the Canton Network, any entity that would like to publicly announce themselves as a node as a service provider for Canton must meet the minimum technical and operational requirements listed here. These standards reduce risk for all participants. Submissions are reviewed by the Tech and Ops Committee, and the review typically takes about two weeks.

For questions, email operations@canton.foundation

Want to announce your service operating nodes on behalf of your clients? Request to be a Node as a Service provider.

Minimum Requirements

1. Infrastructure Standards
  • All nodes must operate in a production-grade environment (cloud or on-prem), with organizational procedures, firewalls, and operational controls in place.
  • Kubernetes-based deployment is recommended for better lifecycle management, scaling, automated failover, and integration with Canton tooling.
2. History of Uptime
  • Providers must demonstrate DevNet, TestNet, and MainNet operation for at least 15 continuous days, with fewer than 50 rounds missed and all upgrades performed correctly.
3. Demonstration of Multi-Tenancy
  • Providers must have a multi-tenant plan, including a key segregation approach. If distributing rewards, the reward model must be explained.
4. Security & Access Management
  • Providers must secure node operation keys.
  • Providers must use existing wallet solutions or KMS systems to allow customers control of their own keys when hosted on multi-tenant validators.
5. Support & Incident Response
  • Providers must designate technical contacts responsible for hosting operations and maintain a 24/7 shared inbox for incident reporting.
  • Providers must have disaster recovery procedures in place.