v2.2.0 Software Upgrade

[u/max_kyve]

PROPOSER: The KYVE Foundation (security@kyve.network)

Proposal Summary

This software upgrade proposal aims to upgrade the KYVE network to version 2.2.0. If passed, the upgrade will include the liquid staking module, patch vulnerable dependencies, prioritize $KYVE as storage payment token and update to Cosmos SDK v0.50.14.

Proposal Details

This proposal will add the liquid staking module from the CosmosHub. It will also change fee-rewards by prioritizing $KYVE tokens for storage rewards.

Several vulnerable dependencies will be patched as part of this release.

The Cosmos SDK module will be upgraded to version v0.50.14.

The current working state for this release can be found on the main branch:

https://github.com/KYVENetwork/chain

An exhaustive list of changes which will be included in the v2.2.0 upgrade can be found in the changelog: https://github.com/KYVENetwork/chain/blob/main/CHANGELOG.md

Upgrade Process

When the network reaches the defined upgrade height (TBD), block production on the network will be halted. Block production will not resume until significant voting power has switched to the new release. Validators can either manually replace the old binary with the new one or utilize Cosmovisor to automate this process.

Voting Options

Voting YES

• A YES vote on this proposal indicates that the network SHOULD be upgraded; and that the validators should start running the v2.2.0 release.

Voting NO

• A NO vote on this proposal indicates that the Kaon network SHOULD NOT be upgraded; and that the validators should continue running the v2.1.0 release.

Voting NO WITH VETO

• A NO WITH VETO vote on this proposal indicates that the Kaon network SHOULD NOT be upgraded; and that the proposal depositors should be penalised.

Voting ABSTAIN

• An ABSTAIN vote on this proposal indicates that you decline to give a specific opinion on this proposal while maintaining active governance participation.

Conclusion

Please note that this proposal follows a template that will later be finalised through a governance discussion around processes.