Masternode setup automated script for vps
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

c3x Masternode setup IMPORTANT NOTES

The development team of C3Xcoin decided to choose Nodemaster to give you an easy way to setup and manage your masternodes.

Recommended VPS:

Check out the easy step-by-step guide for the VPS provider vultr from the developer of Nodemaster that will guide you through the hardest parts.

THE FOLLOWING CONTENT IS NOT FROM c3x' DEVELOPMENT TEAM So please be aware that this service is a third party service but modified by us to fit into the C3Xcoin world !


The Nodemaster scripts is a collection of utilities to manage, setup and update masternode instances.

I am quite confident this is the single best and almost effortless way to setup different crypto masternodes, without bothering too much about the setup part.

About / Background

Many masternode crypto currencies only have incomplete or even non-existing instructions available how to setup a masternode from source.

Many people use binaries, end of with an insecure configuration or fail completely. This is obviously bad for the stability of the individual network.

After doing hundreds of masternode installations in the past two years, i decided to share some of my existing auto-install and management scripts with the community to work on a generalised & reliable setup for all masternode coins.

Comparing with building from source manually, you will benefit from using this script in the following way(s):

  • 100% auto-compilation and 99% of configuration on the masternode side of things. It is currently only tested on a vultr VPS but should work almost anywhere where IPv6 addresses are available
  • Developed with recent Ubuntu versions in mind, currently only 16.04 is supported
  • Installs 1-100 (or more!) masternodes in parallel on one machine, with individual config and data
  • Compilation is currently from source for the desired git repo tag (configurable via config files) Some security hardening is done, including firewalling and a separate user
  • Automatic startup for all masternode daemons
  • This script needs to run as root, the masternodes will and should not!
  • It's ipv6 enabled, tor/onion will follow


SSH to your VPS and clone the Github repository:

git clone && cd vps

Install & configure your desired master node with options:

./ -p c3x

Examples for typical script invocation

These are only a couple of examples for typical setups. Check my [easy step-by-step guide for vultr that will guide you through the hardest parts.

Install & configure 4 c3x masternodes:

./ -p c3x -c 4

Update daemon of previously installed c3x masternodes:

./ -p c3x -u

Install 6 c3x masternodes with the git release tag "tags/v3.0.5.1"

./ -p c3x -c 6 -r "tags/v3.0.5.1"

Wipe all c3x masternode data:

./ -p c3x -w

Install 2 c3x masternodes and configure sentinel monitoring:

./ -p c3x -c 2 -s


The script support the following parameters:

Long Option Short Option Values description
--project -p project, e.g. "pix" shortname for the project
--net -n "4" / "6" ip type for masternode. (ipv)6 is default
--release -r e.g. "tags/v3.0.4" a specific git tag/branch, defaults to latest tested
--count -c number amount of masternodes to be configured
--update -u -- update specified masternode daemon, combine with -p flag
--sentinel -s -- install and configure sentinel for node monitoring
--wipe -w -- uninstall & wipe all related master node data, combine with -p flag
--help -h -- print help info
--startnodes -x -- starts masternode(s) after installation

Troubleshooting the masternode on the VPS

If you want to check the status of your masternode, the best way is currently running the cli e.g. for $MUE via

/usr/local/bin/mue-cli -conf=/etc/masternodes/mue_n1.conf getinfo

  "version": 1000302,
  "protocolversion": 70701,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 209481,
  "timeoffset": 0,
  "connections": 5,
  "proxy": "",
  "difficulty": 42882.54964804553,
  "testnet": false,
  "keypoololdest": 1511380627,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

Help, Issues and Questions

I activated the "issues" option on github to give you a way to document defects and feature wishes. Feel free top open issues for problems / features you are missing here:

I might not be able to reply immediately, but i do usually within a couple of days at worst. I will also happily take any pull requests that make masternode installations easier for everyone ;-)

Management script (not yet implemented)

The management script release will follow within the next couple of days.

command description
nodemaster start c3x (all|number) start all or a specific c3x masternode(s)
nodemaster restart c3x (all|number) stop all or a specific c3x masternode(s)
nodemaster stop c3x (all|number) restart all or a specific c3x masternode(s)
nodemaster cleanup c3x (all|number) delete chain data for all c3x masternodes
nodemaster status c3x (all|number) systemd process status for a c3x masternode
nodemaster tail c3x (all|number) tail debug logs for a c3x masternode


  • provide my Dockerfile & Vagrantfile
  • write more test cases
  • implement a binary option (?)
  • output all supported cryptos as list within help


  • currently not fully idempotent

Ping me at for questions.