Code updates are essential to introduce new features, improve functionality and security. You will need to update your Wagerr wallet (clients) to keep up with the network and codebase created by the Wagerr Development team. Certain updates will require the user to update their wallet before a specific date, and failure to do so will result in their wallet losing connect to the best network.
Ensure that your local wallet is upgraded to the latest version. If it is not you will be unable to start your remote MN.
How to update your remote coin daemon on a VPS or dedicated server
This guide assumes you have root access when logging into the server, if you do not, some commands will need to be executed with “sudo” in front if you get a permission error.
Log in into the VPS
Shutdown the current wagerr daemon by running wagerr-cli stop in the prompt. This will work if your wagerr executables are located in the /usr/local/bin folder, otherwise change the directory to where they are located (usually ~/wagerr-VERSION_NUMBER/bin) with the command cd <directory> and run
You can view a list of sub directories with the command ls.
- On your local computer browse to https://github.com/wagerr/wagerr/releases and update to the latest release. Look for the green tag in the left column, “Latest Release.”
- Back on the VPS, copy the link corresponding to the binary you would like — we will be using the 64-bit Version 2.0.0 for Ubuntu as an example:
Download the binary by doing
- Extract the binary by doing
tar -xvf wagerr-2.0.0-x86_64-linux-gnu.tar.gz
- Copy the new binaries over to the /usr/local/bin folder by running
cp -R wagerr-2.0.0/bin/wagerrd wagerr-2.0.0/bin/wagerr-cli /usr/local/bin
- Run the new Wagerr daemon from any folder by the command,
FOR UPDATING FROM 1.x.x to 2.x.x ONLY
A fresh “Start” is required for all masternodes updating from v1.x.x to v2.x.x. On the LOCAL wallet, once updated and synchronized, switch to the Masternodes tab and click the “Start all” button. To start individual masternodes, select them one by one and click “Start alias.”
NOTE: It can take up to 2 hours for active time to show while the new masternode status is verified by the network.