Frequently Asked Questions

Got a question? We will add it.

Masternodes can be very daunting to setup and run for first time users. So we have put together a range of frequently asked questions along with terms you may find along the way of being a Syscoin Masternode Operator. Every bit helps right!?


The sentinel should be setup to check to see if your Masternode is pinging to the network. If your QT reports a SENTINEL_PING_EXPIRED, it could be a number of issues.

  • 1. QT is displaying incorrectly. Check your VPS to make sure you see "Masternode Successfully Started" via running "syscli masternode status" or "$ ~/syscoin-cli masternode status".
  • 2. You have just started your Syscoin Masternode, and will need to wait till the network acknowledges it. This can take anywhere from 10mins to 60mins.
  • 3. Crontab is not setup properly.
  • 4. Your Sentinel is not setup properly.

Requirements to Setup a Syscoin Masternode:
  • 100,000 Syscoin

  • A VPS installed with Linux with system specs;

  • MINIMUM REQUIREMENTS
  • Ubuntu 16.04 LTS x64
  • 1+ CPU
  • 2GB+ memory
  • 40GB+ SSD hard drive
  • Static IP Address 

  • RECOMMENDED REQUIREMENTS
  • Ubuntu 18.04 LTS x64
  • 4+ CPU
  • 2GB+ memory
  • 40GB+ SSD hard drive
  • Gigabit Network
  • Static IP Address 

You need to send 100,000 Syscoin in one transaction and it must be exactly 100,000 Syscoin. No more, no less. If you do not send the correct amount, it will not show up when you run "masternode outputs" in the debug console.


If you have just setup your Syscoin Masternode, or clicked Start Alias, you will need to wait till your Syscoin Masternode is eligible for Payouts, also known as Maturity. This eligibility period is worked out by the following calculation;

  • Number_Of_Masternodes * 2.6 / 60 = Eligibility Waiting Period in hours.
  • Eg. There are 500 Nodes: 500 * 2.6 / 60 = 21.6 hours.

If you have just setup your Syscoin Masternode, or clicked Start Alias, you will need to wait till your Syscoin Masternode is eligible for Payouts, also known as Maturity. This eligibility period is worked out by the following calculation;

  • Number_Of_Masternodes * 2.6 / 60 = Eligibility Waiting Period in hours.
  • Eg. There are 500 Nodes: 500 * 2.6 / 60 = 21.6 hours.

Secondly, once you are eligible to receive a reward, you may need to further wait in the queue for payouts. The average reward payout is worked out via;

  • Number_Of_Masternodes / 60 = Average Payout Time in Hours
  • Eg. There are 500 Nodes: 500 / 60 = 8.3 hours. (So you should on average receive a reward every 8.3 Hours)

No. Seniority is based on the Transaction ID TimeStamp and block height. So the only way you will lose Seniority, is if you move the 100,000 Syscoin to a new address, which will create a new Transaction ID.


If there is an issue with your Syscoin Masternode Server, there will be 3 Stages it goes through till you will need to Start Alias in the QT, which restarts your Maturity/Eligibility Period. From first going down till end, you have 10,800 Seconds or 3 hours to get your Syscoin Masternode VPS restarted.

  • 1. SENTINEL_PING_EXPIRED: Depending on your setup, your sentinel will check your Syscoin Masternode to see if it is ok, and talking to the network. This check happens from 60sec to 10mins. If your Syscoin Masternode is not pinging, your QT will return a SENTINEL_PING_EXPIRED. (please note, it could also mean a QT Display Issue)
  • 2. EXPIRED: Your Syscoin Masternode will go expired, when it hasn't pinged to the network in 7,200 seconds. You have 1 hour to get your Syscoin Masternode started.
  • 3. NEW_START_REQUIRED: Your Syscoin Masternode will need to be restarted on your VPS, and you will also need to Start Alias in the Syscoin QT. (please note, it could also mean a QT Display Issue)

To unblock your VPS if stuck at Block 87599 you upgraded too late and will need to unblock the blocks;
Type in VPS

$ syscoin-cli invalidateblock a12b6a265ded679a6ad6aba1eb7ad5cf1f5b08ca6d54375425b9c0b3e903a719
$ syscoin-cli reconsiderblock 742cee53abe4d75c442d5c5d7f74f2f6f2a28d37d3e82a3a17e9538e320f430e

You will have to wait a few minutes to load block 87600 because is really heavy then it just goes smoothly. If it stays on 87600 reboot your VPS or restart your QT.

If you used the manual install do the following;

$ ~/syscoin/src/syscoin-cli invalidateblock a12b6a265ded679a6ad6aba1eb7ad5cf1f5b08ca6d54375425b9c0b3e903a719
$ ~/syscoin/src/syscoin-cli reconsiderblock 742cee53abe4d75c442d5c5d7f74f2f6f2a28d37d3e82a3a17e9538e320f430e


