v1.5.0-beta.4

Upgrading from v1.4.0-beta.6

When the network reaches the halt height XYZ, you'll see this message in your node's log (journalctl -fu secret-node):

2:00PM ERR UPGRADE "v1.5" NEEDED at height: XYZ:
2:00PM ERR CONSENSUS FAILURE!!! err="UPGRADE \"v1.5\" NEEDED at height: XYZ

Then, the upgrade steps for v1.5 are:

⚠️ Note: if you have modified your systemd unit file (/etc/systemd/system/secret-node.service) you will need to re-apply those changes post installation and pre-service restart.

Check what database type you're currently using:

awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml

Uncomment and download the right binary based on your database type:

# Stop the v1.4 node, to make sure that your process manager isn't trying to restart it while you upgrade
sudo systemctl stop secret-node

# Get & verify secretd v1.5

## goleveldb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.0-beta.4/secretnetwork_1.5.0-beta.4_testnet_goleveldb_amd64.deb"
# echo "2807c176955e29ff219b0cf60aac51d922785800a4bdac887ae8bc6721f8e4fe secretnetwork_1.5.0-beta.4_testnet_goleveldb_amd64.deb" | sha256sum --check

## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.0-beta.4/secretnetwork_1.5.0-beta.4_testnet_rocksdb_amd64.deb"
# echo "b00d09df145ec98414c75f6a69ac4a94de4f1f2b66b705f0e5a3492d1a0937f9 secretnetwork_1.5.0-beta.4_testnet_rocksdb_amd64.deb" | sha256sum --check

# Install v1.5 binaries
sudo apt install -y ./secretnetwork_1.5.0-beta.4_testnet_*_amd64.deb

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

After restarting the node with v1.5, you should see INF applying upgrade "v1.5" at height: XYZ in the logs (journalctl -fu secret-node). Once 67% of voting power comes online, you'll see blocks executing again.

Details of Upgrade Time

When the network reaches the halt height XYZ, the Secret Network testnet blockchain will be halted and validators will need to take action to upgrade the chain to the secretd v1.5 binary (be it manually or automatically).

The proposal targets the upgrade proposal block to be XYZ, anticipated to be on Thursday October 6, 2022 at 2:00PM UTC.

The upgrade is anticipated to take approx 30 minutes, during which time, there will not be any on-chain activity on the network.

In Case of an Upgrade Failure

In the event of an issue at upgrade time, we should coordinate via the "SN Testnet Validators" Telegram group.

If as a result of a software bug the network fails to produce new blocks with the v1.5 binaries, the SCRT Labs team will distribute a v1.4 binary with an empty v1.5 upgrade handler, which will essentially allow the chain to revert to v1.4 while continuing to produce new blocks.

What's Changed

• Fix secret message parsing when message is plaintext in IBC by @liorbond in #1199

Full Changelog: v1.4.0...v1.5.0-beta.4