Setting up a notary service

Corda comes with several notary implementations built-in:

  • Single-node: a simple notary service that persists notarisation requests in the node’s database. It is easy to set up and is recommended for testing, and production networks that do not have strict availability requirements.
  • Crash fault-tolerant (experimental): a highly available notary service operated by a single party.
  • Byzantine fault-tolerant (experimental): a decentralised highly available notary service operated by a group of parties.

Single-node

To have a regular Corda node provide a notary service you simply need to set appropriate notary configuration values before starting it:

notary : { validating : false }

For a validating notary service specify:

notary : { validating : true }

See Validation for more details about validating versus non-validating notaries.

For clients to be able to use the notary service, its identity must be added to the network parameters. This will be done automatically when creating the network, if using Network Bootstrapper . See Networks for more details.

Crash fault-tolerant (experimental)

Corda provides a prototype Raft-based highly available notary implementation. You can try it out on our notary demo page. Note that it has known limitations and is not recommended for production use.

Byzantine fault-tolerant (experimental)

A prototype BFT notary implementation based on BFT-Smart is available. You can try it out on our notary demo page. Note that it is still experimental and there is active work ongoing for a production ready solution. Additionally, BFT-Smart requires Java serialization which is disabled by default in Corda due to security risks, and it will only work in dev mode where this can be customised.

We do not recommend using it in any long-running test or production deployments.

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.