Jump to content
Sign in to follow this  

Manual upgrade of a Masternode to v1.2.0.0

Recommended Posts


People that should not use this guide
Please do not use this guide if you have your masternode with any of our masternode hosting providers as listed below. Those masternodes will be updated by your hosting service. You might have to start the masternode after they announce that they have completed the update:

  • Stakinglab.io
  • CryptoHashTank
  • Nodehub.io
  • GTM
  • Snode
  • Maiks masternode hosting service
  • BitHostLive
  • Pecunia
  • Apollon 

Detailed manual upgrade instructions

This guide tells you in detail, which steps you should follow for updating your masternode running on a VPS. Alternatives are creating a new VPS and installing the masternode from scratch or rerunning the install script on an existing masternode. Remember to disable the masternode first using this command:

systemctl stop PAWS

Now... over to the instructions for a manual update:

  1. Login to the VPS using putty or any other ssh program that you normally use as described in the installation guide.
  2. You should now have a window with a black screen like the one shown below:

  3. The first thing you do, is stop the masternode service running.

    systemctl stop PAWS

  4. This step is required for upgrades after the fork was activated. We now need to delete the old blockchain database. This will take time, as the blockchain needs to be downloaded from the network:

    rm -r .paws/blocks/ 
    rm -r .paws/chainstate/

  5. The next thing we do is download the new software:

    wget https://github.com/pawsfund/PAWS-Core/releases/download/v1.2.0.0/paws-

    This should output some lines, that indicate the file is being downloaded.
  6. Once the prompt returns, we need to unzip the archive we just downloaded. Do the following:

    unzip paws-
  7. You should now have 3 more files in your home directory. Please do the following to make them executable:

    chmod +x paws*
  8. The files now need copying over the existing executables in /usr/local/bin. We do that as follows:

    mv paws-cli /usr/local/bin
    mv pawsd /usr/local/bin
    mv paws-tx /usr/local/bin

  9. We are now ready to start the masternode service for the first time:

    systemctl start PAWS
  10. We need to restart the masternode AFTER the service has started. Make sure that the wallet is fully synced before proceding by making sure that the number returned by the below command is the same as the current blockheight on http://chain.paws.fund:

    paws-cli getblockcount

    This will take time, depending on how fast your internet connection is. Repeat the above command, to check the current blockcount. Once it is in sync, proceed.
  11. Once the masternode is in sync, do the following command!:

    paws-cli stop

    What happens here, is that we stop the wallet via the commandline, but since the wallet is running as a service the service will start it again once it detects it is shutdown. So this really means that the wallet is stopped, and started immediately after.

  12. You now have to open your local wallet and start the masternode, just like you did with your first installed the masternode. Chances are that it says it is enabled already, and this is because the wallet is really slow to detect that a masternode has going offline.This is a good thing, as it might prevent you from having to wait the initial 18 hours before getting your first reward.

    So open the local wallet, and start the masternode by selecting it and clicking "Start Alias". If you get the invalid ip error go into:

    Tools -> Debug Console and type the following: 
    startmasternode alias 0 YOURMNNAME

  13. The final step is to check if the masternode has started. On the masternode (VPS) type the following command:

    paws-cli getmasternodestatus

    It should return something like:

        "txhash" : "f1355f7864ff97f395b5b51a10ec5ckpe82b0f2c6170b6956ee81f264137821b",
        "outputidx" : 0,
        "netaddr" : "",
        "addr" : "PPUg6iQtMrHjhaYqxYrtFaxMjmcqLzC7pt",
        "status" : 4,
        "message" : "Masternode successfully started"

    Status 4 means you are good to go. If it is not working... repeat the steps from step 10. This might need repeating 1-2 times.

Any problems let us know here on the forum or on Discord.

The PAWS Team

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.