Software upgrades allows any cosmos based network to soft-upgrade the network to a new version. In general, for any state breaking changes, there will be a migration script to migrate the chain data and we generally hard fork the blockchain network. For soft-upgrades,
x/upgrade module has a special function called upgrade-handler which handles all the migrations required. Here is the upgrade handler for
It handles 2 migrations:
Fix vesting account delegation issues
Set staking historical events to
10000, which is required for IBC.
For more details on soft-upgrades click here
Nothing, just sit back and relax. The
software-upgrade proposal will force the binary (current version,
akash-v0.10.x) to halt at specified height, i.e., 455200
akash status 2>&1 | jq -r '.SyncInfo.latest_block_height'
It should be 455199
sudo service akash stop
Option-1: Using pre-build binaries
Download pre-built binaries from: https://github.com/ovrclk/akash/releases/tag/v0.12.1
Option-2: Build from source
git clone https://github.com/ovrclk/akashcd akashgit fetchgit checkout v0.12.1MAINNET=true make install
$ akash version --longname: akashserver_name: akashversion: v0.12.1commit: 53182423582000bf63fa674245a5008c5b466bf1build_tags: osusergo,netgo,ledger,mainnet,static_buildgo: go version go1.16.1 linux/amd64...
sudo service akash start
That's it. You should be able to check new blocks coming up.
Since we are not hard-forking the network, it should be simple to revert back.
Stop akash service
cd akashgit checkout v0.10.2MAINNET=true make install
Edit akash service file and change
akash start to
akash start --unsafe-skip-upgrades 455200
Start akash service