Secret Network v1.5 Upgrade
What's Changed
- Fix secret message parsing when message is plaintext in IBC by @liorbond in #1199
- Refactor Tendermint and Cosmos configs by @assafmo in #1211
- Fix creating accounts using ICA by @assafmo in #1215
- Fix node registration by @Cashmaney in #1221
- Update Cosmos SDK 0.45.9 -> 0.45.10 & Tendermint 0.34.21 -> 0.34.22 by @assafmo in #1230
- Update IBC 3.3.0 -> 3.3.1 by @dependabot in #1237
- Fix nested attributes signatures by @liorbond in #1241
- Fix state sync by @assafmo in #1243
- Fix some protobuf type names by @assafmo in 256d9b2
Special thanks: @faddat!
Full Changelog: v1.4.1-patch.3...v1.5.0
Upgrade Time
When the network reaches the halt height 5,941,700, the Secret Network blockchain will be halted and validators will need to take action to upgrade the chain to the secretd v1.5 binary.
The proposal targets the upgrade proposal block to be 5,941,700, anticipated to be on Wednesday November 2, 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.
Upgrade Instructions
When the network reaches the halt height 5,941,700, you'll see this message in your node's log (journalctl -fu secret-node):
2:00PM ERR UPGRADE "v1.5" NEEDED at height: 5941700:
2:00PM ERR CONSENSUS FAILURE!!! err="UPGRADE \"v1.5\" NEEDED at height: 5941700Then, 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.tomlUncomment 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/secretnetwork_1.5.0_mainnet_goleveldb_amd64.deb"
# echo "483e25f6ba189d4763a81da94f32e20306370bb3111aa208d16c0141a4a0da7d secretnetwork_1.5.0_mainnet_goleveldb_amd64.deb" | sha256sum --check
## rocksdb
# wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.5.0/secretnetwork_1.5.0_mainnet_rocksdb_amd64.deb"
# echo "4ff71dda2592c2d49fa7df723959ec51a5ba94890c0e804b63e95a38424607ae secretnetwork_1.5.0_mainnet_rocksdb_amd64.deb" | sha256sum --check
# Install v1.5 binaries
sudo apt install -y ./secretnetwork_1.5.0_mainnet_*_amd64.deb
# re-apply any systemd unit file customizations
# Restart the node
sudo systemctl restart secret-nodeAfter restarting the node with v1.5, you should see INF applying upgrade "v1.5" at height: 5941700 in the logs (journalctl -fu secret-node). Once 67% of voting power comes online, you'll see blocks executing again.
In Case of an Upgrade Failure
In the event of an issue at upgrade time, we should coordinate via the "SN 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.