Proposals of #59

Vega

Exec Legacy Content
passed
Expected result
Turnout / Quorum
35.98% / 40.00%
Voting start 2021.11.29 at 11:11:56
Voting end 2021.12.13 at 11:12:56
99.98%
94 563 147 atom
Yes
0.00%
2 160 atom
No
0.01%
7 738 atom
Veto
0.01%
6 705 atom
Abstain

Details

logo
Proposer
-
Total deposit
64 atom
Submit time
2021.11.28 at 20:11:04
Deposit end time
2021.12.12 at 20:12:04

Description

This on-chain upgrade governance proposal is to adopt gaia v6.0.0 which includes a number of updates, fixes and new modules. By voting YES to this proposal, you approve of adding these updates to the Cosmos Hub.

Background

Since the last upgrade at height 6910000 there have been a number of updates, fixes and new modules added to the Cosmos SDK, IBC and Tendermint. The following updates are included in gaia v6.0.0:

  • Bump Cosmos-SDK to v0.44.3 which notably includes fixes for the vesting accounts and two new modules outlined below. For a full list of updates in Cosmos-SDK v0.44.3 please see the CHANGELOG.md
    • Add the authz module to the Cosmos Hub. x/authz is an implementation of a Cosmos SDK module, per ADR 30, that allows granting arbitrary privileges from one account (the granter) to another account (the grantee). Authorizations must be granted for a particular Msg service method one by one using an implementation of the Authorization interface.
    • Add the feegrant module to the Cosmos Hub. This module allows accounts to grant fee allowances and to use fees from their accounts. Grantees can execute any transaction without the need to maintain sufficient fees.
    • NOTICE It's imortant to highlight PR #10041 which impacts WALLETS AND EXCHANGES. This update has removed the deprecated the legacy REST endpoints for broadcast & encode. This means POST /tx and POST /txs/encode no longer work. Please see the REST Endpoints Migration guide to migrate to the new REST endpoints.
  • Add IBC as a standalone module from the Cosmos SDK using version v2.0.0. See the CHANGELOG.md for details.
    • Please note that the governance parameter for MaxExpectedBlockDelay is set to 30 seconds. This means if a connection is opened with a packet delay of 1 minute, it requires 2 blocks to be committed after the consensus state is submitted before the packet can be processed.
  • Add packet-forward-middleware v1.0.1 as per Proposal #56 prepared and tested by Strangelove Ventures. This feature allows multi-hop IBC transfer messages so that a user can send tokens from chain A to chain C via chain B.
  • Bump Liquidity module to v1.4.2 to ensure compatibility with Cosmos-SDK.

Ready for Production

These changes have been extensively tested by various Cosmos Core Contributor teams including Hypha Co-Op, Informal Systems Co-Op, Interchain GmbH, Regen Network, Strangelove Ventures, Tendermint Inc and more. The release candidate for this update was run as a local testnet and a public testnet with a successful upgrade; documentation can be found here.

On-Chain Upgrade Process

When the network reaches the halt height, the state machine program of the Cosmos Hub will be halted. The classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. There is also a newer method that relies on Cosmovisor to swap the binaries automatically. Cosmovisor also includes the ability to download the binaries automatically before swapping them. Instructions specific to the upgrade can be found here. To test a simulated local upgrade please see the local testnet documentation. Because it is an onchain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.

Votes

Voter
Answer