The Zilliqa Client is officially supported on Ubuntu 18.04 OS.
The minimum requirements for running the Zilliqa Client are:
- x64 Linux operating system (e.g Ubuntu 18.04.5)
- Recent dual-core processor @ 2.2 GHZ. Examples: Intel Xeon (Skylake)
- 4GB DRR3 RAM or higher
- NAT environment OR Public static IP address
- Any GPUs with at least 2 GB RAM
- 100MB/s upload and download bandwidth
Hashing rate of the network is currently very high. A single GPU will be insufficient. You will need to setup mining proxy connecting to multiple GPUs.
Network Setup for Zilliqa Client
If you are using a home router, you are most probably in a NAT environment.
If you are in a NAT environment, you can either:
- Do single port forwarding using Option 1a. This should be your DEFAULT OPTION.
- Enable UPnP mode using Option 1b if your router does support UPnP.
If you have a public IP address, you can skip this network setup section entirely.
Port forward to port
33133 for both external port (port range) and internal port (local port). You will also have to select the option for BOTH TCP and UDP protocol in your router menu when port forwarding.
An example of this process can be found HERE. After port forwarding, you may check if you have successfully port forwarded with this Open Port Check Tool.
Enable UPnP mode on your home router. Please Google how to access your home router setting to enable UPnP, an example can be found HERE. You can check if you have enabled it UPnP by installing the following tool:
Then type the following in the command line:
You should get a message showing either:
- "List of UPNP devices found on the network : ..."
- OR "No IGD UPnP Device found on the network !".
The first message means UPnP mode has been enabled successfully, while the latter means the enabling of UPnP mode has failed. If you receive the latter message, proceed with using Option 1a instead.
Create a single local or remote CPU node instance with Ubuntu 18.04 OS installed following instructions HERE.
Install Docker CE for Ubuntu on your CPU node instance by following instructions HERE.
Make a new directory in your Desktop and change directory to it:cd ~/Desktop && mkdir join && cd join
Get the joining configuration files:wget https://mainnet-join.zilliqa.com/configuration.tar.gztar zxvf configuration.tar.gz
Find out your current IP address in the command prompt and record it down:curl https://ipinfo.io/ip
Please consult the previous section if you are in a NAT environment.
Edit your constant.xml file in your configuration folder:
GETWORK_SERVER_PORTto the port you will be using to GetWork. (default is
Set the following mining parameters to
Install the python dependencies:sudo apt install python-pipexport LC_ALL=Cpip install request requests clint futures
Run the shell script in your command prompt to launch your docker image:./launch_docker.sh
You will be prompted to enter some information as shown below:
DO NOT duplicate your IP address and use different ports to create different CPU nodes. You will be blacklisted by the network and hence not be able to receive any rewards.
Assign a name to your container (default: zilliqa):
[Press Enter to skip if using default]
Enter your IP address ('NAT' or *.*.*.*):
[Key in your IP address as found in step 5 OR
NATif you chose Option 1b for network setup]
Enter your listening port (default: 33133):
[Press Enter to skip if using default]
You are now a miner in the Zilliqa Mainnet. You can monitor your progress on your CPU node by using:
Checking Your Generated Keypairs
To check your locally generated public and private key pairs in your mykey.txt file, you can enter the following in your command prompt on your CPU node:
The first hex string is your public key, and the second hex string is your private key.
This key pair is generated locally on your disk. Do remember to keep your private key somewhere safe!
Checking Your $ZIL Balance
To check your balance for mining, input the address located in your myaddr.txt file in the search bar of https://viewblock.io/zilliqa:
Stopping the Mining Process
To stop the mining client, stop the docker container running the Zilliqa Client on the CPU node: