Splice 0.5.11

Digital AssetFeb 13, 2026Splice

SV node operators must only deploy this release on networks where all other SV nodes run Splice 0.5.10 or higher! Otherwise the sequencers will disagree on the traffic cost of confirmation responses and fork the ledger…

A newer release in the 0.5 line: Splice 0.5.18
Newest Splice: Splice 0.9.4

Open the release notes (opens in a new tab)docs.canton.network

SV node operators must only deploy this release on networks where all other SV nodes run Splice 0.5.10 or higher! Otherwise the sequencers will disagree on the traffic cost of confirmation responses and fork the ledger.The reason for this is that sequencer nodes running code prior to Splice 0.5.10 do not parse the new dynamic domain parameter that is used to perform a coordinated update of the traffic cost of confirmation responses across all SV nodes. These sequencers would thus ignore the change in the traffic cost computation.Validator node operators are not affected by this requirement, as the change only affects sequencer nodes.

SV app
- Add a new config parameter to control whether the SV app should enable free confirmation responses in the dynamic domain parameters. This new parameter is set to true by default, so that no manual config changes by SV operators are required to enable free confirmation responses on networks running this version of Splice. This change implements Increment 1 “Make confirmation responses free using the heuristic implementation” from CIP-104 - Traffic-Based App Rewards.
Validator and SV app
- The splice-util-batched-markers dar is now uploaded automatically.
Daml
- Optimize the number of views in the automation run by the SV app to convert FeaturedAppActivityMarker contracts into AppRewardCoupon contracts.
- Support weighting of featured app markers. This can be used through the new BatchedMarkersProxy_CreateMarkersV2 or FeaturedAppRight_CreateActivityMarkerV2 choice in the new splice-api-featured-app-v2 package. Note that this is intended for creating markers proportional to the burn of applications not for increasing the weight of markers created from regular app activity e.g. to increase the weight of markers created as part of a transfer. Refer to the tokenomics committee for detailed guidelines on usage. This requires a Daml upgrade to
  
  name version
  amulet 0.1.16
  amuletNameService 0.1.17
  dsoGovernance 0.1.22
  validatorLifecycle 0.1.6
  wallet 0.1.17
  walletPayments 0.1.16

name	version
amulet	0.1.16
amuletNameService	0.1.17
dsoGovernance	0.1.22
validatorLifecycle	0.1.6
wallet	0.1.17
walletPayments	0.1.16

← All Splice releases