Corda and Corda Enterprise compatibility

Corda Enterprise Edition 4.0 guarantees the wire stability and compatibility baseline introduced in Corda open source 3.0 is maintained with future versions of Corda Enterprise.

Corda Enterprise Edition 4.0 can be used in mixed-version/mixed-distribution networks seamlessly, transacting with nodes running on a minimum platform version of 4.

See versioning for further information.

Compatibility with Corda Enterprise Edition 4.0Corda open source 4.xEnterprise Corda 3.xCorda open source 3.x
API compatibility, CorDapps developed for this Corda version can be compiled and run on Corda Enterprise Edition 4.0 nodes.YesYesYes
Binary compatibility, CorDapps compiled on this Corda version can be run on Corda Enterprise Edition 4.0 nodes.YesYesYes
Network compatibility, nodes running this Corda version can transact with Corda Enterprise Edition 4.0 nodes.YesYesYes
RPC compatibility, a client application developed for this Corda version can interact via RPC with a CorDapp running on a Corda Enterprise Edition 4.0 node.YesYesNo
Samples and community apps from https://github.com/corda/samples for this Corda version can be compiled and run on Corda Enterprise Edition 4.0 nodes.YesYesYes

You should also be aware of the following:

  • Corda Enterprise Edition 4.0 nodes can transact with nodes running Corda open source 4.0 and future versions, providing the CorDapp is compatible with and between platform versions and distributions.

  • CorDapps written for Corda open source 4.x are API compatible with Corda Enterprise Edition 4.0 and future versions. Developers can switch their IDE to Corda Enterprise Edition 4.0 without making any code changes in their CorDapp.

  • Corda Enterprise Edition 4.0 nodes can run CorDapps developed on and packaged for Corda 4.x, without recompilation. However, due to Corda Enterprise’s advanced features, such as database migration scripting support, we anticipate application developers will build their CorDapp kernels (contracts, states) against Corda open source, and supply two separate workflow JARs (that depend on the same kernel) that are optimized for each distribution. See separation of CorDapp contracts, flows and services for further information.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.