This adds:
- A bump in contract compilation cost
Astarte testnet validators
We are going to test whether or not this breaks consensus using the testnet. It should not require an upgrade handler, meaning you can stop your node and upgrade to the new binary at any time. If the upgrade fails, then please report this in the #validators-testnet channel on discord.
# get the new version
git checkout main && git pull
git checkout v2.0.2
make build && make install
# check the version - should be v2.0.2
# junod version --long will be commit 998e1b6c6258c4cae4b44f0d74d7717e3a994eab
junod version
# IMPORTANT: stop your chain and replace the binary - stop it now and replace
# if you are using cosmovisor you then need to copy this new binary OVER the moneta binary
# and then check it is symlinked to current
cp /home/<your-user>/go/bin/junod $DAEMON_HOME/cosmovisor/upgrades/moneta/bin
# check symlink
ls -la $DAEMON_HOME/cosmovisor
# should return something like:
# lrwxrwxrwx 1 <user> <user> 49 Dec 5 13:58 current -> /home/<user>/.juno/cosmovisor/upgrades/moneta
# drwxrwxr-x 3 <user> <user> 17 Dec 2 23:51 genesis
# drwxrwxr-x 3 <user> <user> 20 Dec 3 14:14 upgrades
# find out what version you are about to run - should be v2.0.2
$DAEMON_HOME/cosmovisor/upgrades/moneta/bin/junod version
$DAEMON_HOME/cosmovisor/current/bin/junod version
# you can now restart your chainWhat's Changed
Full Changelog: v2.0.1...v2.0.2