osmosis

Prop 1054: Osmosis v32 Software Upgrade

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

Implements the recovery approved in Proposal 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

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 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 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.

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 to come to a quick emergency consensus and mitigate any further issues.

Field
Data
info
https://raw.githubusercontent.com/osmosis-labs/osmosis/main/networks/osmosis-1/upgrades/v32/mainnet/v32_binaries.json
name
v32
time
0001-01-01T00:00:00Z
height
73304000
upgraded_client_state