Setting up a notary in a segregated network
Segregated networks are a smaller network operating within the context of a larger network. A segregated network allows a measure of independence and control over the network parameters within a larger Corda network.
When operating in a Corda Network segregated network, you must deploy, register, and operate the notary. There are three notary implementations to choose from:
- A single notary node
- A notary cluster using a single node
- A highly-available (HA) notary cluster requiring multiple nodes
You should take care when deciding on the type of notary to deploy, as single notary nodes cannot be upgraded to HA notaries later. In production environments R3 recommends using a notary cluster for additional reliability and scalability.
Configuring and deploying a notary
Single-node notaries are simple notary implementations and are not recommended for production environments.
A notary cluster is a group of at least one node that act together as one pooled notary service. Notary clusters can improve notary scalability and reliability because additional nodes can be added to the notary pool as demand increases.
Single-node and multi-node notary clusters are only available in Corda Enterprise. Before deploying a notary cluster, read the JPA notary configuration documentation. A notary cluster requires a backend database to store notarised transactions. A notary cluster can be registered, but not run, without a database.
Register the notary service identity using the HA Utilities tool.
Register each worker node in the notary cluster using the Corda Network process.
Each worker node requires access to the notary service identity key generated in the preceding step. R3 recommends using an HSM to ensure key security.
Add the notary service identity to the network parameters by sending the
nodeInfo-xxx
file using the Corda Network support portal using either a segregated network request form, or by creating a new task.After the network parameters have been updated, start the notary worker nodes.
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.