Corda Network Foundation Document history

Joining Corda Network

A summary of steps to join the Network (either the Pre-Production or Production network) is listed below. More details are given on each of these steps, further down this page.

This assumes that participants wish to operate a node and already have access to at least one CorDapp which they wish to deploy, as well as other considerations listed.

New Joiner Process

June 2019: Please note, the team is working hard to streamline this process, to provide an improved user experience.

Detailed Joining Process

The below provides more on detail on each of the steps for the joining process for either Pre-Production or Production network.

Step 1 Obtain Corda software - either:

Step 2 Trust Root - request the Trust Root from the Network’s Identity Manager. It will be sent back as a network-root-truststore.jks file. In future, the Trust Root will be packaged in the software distribution. For Pre-Production, email For the Production Network, email

Step 3 Deploy the node - where applicable, with help from a Corda representative.

Step 4 Configure the node – a node.conf file must be included in the root directory of every Corda node.

Step 4.1 Choosing an email address The email address should be non-personal (for example, admin@… or info@…) and actively monitored by the node operator. The email address is retained by the Corda Network Operator for the purpose of contact in relation to identity checks (for onboarding) and any administrative or technical issues (on an ongoing basis). It is not included in the certificate.

Step 4.2 Picking a Distinguished Name All nodes on Corda Network must have a Distinguished Name (DN) in their participation certificate.

  • Follow the guidelines here to pick the right DN, as part of the onboarding process.
  • A DN will include a legal entity name for your node. For guidance on which legal entity name to pick for your node, see here.

Step 4.3 Specifying URLs For Initial Registration


Please note if you are joining a SSZ, you need to request your unique networkMapURL from for pre-production or for the production network. The below networkmapurls are for the public zones, so if you start up your node and connect with this url, you will join the public zone. This is a problem that can easily be corrected if you do it accidentally, but your node’s identity will appear on the network map for a period of time, and if you want to keep your node’s identity 100% private, you need to take care not to accidentally join a public zone.

Pre-Production Network

networkServices {
devMode = false
tlsCertCrlDistPoint : ""
tlsCertCrlIssuer : "CN=Corda TLS CRL Authority,OU=Corda UAT,O=R3 HoldCo LLC,L=New York,C=US"

Production Network

The settings below must be added to the node.conf at the end of the file:

networkServices {
devMode = false

tlsCertCrlDistPoint : “”
tlsCertCrlIssuer : “CN=Corda TLS CRL Authority,OU=Corda Network,O=R3 HoldCo LLC,L=New York,C=US”

Step 5 Run the initial registration

Once the node.conf file is configured, the following should be typed to the command line:

java -jar corda.jar --initial-registration

This will send a Certificate Signing Request (with the relevant name and email) to the Identity Service.

A message similar to the below will be printed to the console:

Legal Name: O=ABC LIMITED, L=New York, C=US

Public Key: EC Public Key
            X: d14bc17e650f2a317cbcb95e554f1e26808ca80f67ab804bbc911ec16673abbd
            Y: 1978b02a8e693ecd534ceef835091c376cfc4e506decc69b91a872fc13ad1aeb

Submitting certificate signing request to Corda certificate signing server.
Successfully submitted request to Corda certificate signing server, request ID: 6CBB63558B4B2D9C94F8C14AB713432F60AF692EB30F2E12E628B089C517F3CF.
Start polling server for certificate signing approval.

Important: the Request ID given in the above should be noted and kept safe for future reference.

Step 6 Terms of Use Agreement

Direct Model

Pre-Production Network

The Terms of Use for direct signing are available as a click-through agreement which will provide direct confirmation of acceptance to the Corda Network Operator. Available here: Terms of Use

Production Network

Terms of Use for direct signing available here

Sponsored Model

Business Network Operators need to ensure their participants have signed the Terms of Use before they can receive a participation certificate. If BNOs prefer to organise acceptance themselves, then they must forward appropriate documentary evidence for each participant (either a signed hard copy with wet signature or a scan of such hard copy). You must specify the precise Distinguished Names in order to confirm that the correct entity has signed and an accurate certificate can be issued. They must also sign a Sponsored Terms of Use Agreement (available both for Pre-Production and Production), which can be requested through an r3 representative, or via

Step 7 Identity Manager The Identity Manager does verification checks – upon receipt of a CSR, a number of identity-related checks will be conducted, before issuing a certificate.

Identity checks do not constitute formal Know Your Customer (KYC) or Enhanced Due Diligence (EDD) checks. Node operators and their users are responsible for carrying out appropriate due diligence on any participant in relation to transactions performed via Corda Network.

Upon receipt of a CSR, the Identity Operator will conduct a number of identity-related checks before issuing a certificate:

  1. The DN accurately reflects a real-world legal entity, as registered with an appropriate trade register
  2. The node operator (participating entity) has signed the Corda Network Terms of Use
  3. The contact email address provided is valid
  4. The owner of the email address and an independent and suitably qualified person in the same organisation is aware of / approves the CSR

Step 8 Confirmation Once identity checks have been completed, a signed node CA certificate will be released by the Operator to the node. A node in polling mode will automatically download and install the certificate in its local trust store. It will also automatically generate additional identity and TLS certificates from the node CA certificate, which are required for subsequent operation of the node.

At this point, the node will terminate and will need to be restarted. Type “java -jar “ into the command line. Once restarted, the node will then proceed to download the network map and discover other nodes within Corda Network. By the end of this process, joiners will be a participant in Corda Network and Corda Network Foundation.

Confirming your implementation - Installation and configuration of your Corda applications must be undertaken by the node operator. Instructions to install CorDapps can be found on Specifics on application usage or installation should be available from your CorDapp provider.

Business Network Operators should co-ordinate any post-install tests that may involve a small number of low value transactions on the business network to assure themselves of the correct setup of their node. Node operators should co-ordinate with their Business Network Operator in this regard. All node-initiated activity on the network from the point of connection is the responsibility of the node operator.

Participation fee

Billing details will be gathered, for a participation fee invoice, during this process. This will depend on if they are part of the indirect or direct model.

For further questions on this process, please contact us - preferably on the mailing list.