Releases: shentufoundation/shentu
v2.9.0
An upgrade is planned for the Shentu mainnet at height 16084500 , which is estimated to be reached around Nov 28, 2023 13:00-14:00 UTC
. This release should be applied after reaching the upgrade height.
The upgrade operation should be a binary replacement at the upgrade height, Please refer to https://github.com/shentufoundation/mainnet/tree/main/shentu-2.2/upgrades#v290-upgrade for upgrade instructions.
Changelog
[v2.9.0] - 11-17-2023
New module
- (x/bounty) #786 Add a
bounty
module.
certificate
(x/cert) #786 Add a bountyadmin certificate.
bech32
Only the address with the prefix 'shentu' is supported.
(bech32) #787 Disable old prefix address compatibility.
Binary checksum
sha256sum shentud_2.9.0_*
286892713482cd39dd38a7e76e44ffa6ba0ffeb06c935642c6577dee236b9c7d shentud_2.9.0_arm64_macos
6ef52ee7ae3ea462326665ae3f11e0e2a6a8649b11c21cab479c72cacbee7430 shentud_2.9.0_linux_amd64
4a5b7b3831ababd569999c6a291bca061b3db1a7be47621f81d7a20c4768d938 shentud_2.9.0_win_x86_64.exe
v2.8.0a
Release v2.8.0a
v2.8.0
An upgrade is planned for the Shentu mainnet at height 15094300 , which is estimated to be reached around Sep 21, 2023 13:00-14:00 UTC. This release should be applied after reaching the upgrade height.
The upgrade operation should be a binary replacement at the upgrade height, Please refer to https://github.com/shentufoundation/mainnet/tree/main/shentu-2.2/upgrades#v280-upgrade for upgrade instructions.
Changelog
[v2.8.0] - 09-12-2023
Version 2.8.0 changes the Bech32 address prefix to 'shentu'.
State Machine Breaking Changes
- (app) #718 Modify the persisted Bech32 addresses for various modules to change the prefix to 'shentu'.
Bug Fixes
- (x/cert) #754 Fix the bug of wrongly decoding of platform certificate.
Binary checksum
sha256sum shentud_2.8.0_*
33fa97fbed48705c7b14b8f77c6969555f24068bc7e9caa63024bcac36ac0521 shentud_2.8.0_arm64_macos
3c16c4c4ca62f7b4e447414667338e799bd27de36adddb2354908aaef8072e0a shentud_2.8.0_linux_amd64
90fce7fb8746e7864b81f124b2f4c15932be77eefffea4ff088a9460fd788fc5 shentud_2.8.0_win_x86_64.exe
v2.7.2
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. This release should be applied after reaching the upgrade height.
The upgrade operation should be a binary replacement at the upgrade height, Please refer to https://github.com/shentufoundation/mainnet/tree/main/shentu-2.2/upgrades#v272-upgrade for upgrade instructions.
Changelog
Bug Fixes
- (x/gov) #761 fix the bug of votes are removed early for general proposals
Binary checksum
sha256sum shentud_2.7.2_*
ff249d58394f329d8025915532fb9d12300de784fd9b4eb96529a00af2f9ed2f shentud_2.7.2_linux_amd64
46cc49c82264239688a5990c7ba6d57754bd57e5c38bb06f73654390bf078eb4 shentud_2.7.2_arm64_macos
694a6c971882e471d0b4529b5edc1927bd7c023e553c2a816dfa82e417b782e2 shentud_2.7.2_win_x86_64.exe
v2.7.1
The upgrade operation should be a binary replacement without a chain-halt, Please refer to https://github.com/shentufoundation/mainnet/tree/main/shentu-2.2/upgrades#v271-upgrade for upgrade instructions.
Changelog
[v2.7.1] - 05/25/2023
Upgrade IBC to v4.2.1, which addresses a potential security vulnerability impacting IBC connected full nodes.
Improvements
- (app) #702 Upgrade IBC to v4.2.1
v2.7.0
An upgrade is planned for the Shentu mainnet at height 12926000
, which is estimated to be reached around 1am-2am UTC on April 26, 2023. This release should be applied after reaching the upgrade height.
The upgrade operation should be a binary replacement at the upgrade height, Please refer to https://github.com/shentufoundation/mainnet/tree/main/shentu-2.2/upgrades#v270-upgrade for upgrade instructions.
Changelog
[v2.7.0] - 04-11-2023
Version 2.7.0 brings Oracle 1.5, which offers security evaluation for transactions running on business chains.
State Machine Breaking Changes
- (x/gov) #651 Achieve the compatibility with Cosmos gov interface by removing customized implementation from the gov module.
Features
- (x/oracle) #613 Introducing Oracle 1.5 to provide trusted scoring for other on-chain business transactions.
Improvements
- (app) #646 Upgrade cosmos-sdk from v0.45.9 to v0.45.11 and tendermint from v0.34.21 to v0.34.23
- (app) #599 Upgrade IBC to v4.2.0
- (app) #633 Improve go deps and proto gen.
Bug Fixes
- (x/shield) #563 Fix shield service fees bug.
v2.7.0-rc1
v2.7.0-rc1
v2.6.0
This release changes binary name to shentud
from certik
, and package path to github.com/shentufoundation/shentu
from github.com/certikfoundation/shentu
.
There is an upgrade planned at height 10485430
for shentu mainnet. This release should be applied at the height where Shentu-V260
software upgrade takes place. Further announcements & operations for the upgrade will be posted soon.
The upgrade operation should be a binary replacement at the upgrade height, plus rename of the home directory from .certik to .shentud. Please refer to https://github.com/ShentuChain/mainnet/tree/main/shentu-2.2/upgrades#v260-upgrade for upgrade instructions.
Make sure you do NOT perform the below operations:
certik unsafe-reset-all
or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network.- Replace the binary before the upgrade height. It will corrupt your database and you will have to either download the snapshot at https://shentu-data-snapshot-light.s3.amazonaws.com/shentu.tar.gz or sync from the beginning of shentu-2.2 network.
Changelog
[v2.6.0] - 10/31/2022
Client Breaking Changes
- (app) #467 Change binary name to
shentud
fromcertik
API Breaking Changes
- (app) #467 Change package path to "github.com/shentufoundation/ shentu" from "github.com/certikfoundation/shentu"
- (app) #386 Remove MixedCoins from codebase
State Machine Breaking Changes
v2.6.0-rc1
v2.6.0 RC version
v2.5.0
This includes an unreleased patch to the IBC related vulnerability described in https://forum.cosmos.network/t/ibc-security-advisory-dragonberry/7702.
Please upgrade your node ASAP to avoid node halt, and do not build the binary yourself, as the release binaries contains the fix without disclosing the locations of the bug
The upgrade operation should be a simple binary replacement at the upgrade height:
- Stop the running certik daemon
- Replace the binary (v2.4.0) with the v2.5.0 version.
- Start the daemon with the new binary.
The above steps are sufficient to perform this upgrade.
Make sure you do NOT perform the below operations:
certik unsafe-reset-all
or delete the data directory, as it will require you to sync from the beginning of shentu-2.2 network us use a snapshot to bootstrap your node.