The steps shown here are tested on Ubuntu 24.04, different distributions may need adjustments to the commands.
All commands are meant to be run as root user, if not specified otherwise. Depending on the server installation, they may need to be run from a different user via sudo.
Prerequisites
Install all needed packages for building and configuring the THORNode daemon
Add the application user that is used to run the THORNode application
useradd -m thornode -s /bin/bash
Build
Checkout the latest code and build the binary
As thornode user run:
git clone --branch v2.135.1 https://gitlab.com/thorchain/thornode $HOME/build
cd $HOME/build
ln -fs /usr/bin/true docker; export PATH=$(pwd):$PATH; TAG=mainnet make install
# remove bifrost binary and build directory
rm $HOME/go/bin/bifrost
rm -rf $HOME/build
Note: The build process currently expects to have a docker binary available, which isn't needed for building the thornode binary, so providing it a fake docker command via symlink is just a hack around that limitation.
Prepare environment
Config
Before running the fullndode the first time, the configuration files and directory layout need to be created.
Seeds provide a list of active thorchain nodes, which are needed to join the network.
As thornode user run:
sed -i 's/^seeds = ""/seeds = "c3613862c2608b3e861406ad02146f41cf5124e6@statesync-seed.ninerealms.com:27146,dbd1730bff1e8a21aad93bc6083209904d483185@statesync-seed-2.ninerealms.com:27146"/' $HOME/.thornode/config/config.toml
Ports
Thorchain doesn't use the cosmos-sdk default ports. Technically this step isn't needed, but it is meant to stay in line with all other THORNode deployments.
As thornode user run:
sed -ri 's/:2665([0-9])/:2714\1/g' $HOME/.thornode/config/config.toml
Genesis
For joining the network, the correct genesis file is required