0.8 Release Line

If you are using the Utilities on DevNet or TestNet, you should have version 0.8.2 installed.

  • Migrate your utilities node on MainNet on 2025 Oct 1.

0.8.2

  • Improved registry daml models for reducing transaction cost and workaround external signing limitation.

  • Added Helm chart values for configuring the json api query limit in UI.

  • Added Helm chart values for configuring audience to darsyncer.

  • Fixed UI to remove unlock button on locked holdings.

0.8.1

  • Fixed credential metric for billing overdue time and deposit amount.

  • Fixed UI to correctly display holder service contracts.

  • Added registry metric for number of dead tasks.

  • Added UI for managing unresponsive parties.

  • Fixed a problem where the automatic DAR-uploading process assumed an auth audience of https://canton.network.global.

The DAR files are unchanged from the previous version.

0.8.0

This release introduces

Setup instructions

Installation instructions into a Kubernetes cluster have been simplified, and you can now install the Utilities using Helm. Helm charts are now the recommended way to the install the Utilities.

Utility UI

Asset holders no longer need to establish a HolderService contract with a provider in order to be onboarded to the Registry module.

In addition to that, we modified the rendering of large tables for a better user experience.

This version of the UI requires connectivity to the Utility operator backend, which shoudl be configured upon deployment.

Registry module

This release introduces full token standard support for Utility tokens managed through the Registry module.

Moreover, featured providers can create activity markers upon the execution of token-standard asset transfers / allocations.

Finally, we are going to deprecate the standalone Lock and Unlock workflows in an upcoming release. These are currently unused and should be ported to the token standard.

Credential module and commercial agreement

New Daml packages are introduced to update the dependency on splice-amulet to version 0.1.13.

Collateral module

The collateral module lets users transfer Utility tokens for collateral management purposes, keeping an on-ledger record of collateral posted to a counterparty.

While it currently only supports Utility tokens only, it builds on the Token Standard, which makes it easily extensible to other token-standard-compliant tokens.

Package versions

The following additional DARS should be installed on your validator node.

For users of the credential module:

  • utility-commercials-v0-0.2.1.dar

  • utility-credential-app-v0-0.2.3.dar

Additionally, for users of the registry module

  • utility-registry-app-v0-0.3.0.dar

Finally, for those who wish to use the Collateral App

  • utility-collateral-app-v1-1.0.0.dar

Note

When using the Helm Charts to install the Utility, all Utility DARS will be automatically installed. You no longer need to upload DARs manually.