Skip to content
CCPEDIAby Unity Nodes
ReleasesSplice 0.5.3

Splice 0.5.3

Note: 0.5.2 mistakingly introduced default pruning for Canton participants and should be skipped in favor of 0.5.3. Participants do not prune any data by default. Pruning can be enabled explicitly by any validator…

Note: 0.5.2 mistakingly introduced default pruning for Canton participants and should be skipped in favor of 0.5.3. Participants do not prune any data by default. Pruning can be enabled explicitly by any validator operator. For more information please check the docs.
  • Sequencer connections
    • Improve retries for sending sequencer submissions when a sequencer rejects the request with an overloaded error code by retrying immediately on another node.
    • The network timeout for the connection was lowered to 15 seconds to detect failures faster.
  • Validator
    • Fix bug that caused validators to fail on restoring participant users without rights during a synchronizer migration.
  • Scan
    • The round-based aggregates for balance values (changes to holding fees and initial amounts since round zero) have diverged between scans because of the way amulet expiration is counted in rounds. The balance values recorded in the round aggregates are effectively not depended upon anymore by scan APIs, and are now set to zero to avoid consensus problems when an SV reads aggregates from the rest of the network when first joining.
    • Please note that /v0/total-amulet-balance and /v0/wallet-balance endpoints are marked for removal, and will be removed in an upcoming release. See the Scan OpenAPI documentation for details: /v0/total-amulet-balance and /v0/wallet-balance.
  • Daml
    • Fixed a bug in WalletUserProxy_TransferInstruction_Withdraw, where the controller was required to be the receiver instead of the sender of the transfer instruction. Upgrade to splice-util-featured-app-proxies version 1.2.1 or newer to get the fix.
  • SV app
    • The SV app will no longer store the update history and such, will not be able to answer historical queries. All updates involving the DSO party will still be stored and returned by Scan.
    • Deployment
      • The helm values under scan, that is publicUrl and internalUrl are now mandatory. All SVs already deploy scan on DevNet, TestNet and MainNet so this should have no impact.
  • Docs
    • Improvements to validator docs on Synchronizer Upgrades with Downtime.