Previous Releases

These releases are for prior versions of the Utility. They should no longer be installed on any node connected to DevNet, TestNet or MainNet, and are included only for posterity.

0.8.6

  • Fixed a WebSocket bug in the UI.

  • Corrected the instrument configuration endpoint path.

  • Improved retry logic for handling contention errors in the automation fee trigger.

0.8.5

  • Added support for creating app reward configurations in the Utility UI.

  • Added WebSocket support for the JSON API in the UI. Users can enable it via the Settings page of the UI.

0.8.4

This release was skipped.

0.8.3

NOTE: The darsyncer image has been renamed to utilities-darsyncer-client (it was formerly called utilities-darsyncer). If you are using docker-compose, you will need to update your installation. If you are using the Helm charts, this is handled transparently.

  • Improved token-standard endpoints to ensure forward compatibility with future Daml models.

  • Add support for using the utilities helm chart as a subchart.

  • The DAR uploading process in the helm charts is more efficient about which DARs it chooses to upload.

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.

0.7.8

UI change to filter all contracts based on the Utility Operator.

The DAR files are unchanged from the previous version.

0.7.6

This is a technical release which allows the Utility operator to take control of the billing frequency by setting a minimum billing period for all credentials.

The DAR files and Utility UI are unchanged from the previous version.

0.7.5

This version includes fixes to the UI and the Top Up app. The DAR files are unchanged from the previous version.

UI:

  • expose button to withdraw an Allocation

  • fix rendering of credential billings and commercial agreements in case of long-running queries

Top Up app:

  • make it auth provider agnostic

0.7.4

This is a technical release required as part of the work on Helm Charts for the Utilities.

The DAR files and the UI are unchanged from the previous version.

0.7.3

This version fixes a UI bug where certain operations cannot be performed if the counterparty did not vet the utility-commercials-v0 package.

Moreover, the UI does not poll for the utility-collateral-app package, which logged a noisy error in the previous UI version.

0.7.2

This is a technical release required as part of the work on Helm Charts for the Utilities.

The DAR files and the UI are unchanged from the previous version.

0.7.1

This version fixes a bug that was surfaced on the 0.7.0 UI and Top Up app.

The DAR files are unchanged.

0.7.0

This version includes the following improvements to the Utilities:

  • Make the Utilities compatible with splice-0.1.9

  • Enable cross-provider compatibility, meaning that tokens can be transferred between owners onboarded by different providers

  • Integrating the token standard to enable the settlement of Delivery-versus-Payment workflows (DvPs)

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

  • utility-commercials-v0-0.2.0.dar

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

  • utility-registry-app-v0-0.2.0

We now offer two mechanisms for configuring your operator party:

0.6.1

This version introduces two improvements to the Utility UI:

  • Optimize polling frequency: refresh active contract queries only when the ledger end has advanced

  • Fixing a bug which removed the ability to accept commercial agreements if CurrentVersion was not set

Users can deploy this release of the Utility directly together with the update to Canton 3.3. There is no need to apply 0.6.0 before upgrading to 0.6.1.

0.6.0

This version updates the Utility UI for compatibility with the latest Canton/Daml 3.3.

0.6.0 can be applied to Test Net from June, 11th 2025, and then to Main Net from June, 25th 2025 in line with the Canton/Daml 3.3 rollout schedule listed here

The UI is available here

The Utility Daml models are unchanged from the previous version.

The Utility UI requires Canton/Daml version 3.3 or later.

0.5.3

This release introduces a new application that automatically tops up either CredentialBilling or CommercialAgreement contracts when their locked deposits fall below a configurable threshold. The application can be deployed as a native Kubernetes cron job or as a long-running container, depending on your infrastructure needs.

  • Setup documentation: here

  • Application image: here

The UI has been updated - UI image: here

This version includes a bugfix to remove refetch interval for ledger offset.

This version is fully compatible with existing versions of the application.

0.5.1

This version introduces a new feature to the “Commercial Agreement” component, facilitating base fee payments. The following additional DARS should be installed on your Participant:

  • utility-commercials-v0-0.1.0.dar

The bundle files containing the DAR packages for the Utility are available in JFrog. Download version 0.5.1 of the bundle. The UI is available here

The release is compatible with existing versions of the application.

0.4.1

This version introduces a new component called “Commercial Agreement” and includes an update to the Credential Utility.

The billing processing for paid credentials incurs a service fee. To use this service provided by Digital Asset, a Commercial Agreement must be established. This agreement, issued by Digital Asset, can be accepted via the user interface and outlines the service fee terms.

Additionally, the credential billing process includes an on-ledger accounting feature for rewards that can be used in combination with a Reward Share component (not released yet). In order to support external signing, the CredentialOffer_AcceptFree and CredentialOffer_AcceptPaid will now set validFrom = None.

The new functionality is exposed through the User Interface. In addition, the User Interface includes numerous improvements to enhance usability and user experience.

The following additional DARS should be installed on your Participant Node:

  • utility-credential-app-v0-0.2.1

  • utility-commercials-v0-0.0.1

The bundle files containing the DAR packages for the Utility are available in JFrog. Download version 0.4.1 of the bundle. The UI is available here

The release is compatible with existing versions of the application.

0.3.5

This version introduces a fix to the Utility UI to ensure compatibility with the latest Daml models for Splice (specifically splice-amulet-0.1.6).

The Utility Daml models are unchanged from the previous version.

This version can be deployed by users who are on 0.3.4 at any time, as it does not require synchronisation.

0.3.4

This version introduces an update to the Utility Daml models for the Registry component.

An EnforcementService contract is introduced which, when setup between a holder and a registrar, allows the registrar to transfer the holder’s assets to another receiver under certain conditions.

A RegistrarConfiguration contract is introduced to define the required credentials in order to enter into an EnforcementService.

The Utility UI exposes these new features to users.

The following DARS must be installed in order to proceed with the release:

  • utility-credential-app-v0-0.1.0

  • utility-registry-app-v0-0.0.1

  • utility-registry-app-v0-0.1.0

  • utility-version-v0-0.0.1

The bundle files containing the DAR packages for the Utility are available in JFrog. Download version 0.3.4 of the bundle.

Rollout Schedule

The following schedule outlines the planned updates for each environment:

Environment

Rollout Date

Dev Net

15th Nov

Test Net

28th Nov

Main Net

9th Dec

All client nodes must be updated within this time frame to ensure compatibility and minimize disruptions.

Package Versions

After the rollout, all environments will be running on:

Credential App

Registry App

Frontend Image

Version

0.1.0

0.1.0

0.3.3