MAINNET PAUSED FOR MAJOR UPRADE WITH DOWNTIME

1. #1Wayne Collier10-12-2025source ↗

   MainNet is currently paused for the major upgrade to 0.5.1.

    

   You should be see a `Wrote domain migration dump` record in validator app logs within the next minutes.

    

   The Super Validators will share an update here once the they have successfully bootstrapped the new synchronizer and it is safe for validators to re-join. Based on the size of MainNet state, this is expected to take between 3 and 6 hours.

    

   Other pointers, in line with previous communication:

    

   • The proven upgrade path is 0.4.23 -> 0.5.1. You must upgrade your Validator to 0.4.23 or 0.4.25 before the major upgrade. Upgrading to Splice 0.4.25 is optional; the 0.4.25 -> 0.5.1 upgrade path will also succeed.

    

   • To rejoin the network and resume processing transactions, Validators must complete the migration steps outlined in the technical documentation for Major Upgrades, here: https://docs.dev.sync.global/validator_operator/validator_major_upgrades.html

    

   • MainNet’s Migration ID will change as part of this upgrade. The Super Validators will announce the new Migration ID once MainNet comes back online. The default Migration_ID value will be 4, unless announced otherwise by the Super Validators.

    

   • Every node should take a full backup of its node and identities before the upgrade. Details here: https://docs.dev.sync.global/validator_operator/validator_backups.html#backups

    

   • Ledger API transaction history is not preserved in the current approach to major upgrades on Canton. The participant component in your Validator node will start with an empty history after the upgrade. The Scan history generated by the Super Validators is unaffected and will retain all information from before the upgrade. For more details please see: https://docs.dev.sync.global/validator_operator/validator_major_upgrades.html#implications-for-apps-and-integrations

    

   • Note that, as outlined in the long-term schedule, this major upgrade will be followed immediately by a minor (non-forking) upgrade to Splice 0.5.4. Please only upgrade from 0.4.x to 0.5.1 first, and then upgrade from 0.5.1 to 0.5.4 once you have confirmed that your validator has become healthy on 0.5.1 and migration ID 4. A direct jump from 0.4.x to 0.5.4 cannot be considered safe.