DRIP is an innovative new POS (Proof Of Stake) coin featuring complete privacy with Mixinxg + zDrip as well as a really cool upcoming feature “Send Privately With Bitcoin”. That feature alone I think turns this POS coin into a GEM in a time where POS only coins are not doing much to innovate.
Want to know more? JMILLA has written a great article on it here: https://jmilla.tech/spend-masternode-rewards-privately-as-bitcoin-with-drip
There are two ways to setup a Masternode for DRIP, manually or with installer. This is the installer way using Vultr as the VPS provider. At this time 4 Masternodes works just fine on their $5/mo plan, this may change as the network becomes busier. You can grab a Vultr VPS from here. (yes that is an affiliate link, thanks for your support if you use it 🙂 )
DRIP Masternode Preparation
Things you need:
- DRIP Core Wallet: https://www.dripcoin.tech/wallets/
- A VPS: Vultr
- 10k Drip for each node
- An SSH client such as Putty
DRIP Wallet Masternode Setup
Important: Disable auto-minting and check zDRIP balance. If some of your balance intended for the MN was auto-minted to zDrip you will need to convert it back to DRIP and send it to yourself.
First we will create a masternode key and address for each one that we will be making (this guide is for two). In the wallet open up the console: Tools > Debug Console. For masternode private key type:
Note: Generate one key for each MN.
For the two masternode addresses:
Sending Masternode Collateral
Send exactly 10k to each address. When you add the send to address the “Pay To” field should auto fill with the correct MN name.
Now on your PC wallet still go to Tools > Open Masternode Configuration File. The format of the line to add is:
alias IP:port masternodeprivkey collateral_output_txid collateral_output_index
- alias is your MN name when making the address, example ours is MN1 and MN2
- IP: Your VPS public IPv4 (available in your panel)
- port: 21461
- masternodeprivkey we generated above
- The last two are obtained by running “masternode outputs” in your wallets console
Update The Wallet Configuration File
Go to Tools > Open Wallet Configuration File and add the following, changing the name and password as you like.
rpcuser=long random username
rpcpassword=longer random password
Save any changes, close, and restart the wallet.
DRIP Masternode VPS Setup
Login with SSH utility of your choice such as putty and run:
sudo apt-get update && apt-get upgrade
Now if you are like me you have many different servers and I usually have multiple SSH sessions only, setting a friendly hostname is a good way to easily tell which server your SSH session is on. It is recommended to make the hostname one that resolves, example:
sudo hostnamectl set-hostname guide.virtopia.ca
Verify the change:
sudo cat /etc/hostname
You should see your new hostname. Don’t forget to add an a-record for it where you manage your DNS.
Grab And Run Masternode Install Script
git clone https://github.com/DRIP-Project/vps.git && cd vps
./install.sh -p drip -c 4
This will install config files for 4 MN from the start. You do not need to set them all up, it just makes adding more later easier. All that is needed is to add your masternode private key
Save, exit, and then run command:
This should start your MN services for the two files that you added the master key in. You can check with:
service drip_n1 status
service drip_n2 status
This should return “Active (running)”. If it does not try:
service drip_n1 start
Check status again.
Now in your local wallet open the “Masternodes” tab, right click and “Start Alias“. If successful you should get a notice and status will change to “Enabled“. You do not need to leave your local wallet running once the Masternodes are starting, as long as the daemons are running on the VPS you are getting paid.
You can pull all types of information from the daemons using drip-cli, you need to make sure to define the daemons conf file that you want information on, like so:
drip-cli -conf=/etc/masternodes/drip_n1.conf help
Additional Stuff Like Monitoring And Alerts
If your Masternodes are not running you are not making $ so uptime and knowing if there is an issue or potential issue is important. Here I use monit for monitoring system load (CPU, RAM, and disk space). These things are important as an overloaded system will cause instability and could even cause you increased orphans as well as an inaccessible server if you run out of disk space.
The script already sets up monitoring and service restarts VIA systemd so that is well taken care of. If you are curious you can find the config files in “/etc/systemd/system”.
Note: If using Vultr you need to submit a ticket asking for smtp (port 25) to be unblocked. If it is a new account they will most likely make you wait about 14 days.
sudo apt-get -y install monit
Configure Main Monit Config (monitrc)
Find “# set mailserver mail.bar.baz,” and change to:
set mailserver localhost
Find “# set alert [email protected]” and change to:
set alert [email protected]
Add to the bottom of the file:
check filesystem datafs with path /dev/vda1
if space usage > 85% then alert
This will email alert you if space is more then 85% used. /dev/vda1 you may need to adjust, you can check partitions with fdisk -l
check system $HOST
if loadavg (5min) > 1 then alert
if cpu usage > 95% for 10 cycles then alert
if memory usage > 75% then alert
if swap usage > 25% then alert
Self explanatory, if you have a larger VPS with more CPU cores you can adjust it. For example for 2 cores change 1 to 2 on “if loadavg (5min) > 1 then alert”.
Save and exit, and do:
You need to have either sendmail or postfix installed for Monit to send mail notifications. Check if you have either installed:
sudo apt-get install postfix
When asked choose “Internet Site” and for domain use the hostname that you set at the start of the VPS setup. Check that Postfix is running:
service postfix status
If not running then do:
service postfix start
Check again to make sure running. One last step is to configure the UFW firewall to allow port 25 (tcp) out:
ufw allow out 25
To test that notifications are working you can set the disk alert amount in the monitrc file to something like 1% and do “monit reload” you should get an email.
That is it! Hopefully some of you find this useful and if you want to help supply my coffee habit send me some DRIP 🙂