Change log
- 2025-Mar-05: Posted initial draft
- 2025-Mar-07: Updated agreement language & highlighted the need for a WASM MsgStoreCode Authz grant
- 2025-Mar-18: Updated links and dependancy list.
Background
Gaia v23 is a major release that will follow the standard governance process for software upgrades on the Cosmos Hub. Feedback on this proposal will be open for roughly 1 week.
Reminder – the Cosmos Hub uses expedited voting for software upgrade proposals. 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
We are targeting the upgrade for Wednesday, March 26th. After the upgrade Interchain Labs will upload the Eureka contracts and officially launch the Eureka product later in March.
This release includes an upgrade to IBC v2, which is needed for the launch of the IBC Eureka product. This will allow the Cosmos Hub to connect to Ethereum mainnet over IBC in an affordable and secure manner. In the future, we plan to connect IBC Eureka, and thus the Hub to Solana and to Layer 2s such as Arbitrum and Base.
The release bumps the following dependencies:
- ibc-go to v10.1.0
- ibc-apps/modules/rate-limiting to v10.0.0
- ibc-apps/middleware/packet-forward-middleware to v10.0.0
- ibc-go/modules/light-clients/08-wasm to v10.0.0
- interchain-security to v7.0.0
This upgrade is state-breaking and mandatory once the on-chain vote passes and the upgrade-height is reached.
Additional note:
The WASM light client for Ethereum will not be ready before this proposal goes on-chain. In order to prevent an additional upgrade to be needed, we’re adding an Authz permission to the v23 upgrade in order to allow cosmos1raa4kyx5ypz75qqk3566c6slx2mw3qzs5ps5du to upload (but not modify!) the light client. The specific message being granted is /ibc.lightclients.wasm.v1.MsgStoreCode
Testing and Testnets
The v23 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the v23 upgrade process has been independently tested by the team at Hypha Co-op and has been 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 (v22.3.1).
Governance votes
The following items summarize the voting options and what it means for this proposal:
YES - You agree that the Cosmos Hub should launch IBC Eureka and be upgraded with this release.
NO - You disagree that the Cosmos Hub should launch IBC Eureka and be updated with this release.
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.
