CCPEDIAby Unity Nodes
ReleasesSplice 0.4.7

Splice 0.4.7

Digital AssetSplice

Note: 0.4.6 had a bug and should be skipped in favor of 0.4.7 which fixed a bug where the skipSynchronizerInitialization option could still result in the SV app crashing if its mediator was unreachable which can happen…

Open the release notes (opens in a new tab)docs.canton.network
Note: 0.4.6 had a bug and should be skipped in favor of 0.4.7 which fixed a bug where the skipSynchronizerInitialization option could still result in the SV app crashing if its mediator was unreachable which can happen in certain cases when the sequencer is down.
  • Info (new)
    • important This release contains a new helm chart “splice-info” which is supposed to be installed on all SV nodes and made publicly accessible. The new info endpoint provides:
      • Static information about network, sv, synchronizers, config digests of ip ranges and identities under https://info.sv.<YOUR_HOSTNAME>.
      • Regularly updated (every minute) copy of DSO information under https://info.sv.<YOUR_HOSTNAME>/runtime/dso.json.
      The relevant documentation is updated at sv-helm.
  • Scan
    • Fix bug #1252: populate the token metadata total supply using the aggregates used for closed rounds. The data used corresponds to the data served by the /v0/total-amulet-balance endpoint in app_dev_scan_api for the latest closed round.
    • Fix bug #1280: record_time in Scan API /updates is now right-padded to 6 digits (microseconds).
  • Validator
    • Fix a bug where sweeps through transfer preapprovals failed with a CONTRACT_NOT_FOUND error if the transfer preapproval provider party (usually the validator operator) of the receiver is featured.
  • Splice
    • Building the Splice repo, and running the vast majority of integration tests locally, no longer requires JFrog access.
  • SV
    • Added a domain.skipInitialization helm value that can be set for nodes that have already been onboarded and allows the SV app to start without the sequencer being up. This is useful for long-running sequencer database migrations.
    • Retired deprecated code for old Daml choices AmuletRules_AddFutureAmuletConfigSchedule, AmuletRules_RemoveFutureAmuletConfigSchedule and AmuletRules_UpdateFutureAmuletConfigSchedule
  • Sequencer
    • Fix a sequential scan in a pruning query. This requires a long-running sequencer database migration (expected around an hour on mainnet). Make sure to set domain.skipInitialization on the SV app so the rest of your SV node can continue functioning. The liveness probe of the sequencer will fail during the migration so make sure to temporarily bump livenessProbeInitialDelaySeconds and reduce it back to the default after the migration is complete. Otherwise the liveness probe will kill the sequencer and the migration will never complete.
  • Participant
    • Fix an issue in sequencer BFT connections where the node got completely disconnected on certain failures even if only one sequencer reported those failures.
  • Daml
    • Deprecated Daml choices AmuletRules_AddFutureAmuletConfigSchedule, AmuletRules_RemoveFutureAmuletConfigSchedule and AmuletRules_UpdateFutureAmuletConfigSchedule
      • This requires a Daml upgrade to versions
        nameversion
        amulet0.1.12
        amuletNameService0.1.12
        dsoGovernance0.1.16
        validatorLifecycle0.1.5
        wallet0.1.12
        walletPayments0.1.12
← All Splice releases