Summary

This is a maintenance release that addresses several issues.

What’s New

The Besu solidity driver code had a race condition which, in rare circumstances, could cause the same transaction to be sequenced twice (with two different nonces), This race condition has been closed.  

The participant node can gracefully handle repeatedly sequenced transactions since the v2.7.0 release.  Such transactions are committed only once. However, due to other race conditions in the implementation, the data stored on the participant node may become inconsistent for such a transaction. This inconsistency is detected upon the next attempt to reconnect to the domain and alerted. The race conditions are now closed.

Installation or Download

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

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

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