v4.2.1

What's Changed

• v4.2.1 - Patch handle custom wasm msg by @discoverdefiteam in #189

Full Changelog: v4.2.0...v4.2.1

Coordinated Halt & Node Upgrade

This co-ordinated upgrades will require validators to stop their validators at halt-height determined by governance, switch their binary to v4.2.1 and restart their nodes with the new version.

Manual steps

Step 1: Configure halt-height and restart the node.

This upgrade requires terpd halting execution at a pre-selected halt-height. Failing to stop at halt-height may cause a consensus failure during chain execution at a later time.

There are two mutually exclusive options for this stage:

Option 1: Set the halt height by modifying app.toml

• Stop the terpd process.

• Edit the application configuration file at ~/.terp/config/app.toml so that halt-height reflects the upgrade plan:

sed -i 's|halt-height =.*|halt-height= "<HALT_HEIGHT_HERE>"|g' $HOME/.terp/config/app.toml

• restart terpd process

• Wait for the upgrade height and confirm that the node has halted

Option 2: Restart the terpd binary with command line flags

• Stop the terpd process.

• Do not modify app.toml. Restart the terpd process with the flag --halt-height:

terpd start --halt-height <HALT_HEIGHT_HERE>

• Wait for the upgrade height and confirm that the node has halted

Upon reaching the halt-height you need to replace the v4.2.0 terpd binary with the new v4.2.1 binary and remove the halt-height constraint.
Depending on your setup, you may need to set halt-height = 0 in your app.toml before resuming operations.

sed -i 's|halt-height =.*|halt-height= "0"|g' $HOME/.terp/config/app.toml

Build and start the binary

cd $HOME/terp-core
git pull
git fetch --tags
git checkout  v4.2.1
make install

# verify install
terpd version
# v4.2.1

terpd start # starts the v4.2.1