How to setup an external passive relay node

This quick start guide walks through setting up an external relay node with the help of CNTOOLs.

Major credits and appreciation to the fine folks at Cardano Community Guild Operators for creating and maintaining CNtool, a most helpful swiss army knife for pool operators. You MUST be familiar with how ADA staking works and possess fundamental Linux system administration skills before continuing this guide.

Relay nodes do not have any keys, so they cannot produce blocks. Instead, relays act as proxies between the core network nodes and the internet, establishing a security perimeter around the core, block-producing network nodes. Since external nodes cannot communicate with block-producing nodes directly, relay nodes ensure that the integrity of the core nodes and the blockchain remains intact, even if one or more relays become compromised.

​🌜 0. Prerequisites

  • A different server/VM (not located on the same machine as your block-producer node)

​🛸 1. Run

Installs prerequisite dependencies and creates folder structure.

sudo apt-get install curl net-tools
mkdir "$HOME/tmp";cd "$HOME/tmp"
# Install curl
# CentOS / RedHat - sudo dnf -y install curl
# Ubuntu / Debian - sudo apt -y install curl
curl -sS -o
chmod 755
# Ensure you can run sudo commands with your user before execution
# You can check the syntax for using command below:
# ./ -h
# Usage: [-o] [-s] [-i] [-g] [-p]
# Install pre-requisites for building cardano node and using cntools
# -o Do *NOT* overwrite existing genesis, topology.json and files (Default: will overwrite)
# -s Skip installing OS level dependencies (Default: will check and install any missing OS level prerequisites)
# -i Interactive mode (Default: silent mode)
# -g Connect to guild network instead of public network (Default: connect to public cardano network)
# -p Copy Transitional Praos config as default instead of Combinator networks (Default: copies combinator network)
# You can use one of the options above, if you'd like to defer from defaults (below).
# Running without any parameters will run script in silent mode with OS Dependencies, and overwriting existing files.

Reload environment variables.

. "${HOME}/.bashrc"

Familiarize yourself with the folder structure created by CNtools.

​🤹♀ 2. Build Cardano Node and CLI

Clone the git repository.

cd ~/git
git clone
cd cardano-node

Build all the binaries. Replace the tag with the desired version.

git fetch --tags --all
git pull
# Replace tag 1.26.2 with the version/branch you'd like to build
git checkout 1.26.2
echo -e "package cardano-crypto-praos\n flags: -external-libsodium-vrf" > cabal.project.local

Install binaries to local bin directory.

sudo cp $HOME/.cabal/bin/cardano* /usr/local/bin

Verify the correct versions were compiled.

cardano-cli version
cardano-node version

​⚒ 3. Auto-starting with systemd services

​🎊 Benefits of using systemd for your stake pool

  1. Auto-start your node when the computer reboots due to maintenance, power outage, etc.

  2. Automatically restart crashed node processes.

  3. Maximize your stake pool up-time and performance.

sudo bash -c "cat << 'EOF' > /etc/systemd/system/cnode.service
Description=Cardano Node
ExecStart=/bin/bash -l -c \"exec $CNODE_HOME/scripts/\"
ExecStop=/bin/bash -l -c \"exec kill -2 \$(ps -ef | grep [c]ardano-node.*.${CNODE_HOME} | tr -s ' ' | cut -d ' ' -f2)\"
sudo systemctl daemon-reload
sudo systemctl enable cnode.service

Nice work. Your node is now managed by the reliability and robustness of systemd. Below are some commands for using systemd.

✅ Check whether the node service is active

sudo systemctl is-active cnode

​ 🔎 View the status of the node service

sudo systemctl status cnode

​ 🔄 Restarting the node service

sudo systemctl reload-or-restart cnode

​ 🛑 Stopping the node service

sudo systemctl stop cnode

​🚧 Filtering logs

journalctl --unit=cnode --since=yesterday
journalctl --unit=cnode --since=today
journalctl --unit=cnode --since='2020-07-29 00:00:00' --until='2020-07-29 12:00:00'

​🚀 4. Start the relay node

Pro tip: 🎇 Speed this step up by copying the db folder from another node you control.

sudo systemctl start cnode

Install Guild LiveView.

cd $CNODE_HOME/scripts
curl -s -o
curl -s -o env
chmod 755

Run Guild Liveview.


Sample output of Guild Live View

For more information, refer to the official Guild Live View docs.​

​🛑5. Configure and review the relay node topology file

Modify the CUSTOM_PEERS section of the script to configure your relay node's connections to your other relays and block producer node. Refer to the official documentation for more info.​

nano $CNODE_HOME/scripts/

Deploy the scripts with to setup and schedule the execution. This will handle automatically sending updates to the Topology Updater API as well as fetching new peers whenever the node is restarted.


Review your topology.json and check that it looks correct. Your new relay node's topology should contain your block producer node, your other relay nodes, and other public buddy relay nodes.

cat $CNODE_HOME/files/topology.json

​🔥 6. Configure port-forwarding and/or firewall

Specific to your networking setup or cloud provider settings, ensure your relay node's port 6000 is open and reachable.

​✨ Port Forwarding Tip: Check that your relay port 6000 is open with or .

Additionally, if you have node-exporter installed for grafana stats, you will need to open ports 9100 and 12798. Don't forget to update prometheus.yml on your prometheus server (aka relaynode1). Restart prometheus service for the new relay node to appear in your dashboard.

​👩💻 7. Configure existing relay or block producing node's topology

Finally, add your new NEW relay node IP/port information to your EXISTING block producer and/or relay node's topology file. Modify the CUSTOM_PEERS section of the

For your block producer node, you'll want to manually add the new relay node information to your topology.json file.

Example snippet to add to your block producer's topology file. Add a comma to separate the nodes where appropriate.

"addr": "<relay node public ip address>",
"port": 6000,
"valency": 1

For relay nodes, use the topologyUpdater process to manage your topology file or modify the CUSTOM_PEERS section of the

​🔄 8. Restart all relay and block producer nodes for new topology configurations to take effect

​🎊 9. Verify the connection is working

On the Guild LiveView screen, press P to view the peer list. You should see the connection to other node's IP.

​✨ Congrats on the new relay node.

​🔥 Critical Security Reminder: Relay nodes must not contain any operational certifications, vrf, skey or cold keys.

Congrats on completing the guide. ✨

Did you find our guide useful? Send us a signal with a tip and we'll keep updating it.

It really energizes us to keep creating the best crypto guides.

Use to find our donation addresses. 🙏

Any feedback and all pull requests much appreciated. 🌛

Hang out and chat with fellow stake pool operators on Discord @

​ 😃

Hang out and chat with our stake pool community on Telegram @​