CCPEDIAby Unity Nodes
ReleasesSplice 0.5.18

Splice 0.5.18

Digital AssetSplice

A new optional configuration map additionalPackagesToUnvet to unvet additional supported packages was added in the SV app configuration. This is only aimed as a security measure to add the ability to downgrade to…

  • The latest release in the 0.5 line.
  • Newest Splice: Splice 0.9.4
Open the release notes (opens in a new tab)docs.canton.network
  • SV App
    • A new optional configuration map additionalPackagesToUnvet to unvet additional supported packages was added in the SV app configuration. This is only aimed as a security measure to add the ability to downgrade to previous versions in case of major issues or to prevent corrupted and unsecured packages from being used. More information about this new configuration can be found in the Unvet insecure package versions guide.
  • Deployment
    • We’ve added support for the Stakater Reloader annotation, which performs a rolling restart of pods when their referenced Secrets or ConfigMaps change. The annotation is included by default in all Splice Helm charts. You can disable it by setting enableReloader to false in your Helm values file. Reloader must be installed separately; if it is not present, the annotation is harmless and will be ignored. See also the new deployment tips in the Validator and SV Helm guides.
  • Scan
    • The following tabs and features have been removed from Scan UI. Their corresponding API endpoints are still available, yet deprecated, and will be removed soon. Users are strongly advised to migrate to non-deprecated API endpoints as soon as possible.
      • Canton Coin Activity
        • Recent activity list, and all leaderboards
        • Total app & validator rewards
        • The round as-of which the content has been computed (no round-based data is listed any more)
        • The tab has been renamed “Canton Coin Configuration”
      • Governance
        • Completely removed
      • Validators
        • Completely removed
    • Improve CPU usage of update and event history.
    • Scan now ingests and serves app activity records for traffic-based rewards, which delivers Increments 2 and 3 from the CIP-104 incremental roll-out plan. The responses from the /v0/events and /v0/events/{update_id} endpoints now include the traffic_summary (schema) and app_activity_records (schema) fields.
    These new fields enable the Canton Network community to start validating the traffic-based rewards model and to prepare for the full roll-out of CIP-0104 in the future.Network explorer operators: consider ingesting traffic summaries and app activity records in your network explorer apps together with the mediator verdicts and use them to provide both per-transaction and per-round previews of the expected traffic-based app rewards when CIP-0104 goes live.App developers: review the app activity records for your app to understand the impact of traffic-based app rewards on your app. Keep in mind that the rewards depend on the exact transaction structure of your app, which might change when you stop creating FeaturedAppActivityMarker contracts in your transactions. Traffic-based app rewards also depend on the featured app status of counter-parties in your transactions. Expected rewards can therefore differ between DevNet, TestNet and MainNet because different apps are featured.The new fields are marked as experimental in the API specification, as the validation might show that changes are required. Most likely that will though not be the case.
  • Canton
    • A cause of frequent SEQUENCER_SUBMISSION_REQUEST_REFUSED errors when using BFT sequencer connections and request amplification has been addressed. Set canton.sequencers.sequencer.sequencer-client.amplify-on-max-sequencing-time-too-far to false to restore previous behavior.
      • The SequencerService.sendAsync gRPC service will now return SEQUENCER_MAX_SEQUENCING_TIME_TOO_FAR instead of SEQUENCER_SUBMISSION_REQUEST_REFUSED for transactions with a maxSequencingTime too far in the future from the sequencer view (usually when sequencer is catching up and is behind on processing). This is a breaking API change.
    • The Ledger JSON API v2/package-vetting endpoint has been deprecated in favor of two new endpoints: v2/package-vetting/list and v2/package-vetting/update. These new endpoints are equivalent in functionality, but more compliant with HTTP specifications and tools.
← All Splice releases