corda/docs/source/compatibility-zones.rst
Joel Dudley 8b2ab41057
Updated network docs ()
* Renaming and reordering to help users navigate the Networks section.

* Split of pages between bootstrapped, existing and dynamic compatibility zones. Reintegrates Mike H content about creating a dynamic zone.

* Address review feedback except BNO point.

* Documents BNO app.

* Better docs of networkServices config option. Better comments of NetworkParameters fields.

* Documents additional network map protocol endpoint.

* Address review feedback.

* Addresses Kostas review feedback.

* Update protocol due to bug.

* Addresses Kostas's review feedback.

* Addresses Kostas's review feedback.
2018-11-05 15:51:42 +00:00

1.6 KiB

What is a compatibility zone?

Every Corda node is part of a "zone" (also sometimes called a Corda network) that is permissioned. Production deployments require a secure certificate authority. We use the term "zone" to refer to a set of technically compatible nodes reachable over a TCP/IP network like the internet. The word "network" is used in Corda but can be ambiguous with the concept of a "business network", which is usually more like a membership list or subset of nodes in a zone that have agreed to trade with each other.

How do I become part of a compatibility zone?

Bootstrapping a compatibility zone

You can easily bootstrap a compatibility zone for testing or pre-production use with either the network-bootstrapper or the network-builder tools.

Joining an existing compatibility zone

After the testing and pre-production phases, users are encouraged to join an existing compatibility zone such as Corda Network (the main compatibility zone) or the Corda Testnet. See joining-a-compatibility-zone.

Setting up a dynamic compatibility zone

Some users may also be interested in setting up their own dynamic compatibility zone. For instructions and a discussion of whether this approach is suitable for you, see setting-up-a-dynamic-compatibility-zone.