Upgrade Check
Canton validators must stay above a minimum Splice version that changes weekly and differs per network. Below the minimum, a node stops accepting and sending transactions.
The schedule below applies to every operator. Add your version for a verdict and the breaking changes you have not absorbed.
- Running
- —
- Minimum now
- 0.6.9
- Next minimum
- 0.6.11
- Behind by
- —
Where you sit in the fleet
Enter your version above to see where it sits against the rest of the fleet.
| Version | Nodes | Share | Reported in last 30d |
|---|---|---|---|
| 0.6.10 | 341 | 28% | 341 of 341 |
| 0.5.18 | 189 | 16% | 0 of 189 |
| 0.6.11 | 139 | 11% | 139 of 139 |
| 0.6.7 | 94 | 8% | 87 of 94 |
| 0.6.9 | 89 | 7% | 89 of 89 |
| 0.6.3 | 34 | 3% | 0 of 34 |
| 0.5.13 | 32 | 3% | 0 of 32 |
| 0.6.6 | 26 | 2% | 10 of 26 |
| 0.5.15 | 25 | 2% | 0 of 25 |
| 0.6.2 | 24 | 2% | 0 of 24 |
These are self-reported figures, not observations. Each validator publishes its own version in its DSO license metadata, and 514 of 1211 nodes last refreshed that metadata more than 30 days ago. A node listed on an old release may genuinely be that far behind, or may simply have stopped updating its metadata, and this data cannot tell the two apart. Read the distribution as a rough shape of the fleet rather than as a precise census.
Next deadlines // all networks
| Network | Minimum now | Topology freeze | Next LSU |
|---|---|---|---|
| DevNet | 0.6.11 | 2026-07-21 13:00 UTC · today | 2026-07-22 13:00 UTC · tomorrow |
| TestNet | 0.6.11 | 2026-08-25 13:00 UTC · in 35d | 2026-08-26 13:00 UTC · in 36d |
| MainNet | 0.6.9 | 2026-09-04 13:00 UTC · in 45d | 2026-09-05 13:00 UTC · in 46d |
A topology freeze blocks topology changes — onboarding, key rotation, party allocation — for 24h before the Logical Synchronizer Upgrade.
Minimum .dar packages
Upcoming schedule // MainNet
| Date | UTC | Type | Version | What |
|---|---|---|---|---|
| 2026-07-21 | — | daml models effective | 0.6.9 | MainNet: Daml models from Splice 0.6.9 effective (required for CIP-119) |
| 2026-07-27 | — | weekly upgrade | 0.6.12 | MainNet upgrades to Splice 0.6.12 |
| 2026-07-27 | — | minimum version | 0.6.11 | Minimum version |
| 2026-07-28 | — | daml models effective | 0.6.11 | MainNet: Daml models from Splice 0.6.11 effective (required for CIP-112) |
| 2026-07-28 | — | dar versions | — | Minimum .dar package versions |
| 2026-08-03 | — | weekly upgrade | 0.6.13 | MainNet upgrades to Splice 0.6.13 |
| 2026-08-10 | — | weekly upgrade | 0.6.14 | MainNet upgrades to Splice 0.6.14 |
| 2026-08-17 | — | weekly upgrade | 0.7.0 | MainNet upgrades to Splice 0.7.0 |
| 2026-08-17 | — | breaking change | — | MainNet Breaking API Change: Deprecated TransferCommand functionality removed from validator app… |
| 2026-08-24 | — | weekly upgrade | 0.7.1 | MainNet upgrades to Splice 0.7.1 |
| 2026-08-31 | — | weekly upgrade | 0.7.2 | MainNet upgrades to Splice 0.7.2 |
| 2026-09-01 | — | daml models effective | 0.7 | MainNet new Daml models effective (0.7) |
Automate it
Your node cannot know these deadlines on its own — they live in the Foundation calendar, not in any local metric. Scrape them and the two alerts that actually prevent an outage, below the minimum and freeze in 24h, become ordinary PromQL.
- job_name: canton_schedule
scrape_interval: 15m
scheme: https
metrics_path: /api/ops-metrics
static_configs:
- targets: ['ccpedia.xyz']Alert rules and Alertmanager routing: deploy/alerting. Metrics: /api/ops-metrics. AI tools can ask the same question via MCP (get_upgrade_status). Schedule parsed from the Canton Foundation SV calendar; breaking changes from the official Splice release notes. See Validators for the wider operational picture.
