Introduction
This guide is intended for someone who is looking to setup a Horizen Secure/Super Node. A Secure/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.
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 SECURE/SUPER NODE UNDER THE ROOT USER. The guide details how to add a non-root user, under which the necessary processes will run.
Secure Nodes
NOTE: Our previous guidance advised to use a 4GB RAM VPS server with 2GB of swap on an SSD under Zen 2001150. Under Zen 2001450 these requirements have been reduced. We now recommend configurations with 2GB RAM and 2GB of swap on an SSD.
The recommended total memory allocation is 4GB (RAM + swap). CPUs of an x86-64 Intel Haswell architecture (or AMD equivalent) and newer have been performing well. At this time, due to the size of the blockchain, the minimum storage requirement is 30GB.
We recommend 40GB or larger to allow room for blockchain growth. The storage minimum requirements and recommendations will be periodically increased as the size of the blockchain increases.
Super Nodes
NOTE: Storage allocation of 100GB is likely to change to free disk space when the full Super Node solution is implemented (estimated to be Q1 2019)
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 Secure/Super Node
If you're uncomfortable with performing the setup and maintenance needed for a Secure/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 Secure/Super Node
Node Operator Requirements
Further details regarding the Secure/Super Node criteria and reward eligibility are available on the following pages:
| Description | Command | |
|---|---|---|
| 1 | Domain Name Registration & PropagationA domain name registration (DNS record) is required for a Secure/Super Node. This must point to the external IP address of the Secure/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 >> myhost.mydomain.com Before you begin configuration of your Secure/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 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 |
|
| 2 |
Verify that you can reach your node (using the domain name) from your local machine. Replace the example (myhost.mydomain.com) in the command with your own FQDN.
| Ping IPv4 ping -c 3 myhost.mydomain.com Ping IPv6 ping6 -c 3 myhost.mydomain.com Terminal satoshi@goldwasser:~$ ping -c 3 node01.zentest.win --- node01.zentest.win ping statistics --- |
| 3 |
Verify that you can reach your node (using the domain name) from your local machine. Replace the example (myhost.mydomain.com) in the command with your own FQDN.
| Ping IPv4 ping -n 3 myhost.mydomain.com -4 Ping IPv6 ping -n 3 myhost.mydomain.com -6 C:\WINDOWS\system32\cmd.exe C:\Users\turing>ping -n 3 node01.zentest.win -4 Pinging node01.zentest.win [123.123.123.123] with 32 bytes of data: Ping statistics for 123.123.123.123: |
