[PROPOSAL #][DRAFT] Gaia v8-Rho Upgrade

Change log

  • 2022-10-28 New forum post draft
  • 2022-06-23 Announced delay of Rho on Twitter
  • 2022-05-16 Initial proposal for comment here


Roadmap link: gaia/cosmos-hub-roadmap-2.0.md at main · cosmos/gaia · GitHub

Please note that the original forum post on the Rho upgrade has been deprecated as it contains a number of inaccuracies, notably due to upstream software delays and Prop 69 failing to pass governance.

Since the last v7-Thetha upgrade at height 10,085,397 there have been a number of updates, fixes and new modules added to the Cosmos SDK, IBC and Tendermint.

This is a proposal to adopt the final release for the v8-Rho upgrade for the cosmoshub-4 mainnet.

It contains the following changes:

  • (gaia) bump cosmos-sdk to v0.46.3. See CHANGELOG.md for details including an updated gov module
  • (gaia) bump ibc-go module to v5.0.1. See CHANGELOG.md.
  • (gaia) bump Liquidity module to v2.0.1.
  • (gaia) bump packet-forwarding-middleware to depend on ibc-go v5.
  • (feat) add icamauch (Interchain Account Message Authorization) module.
  • (feat) add globalfee module.
  • (feat) Add Groups module.
  • (feat) replace MempoolFeeDecorator with FeeDecorator to bypass min fees.
  • (tests) add E2E integration tests for the following modules
    • Bank
    • Bypass Min Fee
    • Distribution
    • Encode
    • Evidence
    • FeeGrant
    • Global Fee
    • Gov Legacy
    • Gov New
    • Groups
    • IBC transfer
    • IBC ICA
    • IBC ICA mauth
    • IBC packet forwarding middleware
    • Slashing
    • Staking
    • Vesting

Upgrade process

Validators will connect to theta-testnet-001. You can find the relevant information (genesis file, peers, etc.) to join the public testnet via shell script or Ansible playbook here.

We plan to simulate the upgrade process on this public testnet around November 2nd. You’ll find an up to date testnet schedule here. Once tested on the public testnet, the mainnet software upgrade proposal will follow approximately 5-7 days later. There will be 14 days of voting and the proposal will target a suitable date within a week of the resolution of the vote.

Potential risk factors

Although very extensive testing and simulation has taken place there always still exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors from the new features. In the case of serious problems, validators should stop operating the network immediately. Cosmos Core Contributors will coordinate with validators in the #validators-verified channel of the Cosmos Developer Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release of gaia (v7.0.x).

Release checklist

Checklist of engineering items related to rho can be found in gaia issue 1535 and the Rho label.

Governance votes

The following items summarize the voting options and what it means for this proposal:

NO -
NO WITH VETO - A ‘NoWithVeto’ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of ‘NoWithVeto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.
ABSTAIN - You wish to contribute to quorum but you formally decline to vote either for or against the proposal.