Introduction to node installation
If you’re interested in setting up a node on the Ronin mainnet, here are some hardware recommendations and guides on different methods of installation.
For testnet installation guides, see Saigon testnet.
To run a reliable, performant node on the Ronin mainnet, we suggest that the node’s hardware profile should match or exceed the following specifications:
|Validator node||Non-validator node||Archive node||Bridge operator|
|8-core CPU||6-core CPU||8-core CPU||8-core CPU|
|32 GB RAM||25 GB RAM||32 GB RAM||32 GB RAM|
|700 GB high-speed SSD||700 GB high-speed SSD||7 TB high-speed SSD||700 GB high-speed SSD|
|x86-64 architecture||x86-64 architecture||x86-64 architecture||x86-64 architecture|
These hardware requirements are rough guidelines, and each node operator should monitor their node to ensure good performance for the intended task. The size of your Ronin node will also grow over time.
Get started with node installation
We offer two different methods of installing nodes:
- The Docker method describes the installation of Ronin nodes as Docker instances, for those comfortable with Docker. Two different approaches to setting up your nodes using Docker are described in the following sections.
- The CLI (command line interface) method uses a CLI tool to compile your own node binary from source. For more information, see Build your node using Ronin CLI.
Choose an approach
Within the Docker method, there are two ways to approach the installation of a validator and a bridge operator:
- Combined setup
- Standalone setup
In a combined setup, the validator and the bridge are defined in the same
docker-compose.yml file and run on one machine. We recommend this approach to most users for easier onboarding.
Follow this guide for a combined setup:
📄️ Run a validator and bridge together
(Recommended) Install a mainnet validator and bridge on one machine using Docker.
In a standalone setup, the validator node and the bridge operator are defined in two different
docker-compose.yml configurations and run on two machines, respectively. In this approach, a non-validator node runs alongside the bridge component, allowing you to isolate the resources between the validator and the bridge for enhanced reliability and security.
Follow these guides for a standalone setup:
📄️ Run a standalone validator
Install a standalone mainnet validator node using Docker.
📄️ Run a standalone bridge
Install a standalone mainnet bridge operator after setting up the validator node.