Introduction to Node Operations
Documentation Index
Fetch the complete documentation index at: https://docs.canton.network/llms.txt Use this file to discover all available pages before exploring further.
Introduction to Node Operations
Understanding validator node operations on the Canton Network Global Synchronizer
The Global Synchronizer is the public coordination layer of Canton Network, operated by a decentralized set of validators. This section introduces what it means to operate a node on this network.
What is a Validator?
A validator (also called participant node) is infrastructure that:
- Hosts parties: Stores contract data for the parties it hosts
- Participates in consensus: Confirms transactions affecting its parties
- Exposes APIs: Provides Ledger API access for applications
- Connects to the Global Synchronizer: Provides connectivity to other validators on the Canton Network
flowchart TB
subgraph Validator[Your Validator Node]
PART[Participant<br>Canton runtime]
DB[(Database<br>Party contracts)]
API[Ledger API<br>gRPC / JSON]
PQS[PQS<br>SQL queries]
end
subgraph GS[Global Synchronizer]
SEQ[Sequencer]
MED[Mediator]
end
App[Your Applications] --> API
App --> PQS
API --> PART
PART --> DB
PQS --> PART
PART <--> SEQ
SEQ <--> MED
Validator vs. Super Validator
Validators:
- Host parties and store contracts
- Expose Ledger APIs for applications
- Operated by application operators and enterprises
Super Validators:
- Operate synchronizer infrastructure (sequencer, mediator nodes)
- Participate in network governance
- Operated by major institutions and approved operators
As a validator, you:
- Run your own participant node
- Host parties for your users/applications
- Pay traffic fees in Canton Coin
- Are expected to keep your node updated with versions mandated by the network
- Do not operate synchronizer components (sequencer/mediator)
- Do not participate directly in network governance
- Do not run BFT consensus nodes
Network Environments
Canton Network operates across four environments:
- LocalNet: Local development environment, accessible to anyone, uses local test CC
- DevNet: Integration testing environment, requires VPN and sponsorship, uses faucet for test CC
- TestNet: Staging environment, requires application process, uses faucet for test CC
- MainNet: Production environment, requires full onboarding, CC has real value
Progression Path
flowchart LR
LOCAL[LocalNet<br>Your machine] --> DEV[DevNet<br>Shared test env]
DEV --> TEST[TestNet<br>Staging]
TEST --> MAIN[MainNet<br>Production]
style LOCAL fill:#0277bd,color:#fff
style DEV fill:#ef6c00,color:#fff
style TEST fill:#7b1fa2,color:#fff
style MAIN fill:#2e7d32,color:#fff
Moving between environments requires:
- LocalNet → DevNet: VPN credentials, Super Validator sponsorship
- DevNet → TestNet: Application approval, IP whitelisting
- TestNet → MainNet: Full onboarding process, operational readiness
Operating Models
You have two primary options for running validator infrastructure:
Option 1: Self-Hosted
Run your own validator infrastructure on your own (or cloud) servers.
| Aspect | Details |
|---|---|
| Control | Full control over infrastructure |
| Responsibility | You manage operations, upgrades, security |
| Requirements | Technical expertise, operational capacity |
| Cost | Infrastructure costs + operational overhead |
Best for: Organizations with DevOps/SRE capacity, specific compliance requirements, or need for full control.
Option 2: Node-as-a-Service
Use a provider to host and manage your validator infrastructure.
| Aspect | Details |
|---|---|
| Control | Configuration control; provider manages operations |
| Responsibility | Provider handles upgrades, availability |
| Requirements | Contract with provider |
| Cost | Service fees |
Best for: Teams focused on application development, organizations without infrastructure expertise.
What Running a Validator Involves
Day-to-Day Operations
| Task | Frequency | Description |
|---|---|---|
| Monitoring | Continuous | Health checks, performance metrics |
| Log management | Continuous | Capture and analyze logs |
| Upgrades | Weekly-monthly | Keep pace with network versions |
| Traffic management | As needed | Ensure Canton Coin balance for fees |
| Backup | Regular | Database and identity backups |
Upgrade Expectations
The Global Synchronizer upgrades frequently:
| Type | Frequency | Impact |
|---|---|---|
| Minor updates | Weekly-monthly | Usually backward compatible |
| Feature releases | Quarterly | May require configuration changes |
| Security patches | As needed | Critical; rapid deployment required |
Getting Started
Prerequisites
Before deploying a validator, ensure you have:
- Sponsorship: A Super Validator must sponsor your onboarding
- Infrastructure: Meet the infrastructure requirements
- Technical capacity: Team capable of operating containerized services
- Canton Coin: Budget for traffic fees (TestNet/MainNet)
Onboarding Process
- Contact a Super Validator sponsor (list at canton.foundation)
- Provide your egress IP for network allowlisting
- Wait for allowlisting (typically 2-7 days)
- Obtain onboarding secret from your sponsor
- Deploy your validator with the onboarding configuration
- Verify connectivity and begin operations
Key Responsibilities
As a validator operator, you are responsible for:
| Responsibility | Description |
|---|---|
| Availability | Keep your node running and connected |
| Security | Protect your infrastructure and keys |
| Upgrades | Stay current with network versions |
| Traffic | Maintain Canton Coin balance for fees |
| Compliance | Meet any regulatory requirements for your jurisdiction |
What You Don’t Need to Worry About
The Global Synchronizer handles:
- Consensus: Super Validators run BFT consensus
- Governance: The Global Synchronizer Foundation (GSF) manages network parameters. GSF is the non-profit foundation that governs the Global Synchronizer.
- Sequencing: Synchronizer orders transactions
- Mediation: Synchronizer manages confirmations
Next Steps
Mirrored from Canton Network official documentation (CC-BY-4.0) by CC Privacy Club for learning purposes.