Splice 0.7.2
Upgrade Canton to 3.5.13. The SV app now reconciles the setBalanceRequestSubmissionWindowSize traffic control parameter of the global synchronizer against a new SV app config value…
- A newer release in the 0.7 line: Splice 0.7.5
- Newest Splice: Splice 0.9.4
Runs on Canton 3.5.13
Open the release notes (opens in a new tab)docs.canton.network
-
Upgrade Canton to
3.5.13. -
SV App
-
The SV app now reconciles the
setBalanceRequestSubmissionWindowSizetraffic control parameter of the global synchronizer against a new SV app config valueset-balance-request-submission-window-size, which defaults to Canton’s current default of 2 minutes. This parameter defines the time window used to compute the max sequencing time of traffic purchase (top-up) requests. Canton lowered its default from 4 minutes to 2 minutes (see the Canton 3.5.1 release notes). Networks bootstrapped on an older version (DevNet, TestNet, MainNet) still use the old value for this parameter. By upgrading to this version, SVs agree to change this parameter to 2 minutes (unless they override the new SV app config value). The change takes effect once a sufficient number of SVs have upgraded. - The governance UI no longer stops an SV from casting or changing its vote once a proposal’s target effective time has passed. Votes are now accepted for as long as the vote request is open, matching what the ledger allows. This makes it possible to reject a proposal whose action fails to execute and which would otherwise remain in flight indefinitely.
- Network banner now always shows. The network name is derived from the scan node’s public URL: MainNet/TestNet/DevNet/ScratchNet from the cluster subdomain, LocalNet for localhost, and a capitalized fallback otherwise (Unknown Network when no scan URL is available).
-
The SV app now reconciles the
-
SV UI
- During the creation of
AmuletRules_SetConfigproposal, for therewardConfigconfig field form improve the field descriptions and use drop-downs.
- During the creation of
-
Participant
- Session-signing keys are now officially supported for KMS-enabled validator and SV participants. Please see the updated example configurations for validators and SVs for details on how to enable on Splice deployments. Session signing keys reduce KMS load and cost on KMS-backed participants by signing most messages with short-lived in-memory keys instead of calling the KMS each time.