Overview
UpdatedPassed
- Voting ended
- Apr 25, 2023
- Opened Apr 11, 2023
- Submitted
- Apr 11, 2023
- Apr 11, 06:25 UTC
- Deposit
- 1,000 BAND
- Type
- Software upgrade
Votes
- Yes 99.9% 70.7M BAND
- No 0% 0 BAND
- No with veto 0% 0 BAND
- Abstain 0.1% 53.2K BAND
Description
Context
The purpose of this proposal is to upgrade the BandChain to v2.5. This upgrade will roll-out these features on BandChain
- Bump ibc-go to v4.3.0 due to v3 has reached the end of life and requires coordinating upgrade
- Bump cosmos-sdk to v0.45.15, tendermint (cometbft) to v0.34.27, and go-owasm v0.2.3
- Support statically linked binary for bandd
Upgrade block and date
This upgrade is expected to occur at block 16562500. (Estimate date is April 27, 2023 at 14:00 UTC)
On-Chain Upgrade Process
When the network reaches the halt height, the state machine program of the BandChain will be halted. This classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. We recommend validators to use Cosmovisor to swap the binaries automatically. Because it is an on-chain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.
Instruction to prepare v2.5 binary: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/prepare-for-upgrade-v2.5.md
What it does
The message the chain carries out if it passes, as written in the proposal.
How validators voted
A validator's vote counts for its delegators unless they vote themselves. Largest stake first.
Voting ended before BitBasic started recording Band votes on Oct 29, 2026, and the chain deletes votes when voting ends.