Splice 0.6.2

• Note that the following endpoints that have been deprecated are planned for removal in the next release (0.6.3), or the following one (0.6.4) at the latest:
  • /v0/closed-rounds
  • /v0/top-validators-by-validator-faucets
  • /v0/synchronizer-identities/{domain_id_prefix}
  • /v0/synchronizer-bootstrapping-transactions/{domain_id_prefix}
  • /v0/aggregated-rounds
  • /v0/round-totals
  • /v0/round-party-totals
  • /v0/amulet-config-for-round
  • /v0/round-of-latest-data
  • /v0/rewards-collected
  • /v0/top-providers-by-app-rewards
  • /v0/top-validators-by-validator-rewards
  • /v0/top-validators-by-purchased-traffic
  • /v0/activities
  • /v0/transactions

• Hard Domain Migrations (HDMs) and HDM-based disaster recovery are no longer supported. In particular:
  • the validator configuration domain-migration-dump-path was removed,
  • the SV onboarding mode domain-migration (name / dump-file-path) was removed.
  Logical synchronizer upgrades (LSU) are now the only supported mechanism for protocol upgrades and network-wide disaster recovery.
• Updated the documentation to clarify that the MIGRATION_ID will not change in the future and that all validators should keep the current value for the foreseeable future.
• Updated the Logical Synchronizer Upgrade documentation to include details for Roll Forward LSUs used for disaster recovery.

• SV only: Introduced the concept of serial ID alongside the existing migration ID for synchronizer deployment. The migration ID is now frozen at its current value and configured only once, as the migration.id field in helm chart values. The serial ID is incremented by 1 for each logical synchronizer upgrade and replaces the migration ID in synchronizer (sequencer/mediator/CometBFT) release names, DNS entries, DB names, chain IDs and port numbers. Participant naming and the participant DB name continue to use MIGRATION_ID, which is now frozen. All example YAML files and documentation have been updated to use SERIAL_ID for addressing and MIGRATION_ID for migration-specific configuration. For existing networks, SERIAL_ID must initially be set to the current value of MIGRATION_ID. Newly initialized networks start with SERIAL_ID=0. This also changed the name of the participant helm installation in the documentation, along with the participantAddress in sv-values.yaml. You can either reinstall the helm chart with the new name or ensure the participantAddress reflects the name of your helm chart installation.
• Fixed a regression introduced in 0.6.1 where the reloader.stakater.com/auto annotation was silently dropped from all Deployments rendered by the Splice helm charts, disabling the auto-reload behaviour regardless of the enableReloader value.

• Bugfixes and stability improvements. Among other things, fix a regression in 0.6.0/0.6.1 which causes participants to get stuck at random times, requiring a restart to recover.