0.Chain Information: #
Previous Wallet releases: v0.13.01
Latest Wallet Release: V0.14.01
1. Checklist Before You Start #
To upgrade your node you will need the following:
- Access to your control wallet on PC, MAC or Linux computer.
- Previous Unspent 2500 ABS transaction used from current v0.13.0.1 Masternode.
- Virtual Private Server (VPS) running Ubuntu 180.4 or 20.04.
- Access to your VPS using SSH, using such programs as Kitty or Putty.
2. Setup Collateral and Keys #
Download the last version of ABS wallet from the our website or from Github:
From Website:
https://absify.me/wallets/
Full Release and wallets are also available here:
https://github.com/absolute-community/absolute/releases
3. Removal of Masternode Private Key #
You can keep using your existing Collateral Tx, Collateral Tx Index and BLS Private Key. In this release. Masternode Private key which was generated using Masternode genkey has been retired and therefore this can be removed from your absolute.conf.
4. Your VPS Server #
Use Putty or Kitty to connect to your VPS via SSH. Make sure you have at least Ubuntu Linux v18.04 installed.
5. Upgrade Masternode using upgrade script #
This script is designed for users that have used our install script. Manually configured nodes with non-default configurations and paths can’t be upgraded with this script. If, this is the case follow the manual guide in step 5a.
This script will detect your configuration and stop daemons, download new binaries, upgrade wallet binaries, update sentinel and restart the daemons.
Make sure you are the root user, if you use a different user to login to your VPS then switch the current user to root and navigate to /root folder with this shell command:
cd /root
Download the install script with this command:
wget https://bit.ly/abs_mn_wallet_upgrade -O abs_wallet_upgrade.sh && chmod +x abs_wallet_upgrade.sh
Start the install script with the next command.
./abs_wallet_upgrade.sh
Make sure that the script run without errors!
Script will upgrade the wallet of running nodes, so no need to stop the daemons before running it.
Once complete, the upgrade is complete there is no need to continue to step 6a and 6b
6a. Manual Masternode upgrade #
From your shell (or putty).
Go to your home folder or install folder
cd $HOME
hit ENTER Stop MN Stop script installed MN
systemctl stop absd
If your install pre-dates our install scripts, use:
absolute-cli stop
Wait 30 Seconds before continuing..
Download the last release:
wget https://github.com/absolute-community/absolute/releases/download/v0.14.0.1/absolutecore-0.14.0-x86_64-linux-gnu.tar.gz
Delete Absolute directory:
rm Absolute -R
Decompress
tar -zxvf absolutecore-0.14.0-x86_64-linux-gnu.tar.gz && mv "absolutecore-0.14.0/bin" "$HOME/Absolute"
Modify your absolute configuration file
Although optional, we would recommend removing your masternodeprivkey line from your absolute.conf.
Change directory to .absolutecore:
cd .absolutecore
Edit your absolute.conf with Nano:
nano absolute.conf
Remove masternode private key :
Remove the masternodeprivkey line from your absolute.conf file.
It is important that the next line after your BLS private key is maintained as being blank.
Leave masternode=1 in place.
Save and exit Nano
Save with:
Ctrl +O
Exit with:
Crtl +X
Restart your MN
Start scripted installed MN
systemctl start absd
If your install pre-dates our install scripts, use:
absoluted -daemon
6b. Update Sentinel to V1.4 #
You must update Sentinel to V1.4 to allow the new governance and protocol changes to logged correctly.
The default location of Sentinel is normally:
$HOME/.absolutecore/sentinel
In this directory, run the following command:
git pull
This should automatically update Sentinel to use v1.4. An issues with this command, consider reinstalling Sentinel using this guide here