HackMD
Osmosis v5 Boron Upgrade
This proposal proposes that the chain elect to do a software upgrade to the v5.0.0 software tag of the Osmosis codebase on block height 2383300. The timing of this upgrade is crucial to properly execute the Proposal 32 airdrop clawback. This clawback should happen right at the Airdrop end date of December 15th 5PM UTC, thus this upgrade must execute before it.
The upgrade block height 2383300 is estimated to be at December 14th, UTC 2:30PM. Block times have high variance, so please be monitor the chain for more precise time estimates.
Upgrade features
This upgrade adds features such as:
- Upgrade Cosmos-SDK to SDK v0.44 from SDK v0.42 For a full list of updates in Cosmos-SDK v0.44.3 please see its changelog. Noteable highlights include:
- Authz - Allows granting arbitrary privileges from one account (the granter) to another account (the grantee).
- New modules:
- Bech32IBC - Allows auto-routing of send msgs to addresses on other chains, once configured by governance. Allows you to do a bank send on Osmosis to a cosmos1… address, and it is automatically sent to the corresponding Cosmos Hub address over IBC. This is a big step in enabling more seemless IBC UX.
- TxFees - Enables validators to easily accept txfees in multiple assets, whitelisted by governance, by declaring minimum fees in OSMO. Alternative fee assets are converted to their OSMO value, using the spot price on their primary OSMO base pair pool. This upgrade pre-whitelists all the assets currently supported on the Osmosis frontend with an OSMO basepair pool.
- Implements Proposal 32 - Clawback of unclaimed Osmo and Ion on airdrop end date. (December 15th, 5PM UTC)
- Upgrade IBC from a standalone module in the SDK to IBC v2. This improves the utility of Ethereum Bridges and Cosmwasm bridges.
- Blocking OFAC banned ETH addresses
- Numerous minor bug fixes, gas fixes, and significant speedups.
See more in the changelog
Getting prepared for the upgrade
All nodes will require 32GB of memory. Swap can be used to achieve this, but getting nodes with 32GB RAM is significantly preferred. Furthermore, NVMe SSD's significantly improve the speed of execution.
Please follow the setup instructions here for how to add swap (if needed), and how to configure cosmovisor to automatically switch binaries for this upgrade: Upgrade Guide.
Namely, configure cosmovisor to auto-restart. (Please note, you have to install cosmovisor from the SDK v0.42.9 branch) Then either auto-download binaries or manually build & copy the osmosisd v5.0.0 binary to .osmosisd/cosmovisor/upgrades/v5/bin/.
If you do not want to use cosmovisor due to cosmovisor reliability issues, please be prepared to upgrade at around 2:30PM UTC, December 14th if this proposal passes.
Details of upgrade time
When the network reaches the halt height, the Osmosis blockchain will be halted. Cosmovisor if configured properly, will then switch the binary used to v5.0.0, and the chain will proceed post upgrade.
The blockchain needs to upgrade before 5PM UTC December 15th, in order to meet Prop 32. Due to stability issues post-epoch it seems best to do the upgrade prior to the epoch, as done in the v4 upgrade. Hence the suggestion of December 14th, 2:30PM UTC.
The proposal targets the upgrade proposal block to be 2383300, anticipated to be at Wednesday December 14th 2:30PM UTC (9:30AM EST). This uses a 1 day average block time of 6.65 seconds per block, derived from Cros-nest dashboard. Note that block times have high variance, so keep monitoring the time.
The upgrade is anticipated to take approx 100 minutes, during which time, there will not be any on-chain activity on the network.
In the event of an issue at upgrade time, we should coordinate via the validators channel in discord.
Testing your upgrade setup
There is a testnet which full nodes can sync to, to test that they have setup cosmovisor correctly on a new node. See #testnet-announcements and #testnet-discussion channels in the Osmosis Discord.
