Corda Enterprise release notes

Corda Enterprise 4.8 release overview

This release introduces a number of new features and enhancements, and fixes for known issues from previous releases.

Just as prior releases have brought with them commitments to wire and API stability, Corda Enterprise 4.8 comes with those same guarantees.

States and apps valid in Corda 3.0 and above are usable in Corda 4.8 and Corda Enterprise 4.8.

The main new features and enhancements in Corda Enterprise 4.8 are listed below:

Long-term support (LTS) release

As part of our first major Corda release for 2021, Corda 4.8 and Corda Enterprise 4.8 are our long-term support (LTS) platform versions, which bring improvements and stability fixes that continue to enhance the maturity of the platform as a whole.

The LTS status of this release provides an extra 6 months to our previous support period, providing Corda customers extra time to plan for the next upgrade.

New features and enhancements

Notary database support updates

The JPA notary now supports Oracle DB version 19c. This database is supported until April 30th, 2027, providing long-term support for this Corda release.

Azure Managed Identities authentication

When using an Azure Key Vault HSM with Corda Enterprise, you can now use an existing Azure Managed Identities service as authentication. See Using an HSM with Corda Enterprise for more information.

Time-window metrics gathering

Timer and histogram metrics can now be configured to use time-window data gathering. Time-window data gathering collects all data points for a given time window, allowing outlying data points to be properly represented.

See Node metrics for more information.

Additional notary metrics

Two new metrics have been added that can be used to help calculate notary latency. The StartupQueueTime and BatchSignLatency metrics can be used to help when calculating notary latency and assessing notary worker performance across a notary cluster.

  • The StartupQueueTime represents the time a flow has been queued before starting, in milliseconds.
  • The BatchSignLatency metric represents the time elapsed during a batch signature in milliseconds.

See Monitoring Notary Latency for more information.

Confidential identity key on HSMs

Platform version change

The platform version of Corda 4.8 has been bumped up from 9 to 10.

For more information about platform versions, see Versioning.

Fixed issues

  • We have fixed a security issue that affects notary systems that use the JPA notary implementation in an HA configuration, and when the notary backing database has been set up using the Corda database management tool. The new version of the Corda database management tool must be re-run for the fix to take effect.
  • We have fixed several issues that caused memory leaks. As a result, we have added a new node configuration field - enableURLConnectionCache - and we have modified the attachmentClassLoaderCacheSize node configuration field. See the node configuration fields page for details.
  • We have fixed an issue where the node would be unable to resolve transaction chains that contained states or contracts that it did not relate to installed CorDapps.
  • We have fixed an issue that caused flow state, invocation source, and suspension source filters to break in the node GUI.
  • We have fixed an issue that caused transaction verification to be performed outside of the attachments class loader.
  • We have fixed an issue where HA utilities did not log a message stating that the master key was not needed when using a native mode HSM.
  • We have fixed an issue where HA utilities did not log information about the freshIdentitiesConfiguration.
  • We have fixed an issue where a log message incorrectly stated that a confidential identity key was created.
  • We have fixed an issue that could cause a node to hang if shut down using SIGTERM.
  • We have fixed an issue where the attachment presence cache contained the attachment contents.
  • We have fixed an issue where the Corda Firewall threw an error when retrieving version information.
  • We have fixed an issue where the HA utilities created erroneous logs when using confidential identities.

Known issues

  • When using the Oracle 12c database, the JDBC driver can hang when it is blocked by an empty entropy pool at random times.