Skip to main content

BAND $0.1906 1.92% Market cap $35.3M

BCIP-9: Upgrade to v2.4

Proposal #9 on Band

Band network: Day Nov 3 · Healthy

Typical fee 0.0007 BAND

Overview

Updated

Passed

Voting ended
Nov 17, 2022
Opened Nov 3, 2022
Submitted
Nov 3, 2022
Nov 3, 09:30 UTC
Deposit
1,001 BAND
Type
Software upgrade

Votes

  • Yes 77M BAND
  • No 0 BAND
  • No with veto 0 BAND
  • Abstain 0 BAND

Description

Context

The purpose of this proposal is to upgrade the BandChain to v2.4. This upgrade will roll-out these features on Bandchain

  • Bump cosmos-sdk to v0.45.10 and ibc-go to v3.3.1 to fully support state sync and ICA-host
  • Increase the throughput for oracle module by ~10X from optimizing owasm runtime
  • Increase the MaxGas per block to 50M Gas

Upgrade block and date

This upgrade is expected to occur at block 11525000. (Estimate date is November 21, 2022 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 migrate to use cosmovisor: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/migrate-bandd-binary-to-cosmovisor.md

Instruction to prepare v2.4 binary: https://github.com/bandprotocol/launch/blob/master/laozi-mainnet/docs/prepare-for-upgrade-v2.4.md

Effects

  • Users/Developers: After the upgrade, you will need and are advised to redeploy your oracle scripts to reduce used gas for oracle requests

For full details of upgrade please see this article: https://medium.com/bandprotocol/bandchain-v2-4-upgrade-70dbb896618c

What it does

The message the chain carries out if it passes, as written in the proposal.

  1. Software upgrade cosmos.upgrade.v1beta1 
    {
    "@type": "/cosmos.gov.v1.MsgExecLegacyContent",
    "content": {
        "plan": {
            "info": "",
            "name": "v2_4",
            "time": "0001-01-01T00:00:00Z",
            "height": "11525000",
            "upgraded_client_state": null
        },
        "@type": "/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal",
        "title": "BCIP-9: Upgrade to v2.4",
        "description": "## Context\nThe purpose of this proposal is to upgrade the BandChain to v2.4. This upgrade will roll-out these features o… (1,544 characters)"
    },
    "authority": "band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"
}

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.