Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Masternode setup guide
This guide assumes that you will setup so called COLD Masternode, where the server process is running on a remote Linux system (usually a rented VPS), and your funds are kept safely in your local offline wallet.
Local wallet (collateral transfer)
First, you need to make a transaction collateral of exactly 5000 coins. It should be kept untouched to receive masternode rewards.
- Start the IoTNexus wallet and wait for it to complete the blockchain synchronisation.
- Open Menu → Receiving addresses... and create a new address with label MN1 (or any one you like). Copy this address to the clipboard.
- Send exactly 5000 IOTN in a single transaction to the account address you generated in the previous step. This may be sent from another wallet, or from funds already held in your current wallet.
- Wait for at least 1 transaction confirmation.
- Go to Help/Tools → Debug console and type the following command:
- This command should print a collateral transaction hash and index, usually 0 or 1.
- Keep this info at hand and proceed to the remote VPS setup.
Remote VPS (masternode setup)
You have to find a Linux server which runs 24/7/365 and has a real IP address accessible from the outside. While it is possible to run it at home, the best way is to rent a VPS from a VPS provider. There are many providers, but we recommend Vultr which provides VPS starting from as low as $3.5 USD/month (IPv4 required). To simplify the setup we provide an install script which runs on Ubuntu Linux version 16.04, 17.10 or 18.04 and automates most of the setup for you. You should have a root user access with a password, and log in to the VPS using any ssh client (on Windows it could be putty, kitty or something similar).
Copy and paste the following commands to the root command prompt on Linux:
wget -N https://github.com/IoTNexus/iotnexus/raw/master/contrib/masternodes/iotnexus_masternode_install.sh bash iotnexus_masternode_install.sh
It will ask you if you are sure to setup a masternode. Type Y.
The script will check if it runs on a supported Ubuntu version, update your system, install necessary libraries, install IoTNexus software, configure it as a cold masternode daemon and ask you for your masternode private key. If you don't have one yet, just press Enter, and a new key will be generated for you.
Then you should have a script output similar to this one:
The most important thing is the green line with the data you have to put into your local wallet. So let's go back to it to finalise the setup.
Local wallet (masternode start)
First you should edit a masternode configuration file which is located in the coin data directory. On Windows it is in the "%APPDATA%/IoTNexus" directory. But you may simply use Tools → Open Masternode Configuration File to edit it.
- Copy the green line starting from mn1 from your Linux console and paste it into the end of masternode.conf file you just opened.
- Replace your-tx-hash and your-tx-index with the data from masternode outputs command you got earlier.
- Close editor and save the file.
- Close and restart your wallet.
- After restart ensure you have at least 15 confirmations of your collateral transaction. If you have less - please wait, or your masternode will not start.
- If you have the Masternodes tab - switch to it. If not, open wallet preferences and enable Masternodes tab from there. Your masternode should be visible on this tab.
- Open debug console (from Tools menu) and type there
masternode start-alias mn1
(replace mn1 with your masternode alias from the green line above, it can be any name but must be the same as you wrote in the masternode configuration file). It should report success.
Now your masternode should be running.
You may go to the Linux console and type there:
iotnexus-cli masternode status
If it shows:
Masternode successfully started
You should be fine and start receiving awards. The first award may be granted in an 1 to 24 hours depending on the number of masternodes in the network.