Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

The selected root page could not be found.

Introduction

This guide is intended for someone who is looking to setup a zencash 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.


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.


NOTE: Previous installation guides advised to use a 1 GB VPS server with 4 GB of swap on an SSD. Extensive testing and community feedback revealed that these specifications are no longer suitable.

The recommended total memory allocation is 6GB (RAM + SWAP). CPUs of an Intel Haswell architecture (or AMD equivalent) and newer have been performing well.

  • Nodes configured with 4GB of RAM and 2GB of SWAP have shown to reliably pass challenges
  • Nodes configured with 2GB of RAM and 4GB of SWAP have had some luck with passing challenges
  • Nodes configured with 1GB of RAM and 5GB of SWAP have seldom passed challenges


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 zencash 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 zencash Super Node


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


DescriptionCommand
1

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 >> myhost.mydomain.com

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 (tick) check mark.

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.


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

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

--- node01.zentest.win 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

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.

  • Open a command prompt (press <WinKey> + <r> and type cmd, followed by <Enter>)
ping -n 3 myhost.mydomain.com


C:\WINDOWS\system32\cmd.exe

C:\Users\turing>ping -n 3 node01.zentest.win

Pinging node01.zentest.win [123.123.123.123] with 32 bytes of data:
Reply from 123.123.123.123: bytes=32 time=181ms TTL=52
Reply from 123.123.123.123: bytes=32 time=215ms TTL=52
Reply from 123.123.123.123: bytes=32 time=178ms TTL=52

Ping statistics for 123.123.123.123:
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.


  • No labels