April 30, 2021
This week, we wanted to share some of our top tips for one of your most-asked-about topics: Corda networks!
Corda networks can be used in many contexts and with a variety of tooling to connect them, which can sometimes make things confusing. Let’s start from the beginning.
Corda nodes find each other using the network map. This is a collection of statically signed node-info files, one for each node. If you’re using a network manager, the nodes will request this file from there. If you’re using the network bootstrapper, the nodes have this file created and available from the outset. Ultimately, each node maintains a local map of the other nodes that it can reach.
There are three primary types of Corda networks you should be aware of:
You theoretically could, but it’s not recommended. Remember that those network details are hard-coded. If you wanted to add a new node or a new party to your network, you’d have to re-generate all the network information, stop each node, copy the new network information, and restart them.
Another note about the network map that you get from the bootstrapper is that it’s stored in a serialized blob format. If you open it with Vim, you’ll see gibberish, but you can inspect these blobs with the Corda blob inspector.
Our general recommendation is to use Corda Enterprise with Corda Enterprise Network Manager.
Yes. You can use Corda Open source for your nodes and just use the Enterprise network manager.
For that, you have some community options. The most popular one that’s emerged is called Cordite. While we don’t officially support it, some developers have used it and had success going that route. Be warned, though, that it certainly is harder!
If you’d like to see more blog posts like these or have ideas on what we should add, feel free to send a note to email@example.com.
Share this post
Stay up to date on the latest news and articles related to Corda.