[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 • Bump http-proxy-middleware from 2.0.6 to 2.0.9 ( #3710 ) • Bump golang.org/x/crypto from 0.32.0 to 0.35.0 ( #3709 ) • Bump golang.org/x/crypto from 0.32.0 to 0.35.0 ( #3708 ) • Bump `@docusaurus/core` from 2.4.3 to 3.7.0 ( #3693 ) • Bump `@docusaurus/plugin-client-redirects` from…
Excerpt (1194 of 4432 characters). Read the whole post on the forum ↗
RIP LSM.
Suck it, Kim.
We are absolutely for this proposal. It is a great point to finally see the hub’s LSM fork finally removed from the equation.
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!
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.
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 
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 ?
Not from ICL, but afaik, the functionality is still in the x/liquid module, it’s just rewritten as its own module instead of mixed into the staking module (which needed the Cosmos Hub to use a forked version of the whole Cosmos SDK for the last 2 or so years). Tokenizing staked ATOM is still possible
Thankful for Cosmos_Nanny. Please keep up the great work.
Despite it now being updated (thank you Mintscan), are we not mocking Cosmos Hub governance with these type of careless errors? Then to see the immediate votes committed in favor, even before the summary was updated.
Seems governance is being taken less and less “seriously” when it comes to on-chain proposals here, no?
pofftermatt:(which needed the Cosmos Hub to use a forked version of the whole Cosmos SDK for the last 2 or so years).
Thank you for sharing.
This is correct! Functionality remains the same but this allows us to defork and reduce a lot of tech debt.
Thanks for your kind words.
Tbf, the JSON file looked normal.
That’s probably what the validators looked at to evaluate legitimacy.