[PROPOSAL 1000][VOTING] Gaia v24.0.0 Software Upgrade

Background

This upgrade changes the LSM module to a refactored x/liquid module, which has been audited by . Docs for the module are available here. This work is needed to get the Hub unforked from the SDK, which would reduce our technical debt and ease future development. After the migration in this upgrade, we can complete the unforking in Gaia v25, targeted for mid / late June.

Gaia v24.0.0 is a major release that will follow the regular governance process for software upgrades on the Cosmos Hub, or an expedited one in the event that prop 998 does not pass.

Reminder – This proposal will have a voting period of just ONE WEEK.

If the proposal passes, validators will be required to update the Cosmos Hub binary at the halt-height specified in the on-chain proposal.

Release Details

  • The release candidate can be found here.
  • The changelog can be found here.

DEPENDENCIES

FEATURES

  • Add x/liquid module (#3712)
  • Remove expedited gov prop type restrictions (#3723)
  • Add liquid validator query to x/liquid (#3735)

BUG-FIXES

  • Set x/liquid params during InitGenesis (#3759)

STATE BREAKING

  • Add x/liquid module (#3712)

This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.

Testing and Testnets

The v24.0.0 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the upgrade process will be independently tested by the team at Hypha Co-op and will be performed by validators and node operators on a public testnet prior to cutting the final release.

If you wish to participate in the testnet upgrade process in the future, you can find the relevant information (genesis file, peers, etc.) to join the Cosmos Hub’s Interchain Security Testnet (provider) here.

Potential risk factors

As with any major upgrade, there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors, even though extensive testing and simulation has been completed. In the case of serious problems, validators should stop operating the network immediately.

Coordination with validators will happen in the #cosmos-hub-validators-verified channel of the Cosmos Network 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 (v23.3.0).

Governance votes

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

YES - You agree that the Cosmos Hub should upgrade to v24.0.0.

NO - You disagree that the Cosmos Hub should upgrade to v24.0.0.

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 the quorum but you formally decline to vote either for or against the proposal.

5 Likes

RIP LSM.

Suck it, Kim.

1 Like

We are absolutely for this proposal. It is a great point to finally see the hub’s LSM fork finally removed from the equation.

3 Likes

Looking forward to it, voting yes for sure. Would be great to have the “Interchain Security Testnet Schedule” updated to include v24.

I remember voicing my concern about Hub using its own fork instead of a canonical one quite a while ago, so given that this proposal is essentially switching to a canonical cosmos-sdk repo, it’s a no-brainer YES from me. LFG!

1 Like

The LSM is dead…

2 Likes

If this upgrade is removing the NK LSM code that was mentioned a while back, then yes and thank you.

Keep Cosmos Hub minimal as possible.

1 Like

Any audit planned on this?

Yes, this new module is fully audited by Zellic. The report is available here.

Proposal 1000 is now on-chain. Happy voting everyone :dizzy:

1 Like

As requested before the implementation of this module - we’re indeed in favor of the removal of this unwanted feature.

So right after the upgrade it will not be possible to instantly LS through Stride anymore right ?

FYI, the chat gpt summary in Mintscan for Proposal 1000:

@InterchainLabs @Cosmostation_Lee