Release of Daml 2.8.3


This is a maintenance release that addresses several issues.

What’s New

Several software dependencies have been updated to prevent security vulnerabilities.  They are:  Logback (v1.4.14), Amqp (v5.18), netty (v4.1.100), and GRPC (v1.60).

It was uncovered that an AWS RDS failover would not retry if there was a read-only transaction exception.  This has been fixed and a test added to prevent regressions.

For the Trigger Service, AllInDar actually means "all templates known to the trigger service" which was confusing to users.  So, to avoid confusion, AllInDar has been deprecated in favor of AllTemplates.

Visual Studio Code has an extension for Daml development. A recent VSCode update changed to using case-insensitive extension names which impacted the  `daml studio –replace=always` command. Daml Assistant now deals with the case-insensitive extension names properly. 

Download and Installation

The Daml 2.8.3 SDK has been released. You can install it using the command:  daml install 2.8.3.

The table below lists how you can download Daml Enterprise or individual components.

Daml Enterprise v2.8.3


File download

Container Image




Canton for Daml Enterprise

Standalone JAR file

Daml Finance

GitHub Page



Standalone JAR file

Trigger Service

Standalone JAR file

OAuth 2.0 middleware (Open-Source)

GitHub Page

Participant Query Store

Standalone JAR file

Trigger Runner

Standalone JAR file

Daml Script

Standalone JAR file

If you are using Oracle JVM and testing security provider signatures, note that the Canton JAR file embeds the Bouncy Castle provider as a dependency. To enable the JVM to verify the signature, put the bcprov JAR on the classpath before the Canton standalone JAR.  For example:

java -cp bcprov-jdk15on-1.70.jar:canton-with-drivers-2.8.3-all.jar com.digitalasset.canton.CantonEnterpriseApp

Note: These Docker images are designed to be suitable for production use, with minimal size and attack surface. Minimal images can sometimes make debugging difficult (e.g. no shell in the containers). For convenience, we provide “debug” versions of each of the above images, which you can access by appending “-debug” to the image tag (e.g.