The network

  • A Corda network is made up of nodes running Corda and CorDapps
  • Communication between nodes is point-to-point, instead of relying on global broadcasts
  • Each node has a certificate mapping their network identity to a real-world legal identity
  • The network is permissioned, with access requiring a certificate from the network operator

Network structure

A Corda network is a peer-to-peer network of nodes. Each node runs the Corda software as well as Corda applications known as CorDapps.

network All communication between nodes is point-to-point and encrypted using transport-layer security. This means that data is shared only on a need-to-know basis. There are no global broadcasts.

Identity

Each node has a single well-known identity. The node’s identity is used to represent the node in transactions, such as when purchasing an asset.

Each network has a network map service that maps each well-known node identity to an IP address. These IP addresses are used for messaging between nodes.

Nodes can also generate confidential identities for individual transactions. The certificate chain linking a confidential identity to a well-known node identity or real-world legal identity is only distributed on a need-to-know basis. This ensures that even if an attacker gets access to an unencrypted transaction, they cannot identify the transaction’s participants without additional information if confidential identities are being used.

Admission to the network

Corda networks are semi-private. To join a network, a node must obtain a certificate from the network operator. This certificate maps a well-known node identity to:

  • A real-world legal identity
  • A public key

The network operator enforces rules regarding the information that nodes must provide and the know-your-customer processes they must undergo before being granted this certificate.

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.