Osmosis Proposal: #861
Osmosis v27 Software Upgrade
Turnout:55.63%
Quorum:20.00%
Yes: 99.9%
189,718,774 OSMO
No: 0%
24,027 OSMO
No With Veto: 0%
2,959 OSMO
Abstain: 0.1%
115,779 OSMO
Voting Period
-Proposer
osmo19w2t4ue7qpdh6022m3yxmxvv3w7jla7u3hfq0r
Deposit End
Submit Time
Description
This is a proposal to do a software upgrade to the v27.0.0 software tag of the Osmosis codebase on block height 24250100, which is estimated to occur on Tuesday, November 19th, UTC 14:00. Block times have high variance, so please monitor the chain for more precise time estimates.
Upgrade Features
This upgrade primarily consists of fixes and improvements for the Osmosis codebase, ensuring that Osmosis continues to operate with the most up-to-date and secure software available.
Patches
- Bank Supply Offsets fixed - these reported an incorrect circulating supply for OSMO since v26. This has been fixed on the endpoint since v26.0.2
- Export to genesis state fixed by adding a key missed during the upgrade to Cosmos SDK v0.50.0
- Cosmwasm vm updated to v2.1.3
- Cosmos SDK updated to v0.50.10
- CometBFT updated to v0.38.12
- Cosmwasm Optimizer updated to 0.16.0
Please see the Full Change Log for a complete list of optimizations and any API changes.
Getting Prepared for the Upgrade
Binary Installation
To build the binary, be sure to install Golang 1.22.7 or higher
As always, we recommend validators utilize 64GB of RAM. Since state migration is relatively negligible in this upgrade, it is possible to get away with less, but it is still not recommended. If you are unable to have 64GB of RAM, at a minimum, have a total of 64GB of swap set to prevent out-of-memory errors.
If using Cosmovisor, manually build & copy the osmosisd binary to /cosmovisor/upgrades/v27/bin/.
If not using Cosmovisor, wait for your node to halt at the upgrade height, then install and run the v27.0.0 binary.
Details of Upgrade Time
The proposal targets the upgrade proposal block to be 24250100, anticipated to be on Tuesday, November 19th, UTC 14:00. Note that block times have high variance, so keep monitoring the time. See the countdown HERE.
The upgrade is anticipated to take approximately 15 minutes, during which time there will be no on-chain activity on the network.
In the event of an issue at upgrade time, coordinate via the validators channel in Discord to come to a quick emergency consensus and mitigate any further issues.