Updating to 12.2 - UsersUpgrading and downgradingHow to UpgradeIf you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Dash-Qt (on Mac) or dashd/dash-qt (on Linux).
For a detailed guide of the download, verification and installation process, see How to install Desire Core.
Downgrade warningDowngrade to a version < 0.12.2Because release 0.12.2 includes DIP0001 (2 MB block size hardfork) plus a transaction fee reduction and a fix for masternode rank calculation algo (which activation also depends on DIP0001) this release will not be backwards compatible after DIP0001 lock in/activation happens.
This does not affect wallet forward or backward compatibility.
======================================================================================================================================================
Updating to 12.2 - MasternodesPeriodically, the Desire Core development team will release updates to Desire. Since normal nodes rely on them for services and copies of the blockchain, masternodes are expected to update to new versions of Desire and Sentinel promptly. In some cases, hardware upgrades (more CPU, RAM or disk space, or even custom GPU hardware) may also be necessary. Not updating will eventually result in your masternode being removed from the payment queue. If you run a hosted masternode, your host will take care of updates for you. If not, the method of updating depends on how you installed Desire.
Minor version updates to Desire usually do not result in changes to the protocol version, while major version updates (e.g. from 0.12.1.5 to 0.12.2.0) will usually increase the network protocol version. If the protocol version did not change, you DO NOT need to restart your masternode if you complete the update within 60 minutes. If the protocol version did change, you must issue a start command from your wallet. Do not send start commands to your masternode if not necessary, as it may send you to the back of the payment queue.
Manual updateTo update Desire manually, log in to your server using ssh or PuTTY. First we need to stop Desire running:
~/.desirecore/desire-cli stop
To manually download and install the components of your Desire masternode, visit
https://github.com/lazyboozer/Desire/releases/tag/Desire-v.0.12.2.1 on your computer to find the link to the latest Desire Core wallet. Click Linux, then right-click on Download TGZ for Desire Core Linux and select Copy link address. Go back to your terminal window and enter the following command, pasting in the address to the latest version of Desire Core (0.12.2.1 in the example) by right clicking or pressing Ctrl V.
cd ~
wget https://github.com/lazyboozer/Desire/releases/download/Desire-v.0.12.2.1/desire-0.12.2.1-linux.tar.gz
Remove the old binaries from the working directory, extract the compressed archive, copy the new files to the directory and set them as executable:
rm ~/.desirecore/desired
rm ~/.desirecore/desire-cli
tar xfvz desirecore-0.12.2.1-linux.tar.gz
cp desirecore-0.12.2/bin/desired ~/.desirecore/
cp desirecore-0.12.2/bin/desire-cli ~/.desirecore/
Clean up unneeded files:
rm desirecore-0.12.2.1-linux64.tar.gz
rm -r desirecore-0.12.2/
Restart Desire:
~/.desirecore/desired
You will see a message reading "Desire Core server starting". We will now update Sentinel.
cd ~/.desirecore/sentinel/
git pull
If the protocol version changed during this update, you will need to issue a start command from your wallet. If you are using a hardware wallet, you can issue the start command by simply clicking the button in DMT. If you are using Desire Core wallet, update it to the latest version, then open the debug console and enter this command, where MN1 is the alias for your masternode:
masternode start-alias MN1
Monitor the status of your masternode as it starts up:
~/.desirecore/desire-cli getinfo
~/.desirecore/desire-cli mnsync status
~/.desirecore/desire-cli masternode debug
In particular, the last command should return the status "Masternode successfully started". If you see an error similar to "Invalid protocol version", then the protocol version has changed and you must send a start command from your wallet again. You can also monitor the status of your masternode from Sentinel. If Sentinel detects a functioning masternode, the following command should return nothing:
cd ~/.desirecore/sentinel
venv/bin/python bin/sentinel.py
Finally, you can check for your masternode by its collateral address using DesireNinja, or search the consensus list of masternodes using this command and entering your masternode IP address:
~/.desirecore/desire-cli masternode list full | grep
:
Some people are talking about some Sentinel that needs to be installed but can not find one for Windows , is there one for Windows or is it just something for Linux ? 