Blockchain technology provides many different ways to earn income. This is the main reason why so many investors are drawn to this space. While most of the bitcoin and altcoin investments require active participation in the market, there are ways to earn passive income. An example would be to run a masternode.
This article is a step-by-step beginner’s guide geared towards individuals with little to no knowledge of programming who want to set up a masternode.
What Are Masternodes?
Masternodes are nodes that perform special functions that “standard” nodes do not. To reward masternode operators for providing added services to a blockchain network, they are receive financial rewards built a collateral-based system.
Masternodes come in different shapes and sizes but the setup process is similar for the majority of “masternode coins.”
In this masternode guide, we will guide you through the process of setting up a DASH masternode. Dash (DASH) is one of the most popular masternode coins in the market.
How To Set Up DASH Masternode
1. Set up your VPS
A VPS (Virtual Private Server) is an installation of an OS (operating system) running inside a virtual machine. This is needed in order to run numerous systems on a single physical server, which is more efficient and much cheaper than running it from a home desktop computer.
Vultr offers a variety of options for memory, storage capacity, server location. On top of that, it is affordable, reliable, and likely has the best user experience.
First create an account and add credit. Then, proceed to the Servers menu item on the left and click +. Select your server location:
The server will run on Linux, so choose Ubuntu 18.04 x64 as server type.
At least 2GB of memory is required so choose the appropriate server size.
Input your server hostname and label. “Dashmn1” will be used in this example.
Wait for Vultr to finish installing your server for a few minutes. Once complete, click Manage and save the IP address, username, and password.
2. Set up your operating system
Now we connect to your new server.
On Windows, we need to download PuTTY. Be sure to select the appropriate installer that matches your system.
On Mac or Linux, we can ssh directly from the terminal by typing:
ssh [email protected]<server_ip>
After installing PuTTY, run the app from your Start Menu. Enter the IP address of the server in the Host Name field and click Open. You may see a certificate warning, since this is the first time you are connecting to this server. Simply click Yes.
Log in to your server with the user root and password supplied by your hosting provider.
The root password must be changed as soon as possible for security purposes. Copy and paste this command to the PuTTY window:
Enter a new password. Next we will create a new user with the following command, replacing <username> with a username of your choice:
You will be prompted for a password. Input your new password and be sure to save it.
Now, while still as root, we will update the system from the Ubuntu package repository by inputting the commands:
The system will show a list of upgradable packages. Press Y and Enter to install the packages. Then, input:
apt install ufw python virtualenv git unzip pv
Press Y and Enter. Then input:
ufw allow ssh/tcp
ufw limit ssh/tcp
ufw allow 9999/tcp
ufw logging on
Press Y and Enter. Then input:
fallocate -l 4G /swapfile
chmod 600 /swapfile
Add the following line at the end of the file (press tab to separate each word/number), then press Ctrl + X to close the editor, then Y and Enter save the file.
/swapfile none swap sw 0 0
For security measures, we will install fail2ban and disable root login over ssh.
For fail2ban, input: apt install fail2ban
Create a new configuration file by inputting: nano /etc/fail2ban/jail.local
And paste in the following configuration:
enabled = true
port = 22
filter = sshd
logpath = /var/log/auth.log
maxretry = 3
Then press Ctrl + X to close the editor, then Y and Enter save the file. Restart and enable the fail2ban service by inputting:
systemctl restart fail2ban
systemctl enable fail2ban
Next, open the SSH configuration file to disable root login over SSH:
Locate the line that reads PermitRootLogin yes and set it to PermitRootLogin no. Directly below this, add a line which reads AllowUsers <username>, replacing <username> with the username you selected above. Then press Ctrl + X to close the editor, then Y and Enter save the file.
Reboot the server by inputting: reboot now
3. Send the collateral
Running a Dash masternode requires 1000 DASH as collateral. A masternode can be registered using the official Dash Core wallet. A hardware wallet is another option, and has enhanced security.
In this example, we will use a software wallet as it is more commonly used.
First, you must download the Dash Core Wallet. Then, you open it and wait for it to complete synchronization. It should appear this way when fully synchronized:
Click Tools > Debug console to open the console. Input this command into the console to generate a new Dash address for the collateral:
Save the collateral address since we will need it later.
For security purposes, let’s encrypt the wallet by selecting Settings > Encrypt wallet. Save your password and make sure nobody else knows about it.
Back up your wallet file by selecting File > Backup Wallet. Save the file to an external hard drive or other storage physically separate from your computer. So, if anything happens to your hardware, you can still access your funds.
Now send exactly 1000 DASH in a single transaction to the collateral address you generated in the previous step. Once it’s done, view the transaction in a blockchain explorer by searching for the address.
You will need 15 confirmations before you can register the masternode, but you can continue with the next step at this point already: generating your masternode operator key.
4. Install Dash Core
Dash Core is the software that runs the Dash Core graphic user interface wallet and Dash masternodes. It is also behind the Dash blockchain.
Open PuTTy again and connect using the username and password for your new, non-root user.
To make our lives easier, let’s install Dash Core using an automated installation method dashman. To install Dash using dashman, input the following commands after logging in:
git clone https://github.com/moocowmoo/dashman
(press Y and Enter to confirm)
Dashman will download the latest version of Dash Core for your system, as well as an initial snapshot of the blockchain to speed up the bootstrapping process. Next download and install Sentinel, which is required for masternodes at version 0.12.1 or higher:
~/dashman/dashman install sentinel
Your system is now running as a standard Dash node, and is busy completing synchronization with the blockchain. Since dashman does not automatically restart your masternode in the event of a system error, add a check function to crontab to make sure it checks every minute to ensure your masternode is still running:
Choose nano as your editor and input the following line at the end of the file, after the line for sentinel:
* * * * * pidof dashd || ~/.dashcore/dashd
Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. Check the sync status and wait until all blockchain synchronization and the 15 confirmations for the collateral transaction are complete:
5. Register your masternode
Identify the funding transaction
First, we need to find the txid (transaction ID) of the transaction. Click Tools > Debug console and enter the following command:
This should return a string of characters similar to the following:
“16347a28f4e5edf39f4dceac60e2327931a25fdee1fb4b94b63eeacf0d5879e3” : “1”,
The first long string is your collateralHash, while the last number is the collateralIndex.
Generate a BLS key pair
A public/private BLS key pair is required to operate a masternode.
If you are using a hosting service, they may provide you with their public key, and you can skip this step.
If you are hosting your own masternode, generate a BLS public/private keypair in Dash Core by clicking Tools > Debug console and entering the following command:
Save these keys (write them down if possible) and store them in a safe place.
Add the private key to your masternode configuration
The public key will be used in the following steps. The private key must be entered in the dash.conf file on the masternode. Log in to your masternode using ssh or PuTTY and edit the configuration as follows:
The editor appears with the existing masternode configuration. Add or uncomment these lines in the file, replacing the key with your BLS private key generated above:
Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. We now need to restart the masternode for this change to take effect.
Enter the following commands, waiting a few seconds in between to give Dash Core time to shut down:
Prepare a ProRegTx transaction
A pair of BLS keys for the operator were already generated above, and the private key was entered on the masternode. The public key is used in this transaction as the operatorPubKey.
First, we need to get a new, unused address from the wallet to serve as the owner key address (ownerKeyAddr). This is not the same as the collateral address holding 1000 Dash. Generate a new address as follows:
This address can also be used as the voting key address (votingKeyAddr). Alternatively, you can specify an address provided to you by your chosen voting delegate, or simply generate a new voting key address as follows:
Then either generate or choose an existing address to receive the owner’s masternode payouts (payoutAddress). It is also possible to use an address external to the wallet:
You can also optionally generate and fund another address as the transaction fee source (feeSourceAddress). If you selected an external payout address, you must specify a fee source address. Either the payout address or fee source address must have enough balance to pay the transaction fee, or the final register_submit transaction will fail.
The private keys to the owner and fee source addresses must exist in the wallet submitting the transaction to the network. If your wallet is protected by a password, it must now be unlocked to perform the following commands. Unlock your wallet for five minutes:
walletpassphrase yourSecretPassword 300
We will now prepare an unsigned ProRegTx special transaction using the protx register_prepare command. This command has the following syntax:
protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr
operatorPubKey votingKeyAddr operatorReward payoutAddress (feeSourceAddress)
Open a text editor such as notepad to prepare this command. Replace each argument to the command as follows:
collateralHash: The txid of the 1000 Dash collateral funding transaction
collateralIndex: The output index of the 1000 Dash funding transaction
ipAndPort: Masternode IP address and port, in the format x.x.x.x:yyyy
ownerKeyAddr: The new Dash address generated above for the owner/voting address
operatorPubKey: The BLS public key generated above (or provided by your hosting service)
votingKeyAddr: The new Dash address generated above, or the address of a delegate, used for proposal voting
operatorReward: The percentage of the block reward allocated to the operator as payment
payoutAddress: A new or existing Dash address to receive the owner’s masternode rewards
feeSourceAddress: An (optional) address used to fund ProTx fee. payoutAddress will be used if not specified.
Note that the operator is responsible for specifying their own reward address in a separate update_service transaction if you specify a non-zero operatorReward. The owner of the masternode collateral does not specify the operator’s payout address.
Example (remove line breaks if copying):
Next, we will use the collateralAddress and signMessage fields to sign the transaction, and the output of the tx field to submit the transaction.
Sign the ProRegTx transaction
We will now sign the content of the signMessage field using the private key for the collateral address as specified in collateralAddress. The command takes the following syntax:
signmessage collateralAddress signMessage
signmessage yjSPYvgUiAQ9AFj5tKFA8thFLoLBUxQERb yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN|0|yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip|yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg|ad5f82257bd00a5a1cb5da1a44a6eb8899cf096d3748d68b8ea6d6b10046a28e
Submit the signed message
Your masternode is now registered and will appear on the Deterministic Masternode List after the transaction is mined to a block.
You can view this list on the Masternodes -> DIP3 Masternodes tab of the Dash Core wallet, or in the console using the command protx list valid, where the txid of the final protx register_submit transaction identifies your masternode.
At this point you can go back to your terminal window and monitor your masternode using ~/dashman/dashman status status, by entering ~/.dashcore/dash-cli masternode status or using the Get status function in DMT. The final result should appear as follows:
Now you can finally log out of the server by typing exit.
Congratulations! You now have a masternode running.
Masternode Hosting Services
For those who do not want to go through all the trouble of following this guide, an alternative option would be to utilize masternode hosting services like ZCore and Clicknode. These are easy-to-use services that will effectively run your masternodes on your behalf for a fee.
Masternodes allow the network to remain honest and valid while incentivizing its operators to participate by giving them financial rewards. They are a great way to potentially earn passive income in the altcoin space.
To learn more about how to potentially make money in the digital asset markets, be sure to subscribe to Bitcoin Market Journal.