Proposal #11

BCIP-11: Upgrade to v2.5

Exec Legacy Content
passed
Expected result
Passed
Turnout / Quorum
77.80% / 40.00%

Voting period

Voting ended100.0%
Voting start 2023.04.11 at 08:29:18
Voting end 2023.04.25 at 08:29:18

Vote distribution

99.92%
70 733 404 band
Yes
0%
0 band
No
0%
0 band
Veto
0.08%
53 167 band
Abstain

Details

logo
Proposer
-
Total deposit
1 000 band
Submit time
2023.04.11 at 08:25:38
Deposit end time
2023.04.25 at 08:25:38

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

Votes

Voter
Answer