Part 1 - Introduction and Domain Name Registration


This guide is intended for someone who is looking to setup a Horizen Super Node. A Super Node is intended to be installed on a Virtual Private Server (VPS), Virtual Machine (VM), or standalone server hardware with a 64-bit architecture. Setup will be performed from a command line interface or CLI. On Windows 7 64-bit and newer, this will most commonly be PuTTY, and Terminal on Mac OS and Linux.

It is expected from node operators that they are not just able to follow this guide to completion to run a node, but to keep up with regular security updates and Horizen software updates. Updates are made on a quarterly basis with some periodic interim updates to improve the security, features, performance and reliability of the network. Requirements will not stay static. An operator should also be able to perform system migration and to perform upgrades to support increasing requirements (such as available disk space IE).

If you're unfamiliar with Linux system administration, we recommend that you use one of our many hosting providers. The Horizen blockchain rewards node operators with a percentage of the block reward to run and maintain a quality, fast and reliable node.

The format of the guide is deliberately column-based providing a description on the left, alongside each of the steps, to clarify the exact purpose. A more experienced user may prefer to simply follow the commands in the right column. The guide supports a simple double-click copy and paste of each command into a terminal.

Where applicable, these images will be displayed to indicate if a particular step or page in the guide is specific to one or more operating system. If none are present, the steps apply universally.


Mac OS       Linux         Windows          

Toggle the sidebar on the left << with the [ key

For the best experience with the guide, maximize your window screen such that you do not have any horizontal scroll bar

DO NOT INSTALL AND RUN A SUPER NODE UNDER THE ROOT USER. The guide details how to add a non-root user, under which the necessary processes will run.

VPS configurations using OpenVZ are not supported.

Super Nodes

NOTE: Storage allocation of 100GB is likely to change to free disk space when the full Super Node solution is implemented.

CPU must be based on x86-64 and be on the Intel Broadwell (and newer) or the AMD Excavator (and newer) architectures. Must have flags +bmi2 +adx. Updated since upgrade to ZEND 2.0.24.

The total memory allocation required is 8GB+ of RAM (Not including swap). x86-64 Intel Haswell architecture (or AMD equivalent) CPUs and newer are recommended to meet performance requirements. Super Nodes must have at least 100GB of storage allocated to them.

Community Lists

See the Community VPS List for a list of VPS services our community uses with great success.

  • This list is updated as often as possible and does not reflect the full array of possible services that can be used for a Horizen Super Node

If you're uncomfortable with performing the setup and maintenance needed for a Super Node, you may prefer to reference the Community Hosting and Setup List for a list of node services offered by our community.

  • This list is updated as often as possible and does not reflect the full array of possible services that can be used for a Horizen Super Node

Node Operator Requirements

Further details regarding the Super Node criteria and reward eligibility are available on the following pages:


Domain Name Registration & Propagation

A domain name registration (DNS record) is required for a Super Node. This must point to the external IP address of the Super Node. The value used for your DNS record is referred to as your Fully-Qualified Domain Name (FQDN). It will have a format along the lines of >>

Before you begin configuration of your Super Node, verify your domain name has fully propagated. You can check this at "what is my dns?". If you're using an ipv4 public address, you have an "A" record, if you're using an ipv6 address, you have an "AAAA" record. Enter your FQDN into the search engine with your appropriate DNS record and search. If your FQDN has fully propagated, all the servers in the listing will have a green  check mark.

For Super Nodes, both an A and AAAA record must be created for your DNS that resolves to your node's IPv4 and IPv6 addresses

NOTE: Many VPS providers do not pre-configure IPv6, you must follow your providers instructions on setting up this connection. Once configured properly and added to your DNS with a AAAA record resolving to the same FQDN as the IPv4 address, you can verify proper connectivity with the commands listed below


Verify that you can reach your node (using the domain name) from your local machine. Replace the example ( in the command with your own FQDN.

  • Mac OS - use Terminal (press <CMD> + <SPACE> and type terminal, followed by <Enter>)
  • Linux - open the Terminal application (exact steps differ per distribution)

Ping IPv4

ping -c 3

Ping IPv6

ping6 -c 3

satoshi@goldwasser:~$ ping -c 3
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=52 time=27.5 ms
64 bytes from ( icmp_seq=2 ttl=52 time=27.6 ms
64 bytes from ( icmp_seq=3 ttl=52 time=27.7 ms

--- ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 82.8ms
rtt min/avg/max/mdev = 27.590/27.660/27.723/0.043 ms


Verify that you can reach your node (using the domain name) from your local machine. Replace the example ( in the command with your own FQDN.

  • Open a command prompt (press <WinKey> + <r> and type cmd, followed by <Enter>)

Ping IPv4

ping -n 3 -4

Ping IPv6

ping -n 3 -6

C:\Users\turing>ping -n 3 -4

Pinging [] with 32 bytes of data:
Reply from bytes=32 time=181ms TTL=52
Reply from bytes=32 time=215ms TTL=52
Reply from bytes=32 time=178ms TTL=52

Ping statistics for
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 226ms, Average = 200ms

Part 1 of 11 - Introduction and Domain Name Registration

© 2020 Horizen. All rights reserved.