For Validators
Operational hub for Super Validators: upgrade alerts, an interactive version check, calendar subscriptions, SV roster, infrastructure proposals, latest release tags.
Active Alerts // Radar
Network State
Super Validators // 13 active
Upgrade Check
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.8
- Next minimum
- -
- Required next
- 0.9.x by 2026-11-06
- 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.9.3 | 285 | 19% | 285 of 285 |
| 0.8.4 | 253 | 17% | 253 of 253 |
| 0.5.18 | 186 | 12% | 0 of 186 |
| 0.8.3 | 125 | 8% | 124 of 125 |
| 0.8.0 | 116 | 8% | 108 of 116 |
| 0.8.1 | 53 | 3% | 44 of 53 |
| 0.6.10 | 38 | 2% | 0 of 38 |
| 0.6.3 | 33 | 2% | 0 of 33 |
| 0.5.13 | 31 | 2% | 0 of 31 |
| 0.6.7 | 31 | 2% | 0 of 31 |
These are self-reported figures, not observations. Each validator publishes its own version in its DSO license metadata, and 707 of 1533 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.8 | 2026-11-17 14:00 UTC · in 26d | 2026-11-18 14:00 UTC · in 27d |
| TestNet | 0.8 | 2026-11-03 14:00 UTC · in 12d | 2026-11-04 14:00 UTC · in 13d |
| MainNet | 0.8 | 2026-11-06 14:00 UTC · in 15d | 2026-11-07 14:00 UTC · in 16d |
A topology freeze blocks topology changes (onboarding, key rotation, party allocation) for 24h before the Logical Synchronizer Upgrade.
Upcoming schedule // MainNet
| Date | UTC | Type | Version | What |
|---|---|---|---|---|
| 2026-11-06 | 14:00 | topology freeze | 0.9 | MainNet: Topology Freeze (0.9.x Required) (November 2026) |
| 2026-11-07 | 14:00 | lsu | 0.9 | MainNet: Logical Synchronizer Upgrade (0.9.x Required) (November 2026) |
| 2026-11-09 | - | weekly upgrade | 0.9.4 | MainNet upgrades to Splice 0.9.4 |
| 2026-11-10 | 14:00 | daml models effective | 0.9 | MainNet: Daml models introduced by Splice 0.9.x take effect |
| 2026-11-16 | - | weekly upgrade | 0.10.0 | MainNet upgrades to Splice 0.10.0 |
| 2026-11-17 | 14:00 | breaking change | 0.9 | MainNet: Breaking configurations introduced by Splice 0.9.x take effect |
| 2026-11-23 | - | weekly upgrade | 0.10.1 | MainNet upgrades to Splice 0.10.1 |
| 2026-11-30 | - | weekly upgrade | 0.10.2 | MainNet upgrades to Splice 0.10.2 |
| 2026-12-01 | 14:00 | daml models effective | 0.10 | MainNet: Daml models introduced by Splice 0.10.x take effect |
| 2026-12-07 | - | weekly upgrade | 0.10.3 | MainNet upgrades to Splice 0.10.3 |
| 2026-12-08 | 14:00 | breaking change | 0.10 | MainNet: Breaking configuration changes introduced by Splice 0.10.x take effect |
| 2026-12-11 | 14:00 | topology freeze | 0.10 | MainNet: Topology Freeze (0.10.x Required) (December 2026) |
Subscribe to the Operations Calendar
https://ccpedia.xyz/api/calendar/validator.icshttps://ccpedia.xyz/api/calendar/sv.icshttps://ccpedia.xyz/api/calendar/mainnet.icshttps://ccpedia.xyz/api/calendar/testnet.icshttps://ccpedia.xyz/api/calendar/devnet.icsSubscribe adds a live feed that refreshes on its own. Copy URL gives you the same thing as https, for clients that will not take a webcal link. Both point at the same file, which is regenerated every 30 minutes from the Foundation schedule.
Next up for validator operators
| When | Network | Version | What |
|---|---|---|---|
| 2026-10-26 · in 4 days | DevNet | 0.9.4 | DevNet upgrades to Splice 0.9.4 |
| 2026-11-02 · in 11 days | TestNet | 0.9.4 | TestNet upgrades to Splice 0.9.4 |
| 2026-11-02 · in 11 days | DevNet | 0.10.0 | DevNet upgrades to Splice 0.10.0 |
| 2026-11-03 · in 12 days | TestNet | 0.9 | TestNet: Daml models introduced by Splice 0.9.x take effect |
| 2026-11-03 · in 12 days | DevNet | 0.9 | DevNet: Breaking configuration changes introduced by Splice 0.9.x take effect |
| 2026-11-04 · in 13 days | TestNet | 0.9 | TestNet: LSU (0.9.x Required) (November 2026) |
| 2026-11-07 · in 16 days | MainNet | 0.9 | MainNet: Logical Synchronizer Upgrade (0.9.x Required) (November 2026) |
| 2026-11-09 · in 18 days | MainNet | 0.9.4 | MainNet upgrades to Splice 0.9.4 |
| 2026-11-09 · in 18 days | TestNet | 0.10.0 | TestNet upgrades to Splice 0.10.0 |
| 2026-11-09 · in 18 days | DevNet | 0.10.1 | DevNet upgrades to Splice 0.10.1 |
| 2026-11-10 · in 19 days | MainNet | 0.9 | MainNet: Daml models introduced by Splice 0.9.x take effect |
| 2026-11-10 · in 19 days | TestNet | 0.9 | TestNet: Breaking configuration changes introduced by Splice 0.9.x take effect |
| 2026-11-16 · in 25 days | MainNet | 0.10.0 | MainNet upgrades to Splice 0.10.0 |
| 2026-11-16 · in 25 days | TestNet | 0.10.1 | TestNet upgrades to Splice 0.10.1 |
CCPEDIA parses the Foundation schedule and attributes a network to 517 of 596 events, extracting a Splice version wherever the source states one. The remaining 79 events have no network attributed with confidence and are not served in the feeds above - a wrong deadline in an operator's calendar is worse than an absent one.
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 are not published yet. 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.