An Introduction to Radix Nodes

10st Okt 2023Radix Node v1.0.4 released

We renamed the binary filename from radixnode to babylonnode and changed the default file locations in order to prevent file clashes or unintentional overwrites when updating a node from Olympia to Babylon. Beware that despite effort to reduce friction, we highly recommend to do the migration using a new separate node instead of recycling the existing olympia node.

10st Okt 2023Radix Node v1.0.4 released

Use the babylonnode CLI to update your node or install a new node from scratch – or refer to the update instructions for Docker or systemd install methods.

What is a Radix Node?

The Radix Node (GitHub) is the building block of Radix Network infrastructure. Nodes connect together to conduct consensus on transactions, maintain the ledger, and provide other useful functions.

It can be configured in two different ways depending on its purpose:

A Full Node simply connects to the network, synchronizes ledger state, and observes the status of the network. It can also be thought of as a kind of “wallet” that is connected directly to the network, with the Node’s own account available for programmatic control.

A Validator Node starts life as a Full Node, but has also “registered” itself to the network as a Validator by submitting a special transaction from its account. Registration means that it may now accept XRD token “stake” and potentially be included in the validator set of 100 nodes that conduct network consensus.

Running a Node

If you’re already running an Olympia node (and especially if you’re an active validator) follow the instructions in Olympia to Babylon node migration after you’ve set up your Babylon node.

If you’re looking to run a node for its APIs, first read the Node and Gateway overview to check if you should also be running a Gateway, to get a Gateway API.

See the Node Setup Docs for information on how to set up or configure a node, and check out the Maintenance and Additional Resources sections for further information.