SYSCOIN MANDATORY UPGRADE 3.1.0.0

THIS HAS NOW BEEN SUPERSEDED BY 3.1.x.0 PLEASE USE THIS GUIDE NOW AND NOT THIS ONE .

https://medium.com/@bittyjohn1954/syscoin-upgrade-3-1-x-0-d4884e8cef9c

This upgrade applies to Syscoin QT, Blockmarket and Masternodes but Masternodes are only covered here.

For the latest versions visit Github.

See below for Mandatory Masternode Upgrade Instructions to 3.1.0.0 this also includes updating your sentinel to 1.1.1 if you have not already done so.

This may also be a good time to upgrade your VPS to 18.04 LTS if you wish, do not do it through putty but through your VPS providers site.
This will mean a reinstall of the O/S which will wipe all your data but your IP should remain the same. If you choose to do this when running Justins script it will be a new install not update and you use the same MN key as you have now for that MN.

If you did it manually you will have to install everything again on the VPS only, might also be a good time to switch to using the script. (https://medium.com/@bittyjohn1954/syscoin-3-with-masternodes-cold-setup-unofficial-guide-assuming-a-clean-install-508d50c908d)

This upgrade is required before Block 175000 or your node will not sync afterwards and you will stop receiving rewards, please read release notes for further details.

Login to the vps

*If you used Justin’s/ Doublesharps script:*

To check Sentinel Version

syscli masternodelist json [vpsipaddress]

Stop Syscoind

sudo service syscoind stop

Run the command below and choose ‘Y’ to upgrade then enter, and then select Y or N to sentinel upgrade as required and press enter, then press enter when asked for the branch.

If this is not an upgrade you will need to enter your MN key when prompted, otherwise just accept the values shown.

bash <(curl -sL doublesharp.com/sysmasternode)

When finished the script will start Syscoind automatically.

To check the Syscoin Version and protocol.

syscli getinfo

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

There are 2 methods of updating if you did it manually.( Update only)

1. Press 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

To check Sentinel Version

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

Install if required

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

2) Or you can use this code created by Locutus

This will update your Manual Install setup, all in one line

cd $home && curl -sL https://raw.githubusercontent.com/locutus75/syscoinscripts/master/offlineupdatescript.sh --output $HOME/offlineupdatescript.sh && chmod u+x $HOME/offlineupdatescript.sh && ./offlineupdatescript.sh

This is what it does:
- creates a ~/temp folder
- builds the latest syscoincore from github in this temp folder
- builds the latest sentinel from github
- copies current sentinel.conf
- stops syscoincore
- moves old ~/syscoin folder to ~/temp/syscoin-previous
- moves new ~/temp/syscoin to ~/syscoin
- starts syscoincore

This way, there is almost no downtime.

So you end up with a new version and also you have the old one backed up in ~/temp/syscoin-previous.

Check your version with

~/syscoin/src/syscoin-cli getinfo

If satisfied, you may remove your backup folder with this command

rm -rf ~/temp/syscoin-previous

There is no need to Restart your Node, it may change status to Sentinel Ping Expired for a short time (Less than an hour)

Please note then when looking at the Masternode details in QT and on your VPS, Sysnode.info or Nodecheck.io the protocol version shows the minimum version (70221) not the current (70222). Current version is shown in `getinfo`