Osmosis v32 Software Upgrade
Osmosis proposal #1054: This is a proposal to do a software upgrade to the v32.0.0 software tag of the Osmosis codebase on block height **73304000**, which i...
Yes
100%
No
0%
Abstain
0%
Veto
0%
AI Summary
gpt-6-luna - generated 10/23/2026, 1:18:34 AM
Osmosis v32 Software Upgrade
Proposal 1054 upgrades Osmosis to v32.0.0 at block 73,304,000, estimated for October 27, 2026 at 15:00 UTC. It restores approved Alloyed BTC backing, moves non-base-token balances stuck in ProtoRev to the Liquidity SubDAO for conversion to OSMO and burning, and includes stability improvements. The upgrade is expected to halt onchain activity for about 15 minutes.
- Upgrade to Osmosis v32.0.0 is scheduled for block 73,304,000; timing is an estimate because block times vary.
- Moves 22.65060846 frozen allBTC to the Liquidity SubDAO under the recovery approved in Proposal 1044; the account's OSMO remains untouched.
- Transfers non-base-denom ProtoRev balances to the Liquidity SubDAO to swap to OSMO and burn; base-denom balances remain on their normal distribution path.
- A token that cannot be moved will be skipped, and the upgrade will continue.
- The upgrade is expected to pause onchain activity for approximately 15 minutes.
Voter Impact
A yes vote authorizes the v32.0.0 upgrade and its specified recovery and ProtoRev balance transfers. Voters should weigh the stated OSMO-burn purpose against the planned temporary network halt and variable upgrade timing.
Risk Signals
- The upgrade time is uncertain because block times have high variance.
- Onchain activity is expected to stop for about 15 minutes during the upgrade.
- Some ProtoRev tokens may be skipped if they cannot be moved; the proposal does not specify how such balances would be handled afterward.
Original Proposal Text
This is a proposal to do a software upgrade to the v32.0.0 software tag of the Osmosis codebase on block height **73304000**, which is estimated to occur on **Tuesday, 27th October 2026, UTC 15:00**. Block times have high variance, so please monitor the chain for more precise time estimates. # **Upgrade Features** This upgrade carries out the Alloyed BTC recovery approved by governance and migrates tokens trapped in the ProtoRev module to be able to be sold for additional OSMO burn. The release also includes miscellaneous enhancements and fixes to improve network stability. ## [Alloyed BTC Recovery](https://github.com/osmosis-labs/osmosis/pull/9744) Implements the recovery approved in [Proposal 1044](https://daodao.zone/dao/osmosis/proposals/1044). At the upgrade height, 22.65060846 allBTC frozen on the exploiter's account (`osmo1wq76r2mhqsa9yaygghuwyq4wy6dcsgf8vtzltn`) is moved to the Liquidity SubDAO, to restore Alloyed BTC's backing as that proposal set out. Only the authorised amount of allBTC is moved. The account's OSMO is left in place. This step runs on osmosis-1 only. ## [ProtoRev Stuck Balances](https://github.com/osmosis-labs/osmosis/pull/9760) ProtoRev distributes its profits each day, but only in its base denoms. Profits in any other token build up in the ProtoRev module account, and nothing can move them out. About 84 tokens have accumulated this way, worth roughly $50,000, mostly TIA, AKT and ETH. The upgrade sends every non-base-denom balance in the ProtoRev module account to the Liquidity SubDAO, which will swap them to OSMO and burn it. Base denom balances are untouched and continue through the normal daily distribution. If any single token cannot be moved, it is skipped and the upgrade continues. Please see the [**Full Change Log**](https://github.com/osmosis-labs/osmosis/blob/v32.0.0/CHANGELOG.md) for a complete list of changes. # **Getting Prepared for the Upgrade** ## **Binary Installation** To build the binary, be sure to install [**Golang 1.23.4**](https://github.com/osmosis-labs/osmosis/blob/v32.0.0/go.mod#L3) 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/v32/bin/. If not using Cosmovisor, wait for your node to halt at the upgrade height, then install and run the v32.0.0 binary. ## **Details of Upgrade Time** The proposal targets the upgrade proposal block to be **73304000**, anticipated to be on **Tuesday, 27th October 2026, UTC 15:00**. Note that block times have high variance, so keep monitoring the time. See the countdown [**HERE**](https://www.mintscan.io/osmosis/block/73304000). The upgrade is anticipated to take approximately 15 minutes, during which time there will be no onchain activity on the network. In the event of an issue at upgrade time, coordinate via the validators channel in [Discord](https://discord.com/invite/osmosis) to come to a quick emergency consensus and mitigate any further issues. More details: Not Used