Mandatory Review of Your Nodes (2021-04-16)

Support
#1

Hi Syscoin Community,

It is mandatory for masternode owners who host their own masternodes, and users of Syscoin QT or Spark to make sure all their nodes are on the right block. This post provides instructions to check if your node(s) are correct, and simple steps to fix them if they aren’t.

Visit our github if you would like an in-depth explanation of the issue (same issue as December 5th, related to Dash code, and already resolved in Syscoin 4.2 LUX due for release soon): https://github.com/syscoin/syscoin/issues/414 31

If your masternodes are managed by a third-party service such as AllNodes, you don’t need to do anything for them! However, you should still check your QT or Spark wallets. In either case, continue.

First check that your nodes have the correct chain tip. To do this you will use our explorer: https://sys1.bcfn.ca/

Look for the latest block on the explorer and check this against your nodes by doing the following in QT Console, Spark Console or PuTTY;

For QT or Spark

getblockcount

For VPS

syscoin-cli getblockcount

If your node is correct, its blockcount will match or be fairly close to what is shown as the most recent block by the explorer. In that case there is nothing more you need to do for that node.

If that is not the case, e.g. your node’s blockcount is significantly lower than the explorer’s by more than 100 blocks, you will need to do the following:

For VPS

syscoin-cli invalidateblock fa59f76fa7516030d03eca7c2302fe53faedc8b702c93161b5236b66c4dc1816

sudo service syscoind stop (or syscoin-cli stop if you get an error starting)

sudo su -c 'syscoind -reindex' syscoin

syscoin-cli addnode 54.214.167.210 add && syscoin-cli addnode 207.180.198.20 add && syscoin-cli addnode 173.212.253.105 add && syscoin-cli addnode 167.86.123.23 add

Check your blocks again via the getblockcount command:

syscoin-cli getblockcount

If this still does not work please restart from the top and do again. The issue will be that your node is still attaching to bad peers. As more do this, the less issues nodes will have connecting to good peers.

For QT or Spark Console

invalidateblock fa59f76fa7516030d03eca7c2302fe53faedc8b702c93161b5236b66c4dc1816

Restart QT/Spark

Check your blocks again via the getblockcount command.

If this does not work, you may need to add some peers;

addnode 54.214.167.210 add

addnode 207.180.198.20 add

addnode 173.212.253.105 add

addnode 167.86.123.23 add

Then restart QT/Spark.

Check your blocks again via the

getblockcount

command.

You do not need to reinitialize your Masternode unless it reflects status “New Start Required”

If this still does not work please restart from the top and do again. The issue will be that your node is still attaching to bad peers. As more do this, the less issues nodes will have connecting to good peers.