DAR Package Versions

This document outlines the existing versions of DAR packages used within the Utility.

DAR Package Versions

Package Name	Version	Package Id
utility-commercials-v0	0.0.1	43c23473b5b15a090d617fb1e45bc445951200453db607f8a02b214124b937ce
utility-commercials-v0	0.1.0	c40ba02fec104dc33afd60ed8ecfcfe69e8b65682fbfa7e7d4dfd2430a184754
utility-credential-v0	0.0.1	b5d1109eed821be936f295fdd348b0ad609c562311eb0c9d8e4607b747e41636
utility-credential-v0	0.0.2	aa472491115b521b2855f869999b432c57f39fcb41ef68c659d12431f9d8ddd6
utility-credential-app-v0	0.0.2	40830dd0e8381e35998ed2df4716f82a2cc7096ec1e718a8a314e92e8a301890
utility-credential-app-v0	0.1.0	bbe070b706a3b8b18e5a5c108a4e5a9a4145f81d7dcf76c18a51664807377ddd
utility-credential-app-v0	0.2.0	9d57b6f784ebcaa08ab7555e62c4e1c40d54f94d5a50613cdcc543c7c283f167
utility-credential-app-v0	0.2.1	da2af36b42e336c5dff764ce9d445a09a32788626bc18c6cb0c9a52cbf160b68
utility-registry-holding-v0	0.0.1	a83fb2d68f6f220f10da4e92146ff919ca9228fd467441e4c870b904ae9d516f
utility-registry-v0	0.0.1	d0c8b1c2d96c50c26c47e515d07302a55577013582ee65ec5931df4be610bf3b
utility-registry-v0	0.1.0	3b25e7327b493bbe063e89d34fdacbfcc491007e5eabefea3a2919044a28f452
utility-registry-app-v0	0.0.1	5a6f6551759c95a8a1b491c34c4f2b74d74737e2cb070c662639a7ed90280059
utility-registry-app-v0	0.1.0	98cdf68988bc8987227e90905458779957b3687d6a067b2314e7a4c9fe9f33fa
utility-version-v0	0.0.1	42e902610f593c6fb5516d7a7401ad0892dc44507a777ace0a468a5f6c9d3381

Submission packages

Utility clients are expected to exercise choices on a subset of the packages outlined above. We call this subset the Utility submission packages.

Currently the submission packages are

• utility-credential-app-v0

• utility-registry-app-v0

For these packages, the Utility operator determines which specific package id should be used for submission at any given time. This is to avoid that some Utility clients make use of new package versions that counterparticipants might not have uploaded / vetted.

Submission Package Ids for each environment

Environment	Package Name	Package Version	Package Id
DevNet	utility-credential-app-v0	0.1.0	bbe070b706a3b8b18e5a5c108a4e5a9a4145f81d7dcf76c18a51664807377ddd
TestNet	utility-credential-app-v0	0.1.0	bbe070b706a3b8b18e5a5c108a4e5a9a4145f81d7dcf76c18a51664807377ddd
MainNet	utility-credential-app-v0	0.1.0	bbe070b706a3b8b18e5a5c108a4e5a9a4145f81d7dcf76c18a51664807377ddd
DevNet	utility-registry-app-v0	0.1.0	98cdf68988bc8987227e90905458779957b3687d6a067b2314e7a4c9fe9f33fa
TestNet	utility-registry-app-v0	0.1.0	98cdf68988bc8987227e90905458779957b3687d6a067b2314e7a4c9fe9f33fa
MainNet	utility-registry-app-v0	0.0.1	5a6f6551759c95a8a1b491c34c4f2b74d74737e2cb070c662639a7ed90280059

Tooling Packages

To develop against the utility application contracts from Java or JavaScript/TypeScript we recommend to use Daml SDK 3.2.0-snapshot.20241111.13401.0.v7e9180fc and corresponding tools (e.g. codegen):

Tooling Packages

Package	Version	Stack
@daml/types	3.2.0-snapshot.20241111.13401.0.v7e9180fc	JavaScript/TypeScript
@daml/ledger	3.2.0-snapshot.20241111.13401.0.v7e9180fc	JavaScript/TypeScript
bindings-java	3.2.0-snapshot.20241111.13401.0.v7e9180fc	Java

Note

These should be available from public repositories.