TESTNET SYNCHRONIZER HAS RESUMED PROCESSING

1. #1Wayne Collier26-11-2025source ↗
   The SVs have successfully resumed TestNet on Splice 0.5.1, migration ID 1.As communicated previously, please note:

   • Read the docs
   •  
   • 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.
   •  
   • If you want to minimize rewards you might miss, you'll want to upgrade as soon as possible after the new synchronizer starts up / goes live.
   •  
   • Traffic balances will restart at zero. Any traffic balance held before the major upgrade will be lost. Make sure you're configured to minimize traffic loss
   •  
   • 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
   •  
   • TestNet Migration ID changes as part of this upgrade. The new Migration_ID value for TestNet is 1.
   •  
   • The Super Validators will leave the prior, paused version of the TestNet synchronizer in place for ten days, to allow Validator nodes to catch up, take backups and perform the upgrade.

   The most up to date docs are here:
   https://docs.dev.sync.global/validator_operator/validator_major_upgrades.html#validator-upgrades