Gaia v22.2.0 Upgrade

## **Background** Gaia v22.2.0 is a minor state breaking release that will follow an accelerated governance process for software upgrades on the Cosmos Hub. This is a state breaking security fix, which is why a forum post has been skipped. 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** - The release page can be found [here](https://github.com/cosmos/gaia/releases/tag/v22.2.0). - The changelog can be found [here](https://github.com/cosmos/gaia/blob/v22.2.0/CHANGELOG.md). The release bumps the following dependencies: - Bump [ibc-apps/middleware/packet-forward-middleware](https://github.com/cosmos/ibc-apps/tree/main/middleware/packet-forward-middleware) to [v8.1.1](https://github.com/cosmos/ibc-apps/releases/tag/middleware%2Fpacket-forward-middleware%2Fv8.1.1) ([#3534](https://github.com/cosmos/gaia/pull/3534)) - Add `v22.2.0` upgrade handler ([#3538](https://github.com/cosmos/gaia/pull/3538)) **This is a state breaking upgrade!** ## **Testing and Testnets** The v22.2.0 release has gone through rigorous testing, including e2e tests, and integration tests by Interchain Labs. In addition, the v22.2.0 upgrade process has been independently tested by the team at Hypha Co-op. If additional issues are found while this proposal is on-chain, we will communicate our intention to cancel the upgrade proposal. ### **Potential risk factors** Although extensive testing and simulation will have taken place there always exists a risk that the Cosmos Hub might experience problems due to potential bugs or errors. In the case of serious problems, validators should stop operating the network immediately. Coordination with validators will happen in the [#cosmos-hub-validators-verified](https://discord.com/channels/669268347736686612/798937713474142229) channel of the Cosmos Network Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes. ### **Governance votes** The following items summarize the voting options and what it means for this proposal: **YES** - You agree that the Cosmos Hub should be updated with this release. **NO** - You disagree that the Cosmos Hub should 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.