Release of Daml 2.7.8


This is a maintenance release that addresses several issues.

What’s New

There are several improvements and bug fixes in this release.  

The Visual Studio Code behavior changed and introduced a bug in the Daml extension where multiple Daml extensions could be started and interfere with each other.  This has been fixed.

Fixed a rare race condition where the JSON API could return archived contracts on the very first query of a new (to the JSON API) party.

Backport a fix to ensure the participant completes a failover with a domain reconnect in the presence of faults.

Following the principle of ‘fail fast’, the participant node will now halt if an unexpected event occurs that it cannot recover from.  Then the supervisor system can restart the participant node as a recovery mechanism.  

Installation or Download

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

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

Daml Enterprise v2.7.8


File download

Docker 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, you should note that the provided Canton JAR file embeds the BouncyCastle Provider as a dependency. To enable the JVM to verify the signature, you need to 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.7.8-all.jar com.digitalasset.canton.CantonEnterpriseApp

Note: These Docker images are designed to be minimal in size and attack surface, and are thus suitable for production use. 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.