Splice 0.6.5
Validators must upgrade to 0.6.5 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. Fix LSU issue where participant restarts past freeze…
- 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
-
Canton
- Fix LSU issue where participant restarts past freeze time could lead to losing the LSU announcement. Validators must update to consume this bugfix before any LSU.
-
Observability
- The release bundle now ships a separate Grafana dashboard folder
validator-grafana-dashboards/for Validator operators.
- The release bundle now ships a separate Grafana dashboard folder
-
canton.scan-apps.scan-app.activity-ingestion-user-versionconfiguration setting has been added to control the activity record ingestion version for the purpose of recovering from unexpected operational issues. Incrementing this value causes the Scan app to record a new app activity record completeness lower bound. Reward accounting excludes rounds before this boundary, even though their activity records are retained. Thus bumping the user version has the same effect as reinitializing the app activity record computation from the time of the bump onwards. See the SV Operations docs for more details. -
Scan app
- The
app_activity_record_storetable has been modified to improve DB performance. The corresponding DB migration truncates the existing data in this table which has been ingested since the0.5.18release, which is OK as we are still in the preview phase of CIP-0104. The downstream reward-accounting tables are also cleared as part of this change.
- The
-
SV app
- Support a list of
additionalLegacysynchronizers for the case where more than one legacy synchronizer must be kept alive at a given point.
- Support a list of
-
Validator app
-
Added support for
bft-customscan and sequencer configurations in Docker Compose based validator deployment. - Stop recording update history. This data was never exposed beyond undocumented SQL tables so there should be no effect other than the database growing at a slower rate. If you need to access data for any of the parties on your node use the ledger API.
-
Added support for
-
SV deployment
- The sequencer and mediator helm charts are now setting the same
fsGroup,runAsUser, andrunAsGroupin the security context of the pods as the participant, validator app, and sv app charts.
- The sequencer and mediator helm charts are now setting the same
-
UI
- offline_access scope has been removed from the default requested scopes for OAuth tokens in the CN UIs. When a token expires, users will now be prompted to log in again instead of the UI refreshing the token.