Setting Up A Notary Node

A notary node is a well known and trusted node that provides uniqueness consensus. Because of this, creating and running a notary node is slightly more involved compared with a regular node.

The Network Map Service broadcasts information (stored in the network parameters file) that every participant in the network needs to agree on. One piece of information is the list of notaries. Because all notaries within this list need to be well known and trusted, the process of adding a new one requires some manual intervention on the Network Map Service side.

The exact configuration will depend on the Corda version that the notary node is running.

myLegalName="O=Example Notary,L=London,C=GB"
notary {
    validating=false
}

networkServices {
  doormanURL="http://<IDENTITY_MANAGER_HOST>:<IDENTITY_MANAGER_PORT>"
  networkMapURL="http://NETWORK_MAP_SERVICE_HOST>:<NETWORK_MAP_SERVICE_PORT>"
}

devMode = false

sshd {
  port = <SSH_PORT>
}

p2pAddress="<NOTARY_HOST>:<NOTARY_PORT>"

The steps to integrate the notary node into the network are:

  • Register the node with the Identity Manager
  • Generate the node info file
  • Copy the node info file to the Network Map Service
  • Update the network parameters file on the Network Map Service to reference the new node info file
  • Start (or restart) the Network Map Service
  • Start the notary node as normal

Ensuring that the Identity Manager Service is successfully running, start the notary node for registration.

java -jar corda.jar --config-file <NODE_CONF_FILE> --initial-registration --network-root-truststore-password <TRUST_STORE_PASSWORD> --network-root-truststore <PATH_TO_TRUST_STORE>

The node info file contains information such as address and certificates. The file will be used by all participants on the network to enable them to connect to, and trust, the new notary node.

java -jar corda.jar --config-file <NODE_CONF_FILE> --just-generate-node-info

Follow instructions here Network Map Service

java -jar corda.jar --config-file <NODE_CONF_FILE>

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.