CCPEDIAby Unity Nodes
Mailing Lists/MAINNET IS NOW LIVESource on lists.sync.global ↗

MAINNET IS NOW LIVE

validator-announce1 messagesstarted 10-12-2025
  1. #1Wayne Collier10-12-2025source ↗
    The SVs have successfully resumed MainNet on Splice 0.5.1, migration ID 4
    Before proceeding, confirm that you have completed your Validator migration dump on Splice 0.4.23, migration ID 3. 
     
    Once you have confirmed that you have a complete migration dump on Splice 0.4.23 and Migration ID 3, you may restart your Validator node using Splice 0.5.1 and re-join MainNet. 
     
    The most up to date docs are here: https://docs.dev.sync.global/validator_operator/validator_major_upgrades.html#validator-upgrades
     
    Because of the size of the topology import involved, this upgrade may take longer than normal (~10 to ~15 minutes). 

    As communicated previously, please note:
    •  
    • The upgrade path for Validator nodes is Splice 0.4.23 -> Splice 0.5.1. Splice 0.4.25 -> 0.5.1 is also acceptable.
    •  
    • 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
    •  
    • MainNet Migration ID changes as part of this upgrade. The new Migration_ID value for MainNet is 4.
    •  
    • The Super Validators will leave the prior, paused version of the MainNet synchronizer in place for ten days, to allow Validator nodes to catch up, take backups and perform the upgrade.
    •  
    • 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. Expect a dedicated announcement for this once a threshold of SVs have upgraded. Please always upgrade from 0.4.x to 0.5.1 first, and only 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 can not be considered safe.
    •