v1.10

Secret Network v1.10 Instructions

โš ๏ธ IMPORTANT NOTES โš ๏ธ

  • All coordination efforts will be done in the "SN Validators" Telegram group.

  • Make sure to backup your validator before making any changes.

  • Please read carefully before you begin the upgrade.

Upgrading Manually

โš ๏ธ Note: The below instructions assume default installation. DO NOT COPY-PASTE if config.toml is not in ~/.secretd/config/config.toml or if you modified /etc/systemd/system/secret-node.service. If you have modified /etc/systemd/system/secret-node.service, you will need to re-apply those changes post installation and pre service restart.

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

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

Then, the upgrade steps for v1.10 are:

# Backup your node's SGX secrets
cp -a /opt/secret/.sgx_secrets ~/sgx_secrets_backup
mkdir 19backup
cp ~/.secretd/.node/* 19backup/

# Figure out currently used db backend
DB_BACKEND=$(awk -F \" '/^db_backend =/{print $2}' ~/.secretd/config/config.toml)

# Get the v1.10 binaries
wget "https://github.com/scrtlabs/SecretNetwork/releases/download/v1.10.0/secretnetwork_1.10.0_mainnet_${DB_BACKEND}_amd64.deb"

# Verify the v1.10 binaries
echo '4c1818a6cc8b72e20e492741cb9fbed6567e8971333718f0787e8f182fda18a4 secretnetwork_1.10.0_mainnet_goleveldb_amd64.deb
f33f1494e6498974e13b205e94dd4c538707b8bc8dafbbc7153b79f491b31e22 secretnetwork_1.10.0_mainnet_rocksdb_amd64.deb' |
    grep "$DB_BACKEND" |
    sha256sum --check

# Stop the v1.9 node
sudo systemctl stop secret-node

# Install the v1.10 binaries
sudo apt install -y "./secretnetwork_1.10.0_mainnet_${DB_BACKEND}_amd64.deb"

# re-apply any systemd unit file customizations

# Restart the node
sudo systemctl restart secret-node

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

โš ๏ธ Note: when starting the v1.10 node on a (pre-registered) unpatched machine, you might get a GROUP_OUT_OF_DATE error. It is expected and your node should still start up during the grace period. After the grace period ends (August 21, 2023, 2:00 PM UTC), unpatched machines will no longer start.

Upgrading Automatically Using Cosmovisor

Cosmovisor is a new process manager for cosmos blockchains. It can make low-downtime upgrades smoother, as validators don't have to manually upgrade binaries during the upgrade, and instead can pre-install new binaries, and Cosmovisor will automatically update them based on on-chain SoftwareUpgrade proposals.

โš ๏ธ Cosmovisor is still new and best practices for using it are not yet established. If you don't feel adventurous at this time, we recommend upgrading the manual way.

For instructions on how to setup Cosmovisor, go here.

Details of Upgrade Time

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

The proposal targets the upgrade proposal block to be 10,186,400, anticipated to be on Monday August 14, 2023 at 5: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 Validators" Telegram group.

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

Last updated