[PROPOSAL 885][PASSED] Gaia v15 Software Upgrade

Change log • 2024-2-14 Created initial post • 2024-3-1 Revised title for on-chain proposal • 2024-3-17 Revised title for vote passing Important Notes for Node Operators This is a large upgrade and we expect it to be fairly slow due to state migrations in upgrading the sdk to 0.47.x. There are revised hardware requirements just for this upgrade, but specs can return to current mainnet requirements afterwards. • Minimum: 64GB RAM + 32GB swap • Recommended: 128GB RAM • Bare minimum 32GB RAM + 64GB swap Optimal CPU performance: 2.50GHz, 8 cores (eg Intel Xeon Gold 6248 or equivalent consumer grade processor). It is paramount that the operators set enough SWAP to cover all cases. SWAP partitions can be used to supplement the RAM requirement but they will increase the upgrade time. Further recommendations • If you are unable to meet the hardware requirements, consider skipping the upgrade and resyncing from snapshot once the upgrade goes through. • NodeStake: Cosmos | NodeStake • Polkachu: CosmosHub Node Snapshot | Polkachu • Lavender.five: Node Tools & Validator documentation | Lavender.Five Nodes • Logs will be sparse during this long upgrade. You…

Excerpt (1199 of 6047 characters). Read the whole post on the forum ↗

btruax:

This is a large upgrade and we expect it to be fairly slow due to state migrations in upgrading the sdk to 0.47.x.

For context, this upgrade took us about an hour when doing a stateful upgrade with a single whale validator. Usually our Gaia upgrades are very quick in this format (<10 min).

Appreciate including the fix for missing addresses in /signing_info response: Missing address in signing_infos of rest api #1344 · Issue #1734 · cosmos/gaia · GitHub, that’ll optimise the queries I have to do in my tools.
Already waiting for this to land on Hub, LFG!

btruax:

The focus of this release is the upgrade of Cosmos SDK to v0.47 – this release uses v0.47.8-ics-lsm, a special Cosmos SDK branch with support for both ICS and LSM. Consequently, it also upgrades the following dependencies:

Are there plans for the future to abolish the need for custom releases/tags of cosmos-sdk with the changes specifically tailored for Cosmos Hub?

Look forward to it

The reason Gaia requires a special SDK release is LSM. SDK 0.51 should enable plug-ins for the staking module, which means that the LSM logic can be implemented as a plug-in and then Gaia can go back to mainline SDK.

Staking Facilities is looking forward to upgrading the nodes

We always value the detailled information and instructions provided.

That being said - I just wanted to drop the link to the technical upgrade docs including possible rollback scenarios and backup recommendations:

https://github.com/cosmos/gaia/blob/release/v15.x/UPGRADING.md 

If i remember correctly a future change of the validator commission rate param will not trigger a change the comission rate of the current set?

It has evolved.

Validators with a commission rate < 5% prior to upgrade will have a rate of 5% after upgrade is complete.

Yes in this upgrade the rate will be changes to 5% but if i remember it correctly a gov param change without an upgrade will have no effect on the current val set but will have an effect on new validators/ validator commission changes.

ChainUp & NewHuo is excited to perform the upcoming node upgrade ! appreciate the detailed upgrade documentation previously provided. Does the upcoming upgrade will automatically set the rate to 5% for all validators?

This upgrade migrates the state to enforce the min 5% commission rate – gaia/app/upgrades/v15/upgrades.go at v15.0.0-rc1 · cosmos/gaia · GitHub

The upcoming upgrade will automatically raise the rate to 5% for any validators under 5%. There will be no change in commission rate for any validators currently at 5% or higher.

Redundant question was removed as many people answered the same question.

btruax:

Sets the min commission rate staking parameter to 5% and updates the commission rate for all validators accordingly (according to governance proposal 826).

This change will help small validators stay in the game, letting them keep pace with the big players. This way, the voting power within the network stays more balanced.

btruax:

Reject MsgVote messages from accounts with less than 1 ATOM staked.

This change is a welcome development in combating spam and bot votes on the network, allowing for clearer visibility into authentic user data.

Appreciate the hard work

Looking forward to it.

Yes thats the issue/open question i have about this upgrade.

If we change the paramater in the future (for example to 10%) we will have to migrate the state in an later update again. During the timeframe of the success of this hypothetical proposal and the upgrade, will new validators be forced to use the 10% min_commission and old validators will still be able to use the old min_commission of 5%?

The MinCommissionRate param is only used for CreateValidator and EditValidator messages. This means that once the param is updated to e.g., 10%,

• new validators cannot be created with commission rates below 10%;
• existing validators cannot update their commission rate to values below 10%.
  So yeah, to enforce this new min commission rate to every validator, migration will be required.

We have been notified of an issue with the v15 upgrade that may interfere with operations on the Asteroid Protocol. There is a potential workaround identified and our team is assessing implementation timing. We want to ensure that we are fully supporting all apps that are built on Gaia. At the moment, we will be delaying the final release until next week. I will update this forum post with further information on timing if required.

Thanks you for confirming my assumption.

I think MinCommissionRate should not be a governance paramter since it doesnt result in an immediate change of the commission rate of all validators but creates an unfair advantage over new validators.

I understand that the chances that this will happen are very small but inequalities like this should be avoided by design.

There is an issue on SDK staking: bump all commission rate below param · Issue #10540 · cosmos/cosmos-sdk · GitHub and also a PR feat(x/staking): update validators min commission rate after `MsgUpdateParams` by julienrbrt · Pull Request #19537 · cosmos/cosmos-sdk · GitHub. This means that once we update to this version of SDK (probably 0.51), upgrading the MinCommissionRate param will automatically bump the commission rate for all validators.

@Flo thanks for bringing this up by the way It’s a very good point.