CCPEDIAby Unity Nodes
ReleasesSplice 0.4.0

Splice 0.4.0

Digital AssetSplice

Upgrade to Canton 3.3: This upgrade requires a Hard Synchronizer migration and cannot be applied through a regular helm upgrade. For details refer to the CIP draft. Implement CIP 47 and CIP 56. This release includes a…

Open the release notes (opens in a new tab)docs.canton.network
  • Upgrade to Canton 3.3: This upgrade requires a Hard Synchronizer migration and cannot be applied through a regular helm upgrade. For details refer to the CIP draft.
  • Daml
    • Implement CIP 47 and CIP 56. This requires an upgrade to the following Daml versions:
      nameversion
      amulet0.1.9
      amuletNameService0.1.9
      dsoGovernance0.1.12
      validatorLifecycle0.1.3
      wallet0.1.9
      walletPayments0.1.9
  • Deployment
    • This release includes a change to the database schema that will trigger a short database migration. On DevNet and MainNet, the migration is expected to take 2min for scan applications, and much less for validator and sv applications.
    • Add jemalloc into the docker images. This is not enabled by default but allows for easier testing. Thanks to Stanislav German-Evtushenko for contributing this in https://github.com/canton-network/splice/pull/318
  • Validator
    • Fix an issue where the automation for completing TransferCommand failed if the provider had a featured app right.
    • Fixes and stability improvements for the validator re-onboarding flow. Among other things:
      • Recovery of standard local parties is now automatically possible even if the validator is hosting external parties.
      • It is now possible to force the recovery attempt for a party that was skipped during the fully automated recovery flow.
    • Improve the error message when trying to use the wallet outside of localhost or https. Thanks to Stephane Loeuillet for contributing this in https://github.com/canton-network/splice/pull/322.
  • Scan
    • Scan now implements some Token Standard endpoints that are under the /registry path. https://scan.sv.<YOUR_HOSTNAME>/registry should be routed to /registry at port 5012 in service scan-app in the sv namespace, the same way that /api/scan already is.
← All Splice releases