If you used Justin's/ Doublesharps script:
Run this command and choose 'Y' to upgrade then enter,enter
$ bash <(curl -sL https://raw.githubusercontent.com/einalex/syscoin-scripts/master/masternode.sh)

To check Syscoin Version
syscli getinfo

To check Sentinel Version
syscli masternodelist json [vpsipaddress]

You do not need to update the QT wallet if you do not want to, but it is always best to run the latest Versions. All that is needed is to replace syscoin-qt.exe. There is no need to Restart your Node, it may change status to Sentinel Ping Expired for a short time (Less than an hour), but this is normal. DO NOT PRESS START ALIAS!


If you used BCNF's manual guide instead: Pressing Enter at the end of each line

$ ~/syscoin/src/syscoin-cli stop
$ cd ~/syscoin
$ git checkout master && git pull
$ ./autogen.sh
$ ./configure
$ make -j$(nproc) -pipe
$ ~/syscoin/src/syscoind

Update Sentinel if required

$ cd ~/syscoin/src/sentinel
$ git checkout master
$ git pull

To check Syscoin Version

$ ~/syscoin/src/syscoin-cli getinfo

To check Sentinel Version

$ ~/syscoin/src/syscoin-cli masternodelist json [vpsipaddress]

You do not need to update the QT wallet if you do not want to, but it is always best to run the latest Versions. All that is needed is to replace syscoin-qt.exe. There is no need to Restart your Node, it may change status to Sentinel Ping Expired for a short time (Less than an hour), but this is normal. DO NOT PRESS START ALIAS!


  • $ - signifies a new line
Upgrade to newest Master
  • $ ~/syscoin/src/syscoin-cli stop
  • $ cd ~/syscoin
  • $ git checkout master
  • $ git pull
  • $ ./autogen.sh && ./configure && make -j$(nproc)
  • ################################
  • Restart Daemon
  • $ ~/syscoin/src/syscoind
Stop Syscoind
  • $ ~/syscoin/src/syscoin-cli stop
Start Syscoind
  • $ ~/syscoin/src/syscoind
Check if your Syscoin Masternode is Synced
  • $ ~/syscoin/src/syscoin-cli mnsync status
Check your Syscoin Masternode Status
  • $ ~/syscoin/src/syscoin-cli masternode status
Check your Syscoin Masternode Information
  • $ ~/syscoin/src/syscoin-cli getinfo
Check current Syscoin Masternodes
  • $ ~/syscoin/src/syscoin-cli masternode count
  • ################################
  • In QT
  • Tools > Debug Console
  • $ masternode count

View your syscoin.conf
  • sudo cat /home/syscoin/.syscoincore/syscoin.conf
View your sentinel.conf
  • sudo cat /home/syscoin/sentinel/sentinel.conf
View the Syscoin user crontab which should contain:
  • # */10 * * * * /usr/local/bin/sentinel-ping
  • sudo crontab -u syscoin -l
Run a sentinel ping to speed up Qt syncing? why not!
  • sudo su -c "sentinel-ping" syscoin
View the sentinel-ping cron log, look for errors
  • sudo less /home/syscoin/sentinel/sentinel-cron.log
View the syscoind debug log, look for errors
  • sudo less /home/syscoin/.syscoincore/debug.log
Start and Stop the syscoind systemd service
  • sudo service syscoind stop
  • sudo service syscoind start
  • sudo service syscoind restart
Check that the syscoind process is running at the proper user
  • ps aux | grep [s]yscoind
Log out and back in or run the following to alias syscoind and syscoin-cli
  • source ~/.bashrc
Now the commands run as the syscoin user
  • syscoin-cli getinfo
  • syscoin-cli mnsync status
  • syscoin-cli masternode status
It is aliased to this shorter function
  • syscli getinfo
  • syscli mnsync status
  • syscli masternode status
If you really want to log in as the syscoin user
  • sudo su - syscoin

  • Enabled: Your Masternode is setup correctly and the network acknowledges it.

  • Expired: Your Masternode has not pinged in over 7,200 seconds and is not talking to the network. You will need to restart your Syscoin Masternode on your server - there is an issue.

  • Maturity: Your Masternode has a grace period before being eligible for receiving payouts when you broadcast it anytime to the network, via pressing Start Alias. This is defined by (Number_Of_Masternodes * 2.6 * 60 = grace period), which will give you the amount of time you will need to wait to start receiving payouts.

  • Masternode Genkey: It is a long string of numbers and letters which is used to setup a Masternode. Every Masternode needs it's own unique Masternode Genkey, and you cannot use this key for multiple Masternodes running simultaneously. This is not the same as your Private Key, and no funds are held in the Masternode Genkey.

  • Masternode Outputs: When you make a 100,000 Syscoin transaction, it will give an output which will be a long string of numbers and letters called a txid, followed by either a 0 or 1. This can be seen in your QT Debug Console by printing the following; masternode outputs

  • New_Start_Required: Your Masternode requires a 'Start Alias' in your Syscoin QT, to rebroadcast onto the network.

  • Rebroadcast Masternode: When you click Start Alias, this rebroadcasts your Masternode to the network. Please note that pressing Start Alias, restarts your Maturity.

  • Seniority: An initiative introduced by the Syscoin team to reward long term Masternode Runners. Seniority is based on the time you sent 100,000 Syscoin to an address. The network checks the timestamp of the transaction to determine your payout reward. Seniority increases at a rate of 3% every 4 months or every 175,200 Blocks, capped at 3 years.

  • Sentinel_Ping_Expired: Your Masternode has not pinged and is not talking to the network. It could mean that your sentinel is not setup correctly, your Syscoin Daemon is not running, or you have just started the alias in QT.

  • Static IP: When a device is assigned a static IP address, the address does not change. Masternodes require a static IP.

  • Transaction Hash aka txid: Transaction hash (txid) is an identifier used to uniquely identify a particular transaction. The hash of your transaction usually looks like a random set of letters and numbers. All on-chain transactions (depositing and withdrawing of funds) have a unique txid.

  • VPS: A Virtual Private Server (VPS) is a virtual machine sold as a service by an Internet hosting service. A VPS runs its own copy of an operating system (OS), and customers may have superuser-level access to that operating system instance, so they can install almost any software that runs on that OS

"A Community initiative to help out fellow Sycoiners" - bigpoppa

Donate: bigpoppa or SUZzZvWoKUqSHUAS8RjnhComZ4DUXfMjh1

Setup your Masternode TODAY!

Learn How Now