Proposal #59
Passed on 13 Dec 2021 with 100.0% of the votes for yes.
Yes
100.0%
100.0% without abstain
Veto
0.0%
of votes cast
Ended
13 Dec 2021
99.98%
of votes cast
0.01%
of votes cast
0.00%
of votes cast
0.01%
of votes cast
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.
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:
x/authz is an implementation of a Cosmos SDK module, per [Hidden link], 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.POST /tx and POST /txs/encode no longer work. Please see the [Hidden link] to migrate to the new REST endpoints.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.These changes have been extensively tested by various Cosmos Core Contributor teams including [Hidden link], [Hidden link], [Hidden link], [Hidden link], [Hidden link], [Hidden link] 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 [Hidden link].
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 [Hidden link] 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 [Hidden link]. To test a simulated local upgrade please see the [Hidden link]. Because it is an onchain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.