Validator Versions
What Splice version do Canton Network validators actually run?
Of 1324 DSO-approved Canton Network validators that report a version, 399 run Splice 0.7.3, the most common release.
The figures are self-reported by each operator and refreshed daily. Last updated 2026-09-06.
Version distribution
| Splice version | Validators | Share | Reported in last 30 days |
|---|---|---|---|
| 0.7.3 | 399 | 30% | 399 of 399 |
| 0.5.18 | 186 | 14% | 0 of 186 |
| 0.7.1 | 99 | 7% | 99 of 99 |
| 0.7.0 | 71 | 5% | 71 of 71 |
| 0.6.14 | 57 | 4% | 56 of 57 |
| 0.6.13 | 46 | 3% | 24 of 46 |
| 0.6.10 | 43 | 3% | 0 of 43 |
| 0.6.7 | 34 | 3% | 0 of 34 |
| 0.6.3 | 33 | 2% | 0 of 33 |
| 0.5.13 | 31 | 2% | 0 of 31 |
| 0.5.15 | 25 | 2% | 0 of 25 |
| 0.6.11 | 24 | 2% | 4 of 24 |
How many are below the minimum, per network
| Network | Minimum in force | Validators below it |
|---|---|---|
| MainNet | 0.7 | - |
| TestNet | 0.7 | - |
| DevNet | 0.7 | - |
One fleet, three minimums. A validator serves a single network, so these counts overlap: the same node can be current for MainNet and behind for DevNet.
What the numbers do not tell you
These versions are published by operators in their own licence metadata. They are not observed from the network. 644 of 1324 validators last refreshed that metadata more than 30 days ago, so only 51% of the distribution is backed by a recent report.
The gap matters. Every one of the 186 validators listed on 0.5.18 has a stale report, which reads more like an abandoned record than a fleet of nodes running that release today. Treat the shape as approximate and the tail as unreliable.
Common questions
- What Splice version do most Canton Network validators run?
- 0.7.3 is the most common, on 399 of 1324 validators that report a version. The fleet is spread across 64 distinct versions, so there is no single version the network runs.
- How many Canton validators are below the minimum required version?
- The current minimum version could not be resolved from the schedule.
- What happens if a Canton validator falls below the minimum version?
- A node below the minimum stops accepting and sending transactions on that network. The minimum is raised on a published schedule, so the deadline is known in advance rather than discovered at failure.
- Are these Canton validator versions self-reported or measured?
- Self-reported. Each operator publishes a version in its DSO licence metadata. 644 of 1324 last refreshed that metadata more than 30 days ago, so a node listed on an old release may be behind or may simply have stopped updating.
- Where does this Canton validator version data come from?
- The public Canton Scan API, specifically the DSO-approved validator licence list. CCPEDIA reads every licence, groups the self-reported versions, and refreshes daily.
Method and source
Every DSO-approved validator licence is read from the public Canton Scan API, the self-reported version is taken from each licence's metadata, and the results are grouped. Operator contact details present in the same payload are never stored. The sync runs daily; this page renders whatever the latest run produced, so it does not go stale between edits.
To check your own node against the minimum and see your place in this distribution, use the upgrade check. For the schedule that raises these minimums, see the operations calendar. AI tools can query the same data through MCP with get_validator_fleet.