Corda 5.0 Beta 3.0 Release Notes

DomainSpecific Change
Cluster AdministrationKubernetes Ingress — The Corda REST worker now supports Kubernetes Ingress. This provides the REST worker with HTTP load balancing and enables optional annotations for additional integration.
CorDapp DevelopmentCorda Gradle plugins — The latest Corda Gradle plugins for Corda 5 is version 7.0.3.

Transaction Builder Send Functionality — The following new functions have been added to UtxoLedgerService:
  • sendAndReceiveTransactionBuilder
  • receiveTransactionBuilder
  • sendUpdatedTransactionBuilder
These functions enable negotiating proposals for transaction components between counterparties. For more information, see the API documentation.
Network OperationSigned Notary Server CPB — The notary server CPB is now signed. For information about building and uploading a CPI using the test key used in this beta release, see Notary Server CPB.

Notary Uniqueness Metrics — Metrics have been added to provide an insight into the uniqueness checking functionality. For a full list of available metrics see Notary Uniqueness Metrics.
DomainSpecific Change
CorDapp DevelopmentcreateTransactionBuilder — The getTransactionBuilder() function in utxoLedgerService mapped to a transactionBuilder property in Kotlin. As of this release, this function has been renamed createTransactionBuilder. Any existing CorDapps that use the ledger must be updated.

Identifying Notaries — The Party class was only used to identify notaries, but its existence suggested an identity model that does not exist in Corda 5.0. Therefore, this class has been removed to clear API space for a proper identity model in a later version. Notaries are identified by MemberX500Name and PublicKey.

During the Beta process, R3 do not guarantee the stability of our user APIs. As a result, seemless upgrade between Beta versions is not supported.

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.