The Global Synchronizer is the public infrastructure backbone of Canton Network, a decentralized synchronizer operated by Super Validators.
What It Is
The Global Synchronizer is:
- A synchronizer instance (BFT configuration of several sequencer + mediator nodes) operated by multiple independent parties
- Decentralized: No single entity controls it
- The default coordination layer for Canton Network applications
- Governed by the Global Synchronizer Foundation (under Linux Foundation)
Things to note:
- The Global Synchronizer is not a separate blockchain from Canton Network
- Validators store their own state; the Global Synchronizer is not a separate storage layer
- Private synchronizers can also exist; the Global Synchronizer is not required for all Canton applications
Canton Coin (CC)
Canton Coin is the native utility token of the Global Synchronizer, used for:
| Use | Description |
|---|
| Transaction fees (Traffic) | Pay for network usage when submitting transactions |
| Infrastructure rewards | Incentivize synchronizer operators for providing infrastructure |
| Governance participation | Super Validators stake CC to participate in governance |
Canton Coin is implemented via Splice, a set of reference applications that provide the economic and governance infrastructure for decentralized synchronizers.
Traffic (Transaction Fees)
“Traffic” is Canton’s term for transaction fees. When you submit transactions through the Global Synchronizer, you pay traffic costs in Canton Coin.
Traffic costs largely depend on:
- Transaction size
- Computational complexity
- Current network demand
Obtaining Canton Coin
| Environment | Method |
|---|
| LocalNet | Local test CC with no real value |
| DevNet | Faucet (“tapping”) provides test CC |
| TestNet | Faucet provides test CC |
| MainNet | Purchase from exchanges or earn through network activity |
Network Environments
Canton Network operates across four environments, each serving a different purpose in the development lifecycle.
| Environment | Purpose | How to Access | CC Type |
|---|
| LocalNet | Local development | Run locally on your machine | Test (no value) |
| DevNet | Integration testing | VPN credentials + SV sponsorship | Test (faucet) |
| TestNet | Staging/validation | Application process | Test (faucet) |
| MainNet | Production | Full onboarding | Real value |
LocalNet
LocalNet simulates a Global Synchronizer that runs entirely on your machine - no external network required.
- Purpose: Development and initial testing
- Access: Anyone with Daml SDK installed
- Limitations: Single-machine; doesn’t test real network behavior
When to use: Writing and testing Daml contracts; initial application development; learning Canton.
DevNet
- Purpose: Integration testing with real network infrastructure
- Access: Requires VPN credentials and Super Validator sponsorship
- CC: Test tokens available via faucet (“tapping”)
When to use: Testing multi-validator workflows; validating network integration; pre-production testing.
Access process:
- Contact a Super Validator sponsor
- Receive VPN credentials
- Configure your validator to connect
- Tap for test CC
TestNet
- Purpose: Staging environment; final validation before production
- Access: Application process through Canton Network
- CC: Test tokens; no real value
When to use: Final integration testing; performance validation; user acceptance testing; practice CN and application upgrades.
MainNet
- Purpose: Production environment
- Access: Complete onboarding process
- CC: Real economic value once approved as a featured application
When to use: Production deployments; real transactions; live applications.
DevNet, TestNet, and MainNet all run on infrastructure operated by the same Super Validators. The difference is in access requirements and whether Canton Coin has real economic value.
Environment Progression
Moving through environments requires:
- LocalNet → DevNet: VPN access, SV sponsorship
- DevNet → TestNet: Application approval, operational readiness
- TestNet → MainNet: Full onboarding, production readiness review
Super Validators
Super Validators (SVs) are the entities that operate the Global Synchronizer infrastructure.
Responsibilities
| Responsibility | Description |
|---|
| Infrastructure operation | Run sequencer and mediator nodes |
| Governance participation | Vote on network parameters and upgrades |
| Validator sponsorship | Sponsor new validators joining the network |
| Rewards distribution | Receive and distribute validator rewards |
The Decentralized Synchronizer Operator (DSO)
A group of Super Validators operating nodes together form the DSO. The DSO collectively:
- Operates the synchronizer infrastructure
- Makes governance decisions
- Manages the Splice applications
- Onboards new participants
Super Validators include major financial institutions and technology providers. The current list is maintained by the Global Synchronizer Foundation.
Becoming a Validator
To participate as a validator on the Global Synchronizer:
Options
| Approach | Description | Effort | Control |
|---|
| Node-as-a-Service | Use a provider to host your validator | Least | Medium |
| Self-hosted | Run your own validator infrastructure | Most | Full |
Requirements
- Obtain sponsorship: A Super Validator must sponsor your onboarding
- Deploy infrastructure: Set up validator node(s) with required specifications
- Connect to synchronizer: Configure network connectivity
- Manage upgrades: The network upgrades frequently; validators must keep pace
- Contact a Super Validator (list available at canton.foundation)
- Describe your use case and organization
- Complete any required agreements
- Receive sponsorship and access credentials
For application developers, the simpler path is often using an existing validator (node-as-a-service) rather than self-hosting. This provides network access without operational overhead.
Governance
Global Synchronizer Foundation
The Global Synchronizer Foundation (GSF) is an independent, non-profit body under the Linux Foundation that governs the Global Synchronizer.
Responsibilities:
- Set network policies and parameters
- Coordinate upgrades and maintenance
- Oversee Super Validator participation
- Manage the Splice codebase governance
- Review and commission featured applications
Decision-Making
Governance decisions follow a structured process:
- Proposal: Any SV can propose changes
- Discussion: SVs discuss implications and modifications
- Voting: SVs vote according to governance rules
- Implementation: Approved changes are implemented
What Gets Governed
| Area | Examples |
|---|
| Protocol parameters | Transaction limits, timing windows |
| Economic parameters | Fee structures, reward distributions |
| Membership | SV admission, validator requirements |
| Upgrades | Protocol versions, upgrade schedules |
Splice Applications
Splice is the open-source project (under Hyperledger Labs) providing infrastructure for operating, funding, and governing decentralized Canton synchronizers.
Components
| Component | Purpose |
|---|
| Canton Coin | Native token implementation |
| Validator App | Validator node management |
| Wallet | User wallet for CC |
| Scan | Network explorer |
| Governance | Voting and proposal management |
Token Standard
Splice includes a token standard (CIP-0056) for creating tokens on Canton Network. This provides:
- Standard interfaces for token operations
- Interoperability between applications
- Consistent wallet integration
Upgrade Considerations
The Global Synchronizer and validators currently have frequent upgrades with the rate expected to slow in the next year. As a validator or application developer, expect:
| Frequency | Type | Impact |
|---|
| Weekly-Monthly | Minor updates | Minimal; usually backward compatible |
| Quarterly | Feature releases | May require application updates |
| As needed | Security patches | Critical; rapid deployment required |
Staying Current
- Monitor announcements: Subscribe to Canton Network communications
- Test on DevNet/TestNet: Validate compatibility before MainNet upgrades
- Plan maintenance windows: Schedule time for updates
- Maintain rollback capability: Have procedures for reverting if needed
- Join community channels: #gsf-global-synchronizer-appdev, #gsf-outreach, #validator-operations
Next Steps