CCPEDIAby Unity Nodes
ReleasesSplice 0.5.14

Splice 0.5.14

Digital AssetSplice

Increase default retention parameters of the session encryption keys cache. Most notably, increase the lifetime of session encryption keys from 10 minutes to 1 hour, to improve performance and reduce (KMS) costs…

Open the release notes (opens in a new tab)docs.canton.network
  • Participant
    • Increase default retention parameters of the session encryption keys cache. Most notably, increase the lifetime of session encryption keys from 10 minutes to 1 hour, to improve performance and reduce (KMS) costs throughout the network. This change has no practical security implication for participants that are not using an external KMS: in this case the main (asymmetric) encryption keys are usually already available in memory (in addition to being stored inside the participant database). We encourage operators of KMS-enabled participants to review the updated sections on KMS usage for validator participants and SV participants for more pointers about the security impact of session key caching and ways to tweak the relevant parameters to individual needs.
  • SV app
    • Improve the automation for converting featured app activity markers to handle batches of markers for nodes that have not vetted the same version of the amulet package.
  • Validator app
    • Prevent secrets from being logged at DEBUG level when the environment variable SPLICE_APP_DARS or .appDars in Helm were set.
  • Canton
    • Fix issue where sequencer startup could take more than 10 minutes.
    • APIs:
      • BREAKING The
        • /v2/updates HTTP POST and websocket GET endpoints
        • /v2/updates/flats HTTP POST and websocket GET endpoints
        were incorrectly retuning LedgerEffects events (i.e., CreatedEvent and ExercisedEvent). They are now corrected to return AcsDelta (flat) events (i.e., CreatedEvent and ArchivedEvent).
      • GetUpdatesRequest.updateFormat now appears marked as required in the OpenAPI/AsyncAPI specs even though it was previously optional. This is a specification fix to align with the actual behavior of the API, which requires this field. If your client code was previously omitting this field, you will need to update it to include a valid value.
← All Splice releases