Skip to content

Corda 3.2
Compare
Choose a tag to compare
@fenryka fenryka released this 20 Jul 16:51
· 2625 commits to master since this release
release-V3.2
5ae8325

Corda 3.2

As we see more Corda deployments in production this minor release of the open source platform brings
several fixes that make it easier for a node to join Corda networks broader than those used when
operating as part of an internal testing deployment. This will ensure Corda nodes will be free to interact
with upcoming network offerings from R3 and others who may make broad-access Corda networks available.

The Corda Network Builder

To make it easier to create more dynamic, flexible, networks for testing and deployment,
with the 3.2 release of Corda we are shipping a graphical network bootstrapping tool
to facilitate the simple creation of more dynamic ad hoc dev-mode environments.

Using a graphical interface you can dynamically create and alter Corda test networks, adding
nodes and CorDapps with the click of a button! Additionally, you can leverage its integration
with Azure cloud services for remote hosting of Nodes and Docker instances for local testing.

Split Compatibility Zone

Prior to this release compatibility zone membership was denoted with a single configuration setting

compatibilityZoneURL : "http://<host>(:<port>)"

That would indicate both the location of the Doorman service the node should use for registration
of its identity as well as the Network Map service where it would publish its signed Node Info and
retrieve the Network Map.

Compatibility Zones can now, however, be configured with the two disparate services, Doorman and
Network Map, running on different URLs. If the compatibility zone your node is connecting to
is configured in this manner, the new configuration looks as follows.

networkServices {
    doormanURL: "http://<host>(:<port>)"
    networkMapURL: "http://<host>(:<port>)"
}

NOTE: The compatibilityZoneURL setting should be considered deprecated in favor of the new networkServices settings group.

The Blob Inspector

The blob inspector brings the ability to unpack serialized Corda blobs at the
command line, giving a human-readable interpretation of the encoded date.

NOTE: This tool has been shipped as a separate Jar previously. We are now including it as part of an official release.

Documentation on its use can be found here :doc:blob-inspector

The Event Horizon

One part of joining a node to a Corda network is agreeing to the rules that govern that network as set out
by the network operator. A node's membership of a network is communicated to other nodes through the network
map, the service to which the node will have published its Node Info, and through which it receives the
set of NodeInfos currently present on the network. Membership of that list is a finite thing determined by
the network operator.

Periodically a node will republish its NodeInfo to the Network Map service. The Network Map uses this as a
heartbeat to determine the status of nodes registered with it. Those that don't "beep" within the
determined interval are removed from the list of registered nodes. The Event Horizon network parameter
sets the upper limit within which a node must respond or be considered inactive.

.. important:: This does not mean a node is unregistered from the Doorman, only that its NodeInfo is
removed from the Network Map. Should the node come back online it will be re-added to the published
set of NodeInfos

Issues Fixed

  • Update Jolokia to a more secure version [CORDA-1744]
  • Add the Blob Inspector [CORDA-1709]
  • Add support for the Event Horizon Network Parameter [CORDA-866]
  • Add the Network Bootstrapper [CORDA-1717]
  • Fixes for the finance CordApp[CORDA-1711]
  • Allow Doorman and NetworkMap to be configured independently [CORDA-1510]
  • Serialization fix for generics when evolving a class [CORDA-1530]
  • Correct typo in an internal database table name [CORDA-1499] and [CORDA-1804]
  • Hibernate session not flushed before handing over raw JDBC session to user code [CORDA-1548]
  • Fix Postgres db bloat issue [CORDA-1812]
  • Roll back flow transaction on exception [CORDA-1790]
Assets 2