What is deployed on the Canton Network, what is scheduled, whether it is confirmed, and where every fact came from. Every value links to the record it was published from; the arrow beside it opens the upstream document that was polled.
The highest version the Splice tags endpoint carries. A release existing is not a network running it; what each network is on is below.
| Network | Current (scheduled) | SVs on it | Since | Minimum | Next | Due | Reported |
|---|
Current is the last confirmed upgrade on the SV Operations Schedule whose date has arrived. The schedule states what the operators intend, so a date that has arrived is not proof the upgrade ran. Minimum is the oldest version a validator may run. Next is the earliest upgrade still ahead, confirmed or not. SVs on it counts the Super Validator nodes whose own roster entry reports that version. Reported is the version the network's own info document states.
From the SV Operations Schedule.
| Date | Network | Event | Status | Version |
|---|
The hosts each Super Validator node publishes, as the network's own DSO document states them. Scan is the node's public read endpoint. A participant connects to a sequencer, and the sequencer changes at every synchronizer serial: while an upgrade is in flight, and for a while after it, a node lists one per serial, highest first. A serial below the one the network reports as current is marked legacy, one above it successor.
| Source | Publisher | Authority | State | Last polled | Last success | Last changed |
|---|
Everything that changed, newest first.
| Observed (UTC) | Network | Subject | Change | What moved |
|---|