Corda 5 Developer Preview 2 is now available.

API stability guarantees

Corda maintains the stability of specific APIs. APIs are categorized as:

  • Public APIs, which are APIs/application binary interfaces (ABIs) that are backwards compatible. See public API for more information.
  • Non-public APIs. These APIs are not guaranteed to be backwards compatible. See non-public API (experimental) for more information.

Public API

The following modules form part of Corda’s public API. These will be backwards compatible for future releases, unless an incompatible change is required for security reasons:

  • Core (net.corda.core): Core Corda libraries such as crypto functions, types for Corda’s building blocks (such as states, contracts, transactions, and attachments), and some interfaces for nodes and protocols.
  • Client RPC (net.corda.client.rpc).
  • Client Jackson (net.corda.client.jackson): JavaScript Object Notation (JSON) support for client applications.
  • DSL Test Utils (net.corda.testing.dsl): a simple domain-specific language (DSL) for building pseudo-transactions (this is not the same as the wire protocol) for testing purposes.
  • Test Node Driver (net.corda.testing.node, net.corda.testing.driver): test utilities to run nodes programmatically.
  • Test Utils (net.corda.testing.core): generic test utilities.
  • Http Test Utils (net.corda.testing.http): a small set of utilities for making HTTP calls, aimed at demos and tests.
  • Dummy Contracts (net.corda.testing.contracts): dummy state and contracts for testing purposes.
  • Mock Services (net.corda.testing.services): mock service implementations for testing purposes.

The Tokens SDK (com.r3.corda.lib.tokens) available in the Tokens GitHub repository also has a stable API.

Non-public API (experimental)

Corda does not guarantee backwards compatibility for:

  • Incubating modules (where possible, disruption to developers will be minimized). See Corda incubating modules for more information.
  • The finance module: a legacy module. Use the Tokens SDK com.r3.corda.lib.tokens (available in the Tokens GitHub repository instead.

Corda incubating modules

Incubating modules are under development, and are subject to change until they graduate to the public API.

  • net.corda.confidential: experimental support for confidential identities on the ledger.
  • net.corda.client.jfx: support for Java FX UI.
  • net.corda.client.mock: client mock utilities.
  • Cordformation: Gradle integration plugins.

Corda internal modules

Some public modules may depend on internal modules, so be careful not to rely on these transitive dependencies. In particular, the testing modules depend on the node module, and so you may end having the node in your test classpath.

The @DoNotImplement annotation

Certain interfaces and abstract classes within the Corda API have been annotated as @DoNotImplement. Removal or modification of these classes’ existing functionality will be avoided. However, the annotation is a warning that they may be extended in future versions of Corda. You should only use these classes “as is”, and not attempt to extend or implement any of them.

This annotation is inherited by subclasses and sub-interfaces.

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.