the 5 minute masternode setup

A lot of question i receive on a daily basis are from masternode fans looking for an easy to follow, non-technical guide that isn’t as clumsy as 99% of the articles out there.

This article is for your and i hope you will enjoy reading it. If you follow my instructions, you will have a reasonably secure and scalable setup. It’s quite similar to my XZC article, but also with the controller side in mind.

These are the essential bits from the longer version of this article. This shorter version mostly consists of screenshots, accompanied by a explanatory comment. From start to finish.

It’s meant to illustrate a typical masternode setup . The overall process is the same for almost every coin. So even you don’t own any $KLKS, the general system can be applied to 99.9% of masternode setups.

You need the following set of tools to start:

Start by downloading my VM setup scripts for the kalkulus controller. You can find it on my github account. In a console (for Windows use Git-Bash), clone this repository first:

Open the cloned directory “kalkulus-masternode-controller” and execute the one and only required command to create the environment:

Make a note of the final script output. It will list your collateral deposit address and the masternode privatekey for your convenience. All of this is done locally.

Connect to your masternode w/ putty. The first thing to do on your VPS is to clone my git nodemaster script:

This is really easy. Use the ./install.sh script with “klks” and “-n 4” as options , (ipv4 networking selected).

This will take a while and take care of all that annoying stuff you have to do normally when compiling & setting up a masternode.

The script downloads, compiles and configures the system now. This will usually take between 15–30 minutes depending on the internet connection and cpu/ram of the VPS. So after another cup of coffee, kalkulus should be compiled and ready to be configured.

We need to fill 2 variables here:

When you are done, start the masternode to let it sync. The command to do this on the VPS is:

Now all that’s left is to start your masternode from the masternodes tab in your wallet. Congrats, your masternode setup is complete!

Your controller VM doesn’t have to run 24/7 btw. For most setups i did in the past, monitoring the incoming rewards and a check for wallet updates every 1–2 weeks is enough to keep up with new developments.

Still some questions? Check the longer version of this article and/or ping me at marsmensch@protonmail.com.

Thanks for reading that far & have a lot of fun!

If this guide helped you in any way, please contribute some feedback. BTC donations also welcome and never forget:

Have fun, this is crypto after all!

Related posts:

Are you looking for a simple way to create engaging and professional Pins on Pinterest? … Then Pin Builder is the tool for you. Pin builder is a set of tools available for business accounts that…