Upgrade notes¶
These notes provide helpful instructions to upgrade your Corda Applications (CorDapps) from previous versions, starting from our first public Beta (Milestone 12), to V1.0
General¶
Always remember to update the version identifiers in your project gradle file:
ext.corda_release_version = '1.0.0'
ext.corda_gradle_plugins_version = '1.0.0'
It may be necessary to update the version of major dependencies:
ext.kotlin_version = '1.1.4'
ext.quasar_version = '0.7.9'
Please consult the relevant release notes of the release in question. If not specified, you may assume the versions you are currently using are still in force.
We also strongly recommend cross referencing with the Changelog to confirm changes.
Milestone 14¶
Build¶
MockNetwork has moved.
A new test driver module dependency needs to be including in your project: corda-node-driver. To continue using the mock network for testing, add the following entry to your gradle build file:
testCompile "net.corda:corda-node-driver:$corda_release_version"
Note
you may only need testCompile “net.corda:corda-test-utils:$corda_release_version” if not using the Driver DSL.
Configuration¶
CordaPluginRegistry
has been removed. The one remaining configuration itemcustomizeSerialisation
, which defined a optional whitelist of types for use in object serialization, has been replaced with theSerializationWhitelist
interface which should be implemented to define a list of equivalent whitelisted classes. You will need to rename your services resource file to the new class name: ‘resources/META-INF/services/net.corda.core.node.CordaPluginRegistry’ becomes ‘resources/META-INF/services/net.corda.core.serialization.SerializationWhitelist’ An associated property onMockNode
was renamed fromtestPluginRegistries
totestSerializationWhitelists
. In general, the@CordaSerializable
annotation is the preferred method for whitelisting as described in Object serialization
Missing imports¶
Use the automatic imports feature of IntelliJ to intelligently resolve the new imports.
Missing imports for contract types.
CommercialPaper and Cash are now contained within the finance module, as are associated helpers functions. For example:
import net.corda.contracts.ICommercialPaperState
becomesimport net.corda.finance.contracts.ICommercialPaperState
import net.corda.contracts.asset.sumCashBy
becomesimport net.corda.finance.utils.sumCashBy
import net.corda.core.contracts.DOLLARS
becomesimport net.corda.finance.DOLLARS
import net.corda.core.contracts.issued by
becomesimport net.corda.finance.issued by
import net.corda.contracts.asset.Cash
becomesimport net.corda.finance.contracts.asset.Cash
Missing imports for utility functions.
Many common types and helper methods have been consolidated into net.corda.core.utilities package. For example:
import net.corda.core.crypto.commonName
becomesimport net.corda.core.utilities.commonName
import net.corda.core.crypto.toBase58String
becomesimport net.corda.core.utilities.toBase58String
import net.corda.core.getOrThrow
becomesimport net.corda.core.utilities.getOrThrow
Missing flow imports.
In general all reusable library flows are contained within the core API net.corda.core.flows package. Financial domain library flows are contained within the finance module net.corda.finance.flows package. Other flows that have moved include:
import net.corda.core.flows.ResolveTransactionsFlow
becomesimport net.corda.core.internal.ResolveTransactionsFlow
Core data structures¶
Missing Contract override.
The contract interace attribute
legalContractReference
has been removed, and replaced by the optional annotation@LegalProseReference(uri = "<URI>")
Unresolved reference.
Calls to
AuthenticatedObject
are replaced byCommandWithParties
Overrides nothing:
isRelevant
inLinearState
.Removed the concept of relevancy from
LinearState
. AContractState
‘s relevance to the vault is now resolved internally; the vault will process any transaction from a flow which is not derived from transaction resolution verification. The notion of relevancy is subject to further improvements to enable a developer to control what state the vault thinks are relevant.Calls to
txBuilder.toLedgerTransaction()
now requires a serviceHub parameter.Used by the new Contract Constraints functionality to validate and resolve attachments.
Flow framework¶
Flow session deprecations
FlowLogic
communication has been upgraded to use functions onFlowSession
as the base for communication between nodes.- Calls to
send()
,receive()
andsendAndReceive()
on FlowLogic should be replaced with calls to the function of the same name onFlowSession
. Note that the replacement functions do not take in a destination parameter, as this is defined in the session. - Initiated flows now take in a
FlowSession
instead ofParty
in their constructor. If you need to access the counterparty identity, it is in thecounterparty
property of the flow session.
See
FlowSession
for step by step instructions on porting existing flows to use the new mechanism.- Calls to
FinalityFlow
now returns a singleSignedTransaction
, instead of aList<SignedTransaction>
TransactionKeyFlow
renamed toSwapIdentitiesFlow
Note that
SwapIdentitiesFlow
must be imported from the confidential-identities* package ‘’net.corda.confidential’‘
Node services (ServiceHub)¶
VaultQueryService: unresolved reference to vaultQueryService.
Replace all references to
<services>.vaultQueryService
with<services>.vaultService
. Previously there were two vault APIs. Now there is a single unified API with the same functions:VaultService
.serviceHub.myInfo.legalIdentity
no longer exists; use theourIdentity
property of the flow instead.FlowLogic.ourIdentity
has been introduced as a shortcut for retrieving our identity in a flowgetAnyNotary
is gone - useserviceHub.networkMapCache.notaryIdentities[0]
insteadNote: ongoing work to support multiple notary identities is still in progress.
ServiceHub.networkMapUpdates
is replaced byServiceHub.networkMapFeed
ServiceHub.partyFromX500Name
is replaced byServiceHub.wellKnownPartyFromX500Name
Note: A “well known” party is one that isn’t anonymous and this change was motivated by the confidential identities work.
RPC Client¶
Missing API methods on CordaRPCOps interface.
Calls to
verifiedTransactionsFeed()
andverifiedTransactions()
have been replaced with:internalVerifiedTransactionsSnapshot()
andinternalVerifiedTransactionsFeed()
respectivelyThis is in preparation for the planned integration of Intel SGX™, which will encrypt the transactions feed. Apps that use this API will not work on encrypted ledgers: you should probably be using the vault query API instead.
Accessing the networkMapCache via
services.nodeInfo().legalIdentities
returns a list of identities. The first element in the list is the Party object referring to a node’s single identity.This is in preparation for allowing a node to host multiple separate identities in future.
Testing¶
Please note that Clauses have been removed completely as of V1.0. We will be revisiting this capability in a future release.
CorDapps must be explicitly registered in
MockNetwork
unit tests.This is done by calling
setCordappPackages
, an extension helper function in thenet.corda.testing
package, on the first line of your @Before method. This takes a variable number of String arguments which should be the package names of the CorDapps containing the contract verification code you wish to load. You should unset CorDapp packages in your @After method by usingunsetCordappPackages()
after stopNodes().CorDapps must be explicitly registered in
DriverDSL
andRPCDriverDSL
integration tests.Similarly, you must also register package names of the CorDapps containing the contract verification code you wish to load using the
extraCordappPackagesToScan: List<String>
constructor parameter of the driver DSL.
Finance¶
FungibleAsset interface simplification.
The
FungibleAsset
interface has been made simpler. TheCommands
grouping interface that included theMove
,Issue
andExit
interfaces have all been removed, while themove
function has been renamed towithNewOwnerAndAmount
to be consistent with thewithNewOwner
function of theOwnableState
.The following errors may be reported:
- override nothing (FungibleAsset): move
- not a subtype of overridden FungibleAsset: withNewOwner
- no longer need to override override val contractHash: SecureHash? = null
- need to override override val contract: Class<out Contract>? = null
Miscellaneous¶
args[0].parseNetworkHostAndPort()
becomesNetworkHostAndPort.parse(args[0])
There is no longer a
NodeInfo.advertisedServices
property.The concept of advertised services has been removed from Corda. This is because it was vaguely defined and real world apps would not typically select random, unknown counterparties from the network map based on self-declared capabilities. We will introduce a replacement for this functionality, business networks, in a future release.
Milestone 13¶
Core data structures¶
TransactionBuilder changes.
Use convenience class
StateAndContract
instead ofTransactionBuilder.withItems()
for passing around a state and its contract.Transaction building DSL changes:
- now need to explicitly pass the ContractClassName into all inputs and outputs.
- ContractClassName refers to the class containing the “verifier” method.
Contract verify method signature change.
override fun verify(tx: TransactionForContract)
becomesoverride fun verify(tx: LedgerTransaction)
No longer need to override Contract
contract()
function.
Node services (ServiceHub)¶
ServiceHub API method changes.
services.networkMapUpdates().justSnapshot
becomesservices.networkMapSnapshot()
Configuration¶
No longer need to define
CordaPluginRegistry
and configurerequiredSchemas
Custom contract schemas are automatically detected at startup time by class path scanning. For testing purposes, use the
SchemaService
method to register new custom schemas: eg.services.schemaService.registerCustomSchemas(setOf(YoSchemaV1))
Identity¶
Party names are now
CordaX500Name
, notX500Name
CordaX500Name
specifies a predefined set of mandatory (organisation, locality, country) and optional fields (commonName, organisationUnit, state) with validation checking. Use new builder CordaX500Name.build(X500Name(target)) or, preferably, explicitly define X500Name parameters usingCordaX500Name
constructor.
Testing¶
MockNetwork Testing.
Mock nodes in node tests are now of type
StartedNode<MockNode>
, rather thanMockNode
MockNetwork now returns a BasketOf(<StartedNode<MockNode>>) Must call internals on StartedNode to get MockNode:a = nodes.partyNodes[0].internals b = nodes.partyNodes[1].internals
Host and Port change.
- Use string helper function
parseNetworkHostAndPort()
to parse a URL on startup. eg.
val hostAndPort = args[0].parseNetworkHostAndPort()
- Use string helper function
The node driver parameters for starting a node have been reordered, and the node’s name needs to be given as an
CordaX500Name
, instead of usinggetX509Name
Milestone 12 (First Public Beta)¶
Core data structures¶
Transaction building
You no longer need to specify the type of a
TransactionBuilder
asTransactionType.General
TransactionType.General.Builder(notary)
becomesTransactionBuilder(notary)
Build¶
Gradle dependency reference changes.
Module name has changed to include corda in the artifacts jar name:
compile "net.corda:core:$corda_release_version" -> compile "net.corda:corda-core:$corda_release_version"
compile "net.corda:finance:$corda_release_version" -> compile "net.corda:corda-finance:$corda_release_version"
compile "net.corda:jackson:$corda_release_version" -> compile "net.corda:corda-jackson:$corda_release_version"
compile "net.corda:node:$corda_release_version" -> compile "net.corda:corda-node:$corda_release_version"
compile "net.corda:rpc:$corda_release_version" -> compile "net.corda:corda-rpc:$corda_release_version"
Node services (ServiceHub)¶
ServiceHub API changes.
services.networkMapUpdates()
becomesservices.networkMapFeed()
services.getCashBalances()
becomes a helper method within the finance module contracts package:net.corda.finance.contracts.getCashBalances
Finance¶
Financial asset contracts (Cash, CommercialPaper, Obligations) are now a standalone CorDapp within the finance module.
- Need to import from respective package within finance module:
eg.
net.corda.finance.contracts.asset.Cash
- Likewise, need to import associated asset flows from respective package within finance module:
- eg.
net.corda.finance.flows.CashIssueFlow
net.corda.finance.flows.CashIssueAndPaymentFlow
net.corda.finance.flows.CashExitFlow
- eg.
Moved
finance
gradle project files into anet.corda.finance
package namespace.This may require adjusting imports of Cash flow references and also of
StartFlow
permission ingradle.build
files. Associated flows (Cash*Flow, TwoPartyTradeFlow, TwoPartyDealFlow) must now be imported from this package.