Part 7 - Install and Configure the Node Tracker

  • Clone the Node Tracker software
  • Configure zen.conf
  • Run the tracker and check your node on the tracking website

1Install npm, upgrading it to the stable release
sudo apt-get install npm -y && sudo npm install -g n && sudo n stable

The above may fail on some Debian 10/11 instances, in such cases, use the following to install npm and node js

sudo apt-get install -y nodejs
sudo npm install -g n && sudo n stable
2Change directory (cd) to the user's home directory and clone the Node Tracker software
cd ~/ && git clone
3Change directory (cd) to where the software has been cloned
cd nodetracker
4Install the Node Tracker with npm
npm install

Locate your node's public IPv4 and/or IPv6 address(es) and append them to the zen.conf file as external IP address(es) connected over port 9033 (default)


NOTE: Replace <IPv4> with the public IPv4 of your node, remove <brackets>

NOTE: Replace <IPv6> with the public IPv6 of your node in compressed notation without leading zeros, remove <brackets>

Use the following link to ensure your IPv6 address is in compressed notation:

Create environmental variables for IPv4


Append external IPv4 into zen.conf

echo "externalip=$IPV4" >> ~/.zen/zen.conf

Create environmental variables for IPv6


Append external IPv6 into zen.conf

echo "externalip=$IPV6" >> ~/.zen/zen.conf

Append port into zen.conf 

echo "port=9033" >> ~/.zen/zen.conf

Restart zend and check the address configuration

NOTE: The output of the 2nd command should display the address(es) entered in the previous step

zen-cli stop && sleep 8 && zend && sleep 30
zen-cli getnetworkinfo | grep address

Configure the tracker by running the setup process, for this you will need the following details

  • Enter node type (super)
  • Stake t_address (the t_address with 42 or 500 ZEN from step 7.2)
  • Email address - to receive alerts for any exceptions, downtimes or notifications related to your node
  • Fully-Qualified Domain Name (FQDN)
  • IP address version (ipv4, or ipv6)
  • Region code (choose NA, or EU), defaults to your node's nearest region
  • Optional node category - alphanumeric (used to help categorize nodes)
    • Must have an entry to be able to generate an API sub key
    • If using an optional verified stake address created with the Stake Tool enter the category associated with the API sub key

node setup.js
8Now test the Node Tracker installation and configuration
node app.js

Leave the Node Tracker running in your terminal and check the status of your node on the tracking website, use the search box and enter the FQDN of your node << Super Nodes

Select your node and check the following values (top left of the detail page) are true and up respectively - example shown to the right

NOTE: The tracking server validates certificates in batches, you may only see a State of "up" and a Cert Valid of "not checked" or "false not found" until the tracking server runs a batch of certificate checks. You can proceed with further steps without waiting for a Cert Valid of "true"

10If your node displays on the tracking site with "state: up", exit the tracker by pressing CTRL + c and continue to part 9

Part 8 of 11 - Install and Configure the Node Tracker

© 2020 Horizen. All rights reserved.