Version Info
ChainID: 201018
Version: 0.16.2
Git Commit: 430aecb60a61a10613835f4f014f0ecb5a72af5c
Binary Document: https://download.alaya.network/alaya/platon/0.16.2/alaya

1. Upgrade Instructions

If you are using the 0.16.1 version, please to Step 3 for the upgrade.

$ alaya version
Version: 0.16.1-unstable
Git Commit: 76b3b19b70d6c9a7f0dcc3119471613e3c84dc24

2. Upgrade Notice

The following notices are for the upgrade from 0.16.0 to 0.16.1. However, if you didn’t upgrade to 0.16.1, you could also directly upgrade to 0.16.2. Even so, these reminders would also be helpful.

2.1 About CPU, RAM and Disk

During the upgrade, part of the historical data will be migrated to the Freezer database. This will take up more CPU utility, which will return to normal upon completed data migration. When your device is rebooted after the upgrade, in rare cases, you may experience increased RAM use, which will also normalize once the data is migrated. The upgrade will also occupy more storage. For instance, the upgrade at block height 30,700,000 will take up 11GB additional storage space. For more details, please refer to Github releases.

RAM upgrade

During the upgrade and rebooting process, there is a small chance that validators using 8GB RAMs will suffer OOM due to the increased RAM use. To avoid the potential OOM problem, we recommend creating a swap partition or upgrading to 16GB RAM (if possible).

Add a swap partition

wget https://download.alaya.network/alaya/scripts/alaya_swap.sh
chmod +x alaya_swap.sh
./alaya_swap.sh

Notice:

The ‘alaya_swap.sh’ script provided in the document will carry out the following process: Where there is no swap partition, the script will create an 8GB swap partition; where the swap partition is smaller than 7GB, the script will expand it to 8GB; where the swap partition is larger than 7GB, the script will remain inactive.
Validators who carried out the upgrade without expanding their RAM could experience OOM, which will result in connection failures. For such users, the activation process will resume once their device is rebooted.

Disk expansion

The upgrade will take up 11GB additional disk space; where the storage is insufficient, we recommend expanding the disk capacity.

2.2 Incompatibility

After the present validator upgrade, you can no longer use the 0.16.0 version and the upgraded data for activation. Validators are advised to download the backup data we provided and have it stored on your validator PC before the upgrade. In case of failed activation after the upgrade, you will need to use the 0.16.0 version and data for activation.

The fast model backup data is 17GB big, at the block height of 33,280,041. In case of failed activation, the backup data will be used to replace the data/platon directory.

wget https://download.alaya.network/alaya/nodedata/0.16.0-fast-data.tar.gz
tar -xf 0.16.0-fast-data.tar.gz

3. Upgrade Instructions (upgrade without rebooting)

The following instructions are based on the Ubuntu18.04 system. You could complete the upgrade directly through the binary document or source code compiling. Please carry out the upgrade in strict accordance with the following procedures. If you need any help, feel free to reach out to us through our customer service.

Directly activate the binary document

# Make a binary backup
$ [[ -x /usr/bin/alaya ]] && sudo mv /usr/bin/alaya /usr/bin/alaya_`alaya version | grep ‘^Version:’ | awk -F “[ ,:,-]” ‘{print $3}’`
# Download the latest binary document
$ wget https://download.alaya.network/alaya/platon/0.16.2/alaya
# Use the latest version of alaya
$ chmod +x alaya
$ sudo mv alaya /usr/bin/alaya
# Check the version
$ alaya version
Version: 0.16.2-unstable
Git Commit: 430aecb60a61a10613835f4f014f0ecb5a72af5c

Source code compiling (The following is intended for previously complied environments. For new compiling, please refer to our official website.)

# Make a binary backup
$ [[ -x /usr/bin/alaya ]] && sudo mv /usr/bin/alaya /usr/bin/alaya_`alaya version | grep ‘^Version:’ | awk -F “[ ,:,-]” ‘{print $3}’`
# Compile the binary document
$ git clone https://github.com/AlayaNetwork/Alaya-Go.git — recursive
$ cd Alaya-Go 
$ git fetch — all
$ git checkout -b alaya-0.16.2 430aecb60a61a10613835f4f014f0ecb5a72af5c
# In case of missing go.sum entry for module, please use go mod tidy to remove unused dependencies and add the missing ones.
$ go mod download && make all
# Use the latest version of Alaya
$ chmod +x build/bin/alaya
$ sudo mv build/bin/alaya /usr/bin/alaya
# Check the version
$ alaya version
Version: 0.16.2-unstable
Git Commit: 430aecb60a61a10613835f4f014f0ecb5a72af5c

4. When to Reboot the Alaya Process

If the present node has staked before, please check whether it has been selected as a validator (Verifying) on the Alaya Blockchain Explorer. If so, please reboot the alaya process after the node exits from the validator model (switch from Verifying to Active)

The command below is for reference only. Validators should reboot the alaya process according to their own management approach.

nohup alaya --identity alaya-node --datadir ./data --port 16789  --rpcport 6789 --rpcapi "db,platon,net,web3,admin,personal" --rpc --nodekey ./data/nodekey --cbft.blskey ./data/blskey --verbosity 1 --rpcaddr 127.0.0.1 --syncmode "fast" > ./data/platon.log 2>&1 &

5. Version Statement

After the version statement is released, you could check the validator version on the Alaya Blockchain Explorer.

alaya_mtool declare_version --keystore $ALAYA_MTOOLDIR/keystore/staking.json --config $ALAYA_MTOOLDIR/validator/validator_config.json

Validators who never staked before could skip this step.
Where $ALAYA_MTOOLDIR is not defined, the absolute path should be completed according to the actual deployment.