Splice 0.6.4
Validators must upgrade to 0.6.4 or newer before any LSU. If you don’t upgrade in time, your node will be unable to receive or submit transactions until you upgrade. The wallet and CNS UIs now support optionally…
- A newer release in the 0.6 line: Splice 0.6.14
- Newest Splice: Splice 0.9.4
Open the release notes (opens in a new tab)docs.canton.network
-
Wallet & CNS UIs
- The wallet and CNS UIs now support optionally configuring the requested OAuth token scope, to support IAM providers that require doing so.
-
Scan UI
- Bring back the governance page that was removed in release 0.5.18.
-
Wallet UI
- Fix a corner case in the wallet Allocations UI where invalid values would be passed to
/v0/allocationswhen creating allocations from allocation requests. This could manifest as a browser error when clickingAccepton an allocation request.
- Fix a corner case in the wallet Allocations UI where invalid values would be passed to
-
SV app
-
SV participants now use the public sequencer URL instead of the internal one to connect to their sequencer. This avoids some redundant reconnects around LSUs where the participant LSU automation would set the public URL while the SV app would set the internal one.
The prior behavior can be recovered by setting
canton.sv-apps.sv.use-internal-sequencer-api = truethrough anADDITIONAL_CONFIGenvironment variable. LSUs will still work but be slightly slower due to extra reconnects.
-
SV participants now use the public sequencer URL instead of the internal one to connect to their sequencer. This avoids some redundant reconnects around LSUs where the participant LSU automation would set the public URL while the SV app would set the internal one.
The prior behavior can be recovered by setting
-
SV deployment
- Splice Info endpoint now includes
/runtime/status.jsonwhich provides status of core components (sv, scan and mediator at this moment) refreshed every 60 seconds.splice-infohelm chart now requiresruntimeDetails.migrationIdto be specified.
- Splice Info endpoint now includes
-
Scan
-
The app activity records computation has been modified to exclude the transactions submitted by SVs, as the SVs don’t burn traffic and transactions submitted by them should not generate traffic-based app rewards as specified in CIP-0104.
The data provided by the experimental
app_activity_recordsfield ofGET /v0/events/{update-id}andPOST /v0/eventsendpoints prior to this release may have attributed app-activity to SV submitted transactions, and such app activity records should be considered incorrect. App activity records data provided for other transactions is valid. Neither endpoint will provideapp_activity_recordsfor events prior to this release. Internally, theapp_activity_record_storetable will be truncated to remove the records computed with the earlier logic on initial launch.
-
The app activity records computation has been modified to exclude the transactions submitted by SVs, as the SVs don’t burn traffic and transactions submitted by them should not generate traffic-based app rewards as specified in CIP-0104.
The data provided by the experimental