There is a planned upgrade on shentu-2.2 network at height 6334000, which approximately correspond to Jan 20, 2022 00:30 UTC. The upgrade is a simple binary swap:
- Stop the running certik daemon
- Replace the binary with the
v2.3.0v2.3.1 version. - Start the daemon with the new binary.
Make sure you do NOT perform certik unsafe-reset-all or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/ShentuChain/shentu/releases/tag/v2.3.0 https://github.com/ShentuChain/shentu/releases/tag/v2.3.1.
To automate your upgrade process, you can use cosmovisor. However, we encourage monitoring the process during the time of the actual upgrade to ensure the node upgrades in a timely manner.
There is a planned upgrade on shentu-2.2 network at height 6530000, which approximately correspond to Feb 02, 2022 16:00 UTC. The upgrade is a simple binary swap at any height before the upgrade:
- Stop the binary at any height before 6530000.
- Replace the binary with the v2.3.1 version.
- Start the daemon with the new binary.
Make sure you do NOT perform certik unsafe-reset-all or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/ShentuChain/shentu/releases/tag/v2.3.1.
There is a planned upgrade on shentu-2.2 network at height 8705500, which approximately correspond to July 07, 2022 06:00 UCT. The upgrade is a simple binary swap at the upgrade height.
- Upgrade height is reached
- Stop the running certik daemon
- Replace the running binary (either v2.3.2 or v2.3.1) to v2.4.0 binary
- Start the daemon with the new binary
Or you could use cosmovisor. Shentu-V2 upgrade will support audo-download of the binaries for linux-amd64 binaries. However, we strongly encourage the node operators to stand by during the upgrade time to ensure the node can be upgrade in a timely manner.
Make sure you do NOT perform certik unsafe-reset-all or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/ShentuChain/shentu/releases/tag/v2.4.0.
There is a planned upgrade on shentu-2.2 network at height 10485430, which approximately correspond to Nov 09, 2022 06:00 UCT. Here are what you need to do.
- Upgrade height is reached
- Stop the running certik daemon
- Replace the running binary with the v2.6.0 version. The binary is renamed to shentud since v2.6.0
- Update the home directory (default directory changed from ~/.certik to ~/.shentud)
- Add additional config entries. add_config_entries_v260 contains diff files that show the additional entries added in app.toml and config.toml. If you want the upgrade to use iavl-fastnode (will impro ve performance) add iavl-disable-fastnode = false in app.toml under [base] before re-starting the node (it might take several hours)
- Set up shentud system service
- Start the shentud daemon with the new binary
Make sure you do NOT perform certik unsafe-reset-all, shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
Cosmovisor might not be able to find the expected binary or home directory due to the rename from certik to shentud. To make it work, you need to wait for the halt of the certik binary, then set everything up with shentud before you start cosmovisor. Here are some (probably not all) of the things you need to do.
- Upgrade height is reached
- Stop the running certik daemon
- Update the home directory (default directory changed from ~/.certik to ~/.shentud)
- Set up cosmovisor directory under ~/.shentud home directory
- Set environment variables with shentud binary and ~/.shentud home directory
- Start cosmovisor
You can find the release notes and built binaries here: https://github.com/ShentuChain/shentu/releases/tag/v2.6.0.
An upgrade is planned for the Shentu mainnet at height 12926000, which is estimated to be reached around 0am-1am UTC on April 26, 2023. Here are what you need to do:
- Upgrade height is reached
- Stop the running shentud daemon
- Replace the running binary with the v2.7.0 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.7.0
Here are what you need to do:
- Stop the running shentud daemon
- Replace the running binary with the v2.7.1 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.7.1
An upgrade is planned for the Shentu mainnet at height 14875800, which is estimated to be reached around Sep 06, 2023 13:30-14:30 UTC. Or you could get the upgrade time by visiting https://www.mintscan.io/shentu/blocks/14875800. Here are what you need to do:
- Wait until upgrade height is reached
- Stop the running shentud daemon
- Replace the running binary with the v2.7.2 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.7.2
Here are what you need to do:
- Wait until upgrade height is reached
- Stop the running shentud daemon
- Replace the running binary with the v2.8.0 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.8.0
Here are what you need to do:
- Wait until upgrade height is reached
- Stop the running shentud daemon
- Replace the running binary with the v2.9.0 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.9.0
Here are what you need to do:
- Wait until upgrade height is reached
- Stop the running shentud daemon
- Replace the running binary with the v2.10.0 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.10.0
An upgrade is planned for the Shentu mainnet at height 19525000, which is estimated to be reached around 10am UTC on July 23, 2024.
Here are what you need to do:
- Wait until upgrade height is reached
- Stop the running shentud daemon
- Replace the running binary with the v2.11.0 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud tendermint unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.11.0
An upgrade is planned for the Shentu mainnet at height 20949300, which is estimated to be reached around 12:30PM UTC on Oct 30th, 2024.
Here are what you need to do:
- Wait until upgrade height is reached
- Stop the running shentud daemon
- Replace the running binary with the v2.12.0 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud comet unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.12.0
The upgrade at height 21239900, expected around Nov 19th, 2024 13:00 UTC.
Here are what you need to do:
- Wait until upgrade height
21239900is reached - Stop the running shentud daemon
- Replace the running binary with the v2.13.0 version
- Restart the shentud daemon with the new binary
Make sure you do NOT perform shentud comet unsafe-reset-all, or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network. The above steps are sufficient to perform this upgrade.
You can find the release notes and built binaries here: https://github.com/shentufoundation/shentu/releases/tag/v2.13.0