Summary

This is a maintenance release that addresses several issues.

What’s New

• Updated Daml Studio to work with Visual Studio Code version 1.92 and above.
• Fixed a bug in daml-script where submission by parties imported via getUser were targeting the wrong participant in a multi-participant setting.
• A participant node could crash due to an exercise of a retroactive interface failing because the Daml engine does not explicitly request the interface package. It is possible that this can lead to a ledger fork as participants come to different conclusions.

Download and Installation

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

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

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.10-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. digitalasset-docker.jfrog.io/http-json:2.8.10-debug).