v5.0.0-rc1

rc1 of v5.0.0, for testing.

High level overview of upgrades included in this:

• Upgrade to SDK v0.44, include authz module. Also upgrade to IBC v2
• Add Bech32IBC, so once governance approves certain IBC channels, you can just send to other chains addresses like cosmos1..., and the chain will handle IBC'ing it out for you
• Allow whitelisted tx fee tokens based on conversion rate to OSMO. This means that a single min-fee can be set in osmo, and a full node will accept fees in atoms, etc. at an equivalent spot price derived from the AMMs. (The tx fees are not auto-converted)
• Reduce growth rate of epoch time due to common user actions
• {Minor bug fixes}

Relayer speed bump

This is a relayer speed bump that has a much larger IAVL cache.

v4.2.0 - Epoch and mempool improvements

The v4.2.0 release includes significant reductions in the I/O time used at the Osmosis epoch, and mempool improvements.
The prior release, v4.1.0, improved the CPU time taken by the epoch significantly, but did not change the I/O time which thanks to very detailed profiling from @blockpane , was determined to be the bottleneck.

This is not a permanent fix for I/O time, but instead a constant factor improvement.

As a headsup, there has been two full nodes who tried the new software version and had an app hash issue. This has not been seen on any other nodes using this software version. It is suspected that there was some unfortunate db corruption unrelated to update (or perhaps the new Tendermint version), but please do exercise caution / gradual rollouts.

What's Changed

• Lower epoch I/O time by an expected 2-3x #561
• Add local mempool filter to block txs that take > 25M gas. (This in large part fixed the chain congestion issue of 10/28)
• Add local mempool filter to block redundant IBC relays #556
• Upgrade to Tendermint v0.34.14 by @faddat in #529
• Add rollback to command tree by @jackzampolin in #555

Also huge thanks to @blockpane who was instrumental in diagnosing the I/O time issues, and @jackzampolin @faddat @clemensgg @UnityChaos @imperator-co @Wolfcontract for the work in testing the various new versions here!

v4.1.0 - Minor release for Epoch time reduction

This release provides large speedups to the Osmosis epoch time. It does by reducing the amount of events emitted, to have less redundant data. It now only emits one event per address receiving LP rewards.

This upgrade is state-compatible with v4.0.0, and has been tested to be so with many different node operators now. It is encouraged for full nodes & validators to upgrade, in order to significantly reduce their load every epoch.

v4.0.0 - Osmosis stability upgrade (Berylium)

Osmosis v4.0.0 - Berylium

This upgrade is a large stability upgrade to Osmosis. It brings with it faster epochs, and improved computation time for various on-chain operations, and fixes to the high gas amounts needed for bonding and unbonding txs.

The features of this upgrade are:

• Fixing gas issues for bonding and unbonding tokens (NOTE: issues at epoch of there just being super high amounts of activity may still persist, with it taking seconds for txs to get into a block)
• Removing the need for users to withdraw locked tokens once they are finished unlocking
• Adding a governance parameter for a minimum fee to create a pool.
• Implements prop 12

See more in the changelog

v4.0.0-rc1

Release candidate #1 for osmosis v4

This change primarily brings numerous stability improvements to the chain. It brings with it faster epochs, and improved computation time for various on-chain operations, and fixes to the high gas amounts needed for bonding and unbonding txs.

The features of this upgrade are:

• Fixing gas issues for bonding and unbonding tokens (NOTE: issues at epoch of there just being super high amounts of activity may still persist, with it taking seconds for txs to get into a block)
• Removing the need for users to withdraw locked tokens once they are finished unlocking
• Adding a governance parameter for a minimum fee to create a pool.

If no bugs are found, this state machine will be what is on Osmosis v4.

More thorough changelog here

v3.1.0 Governance Patch

This upgrade is meant as a patch that must be hard forked in, due to a bug in proposal 16 breaking on-chain governance of Osmosis. It prevents governance proposals from moving into voting period. Details of the bug are at the bottom. This is the version that should be used, not v2.0.0 or v3.0.0.

This upgrade includes:

• Update to Cosmos-SDK v0.42.9, which fixes state syncing.
• At block height 712000
  • Fixing the immediate governance issue, by changing the min_deposit parameter to what was intended
  • Fixing the bug in min_commission_rate, that allowed validators to create a validator with a lower rate than the minimum. It also bumps up all validators to the minimum.

Proposed Upgrade Process

• Every node should upgrade their software version from v1.0.x to v3.1.0 before the upgrade block height 712000. If you use cosmovisor, simply swap out the binary at genesis/bin to be v3.1.0, and restart the node.
• Upon upgrading their setup, every validator should place a deposit on a signalling proposal, to signal readiness for the upgrade. (1uosmo suffices)
• Every node should check in between August 10th 1:00AM UTC and 2:00PM UTC, and see if 2/3rds of validators have put a non-zero deposit on the proposal. If so, no further action needed (unless they didn't upgrade yet, in which case they should). If 2/3rds of validators have not signalled readiness by this time, then the upgrade is considered to have not reached agreement, and all nodes should downgrade their binary back to v1.0.x for further coordination.

Governance Bug

In proposal 16, the 'min_deposit' value on the proposal was set to 500osmo and not the intended 500000000uosmo. On chain, the denomination "osmo" doesn't exist, there is only "uosmo" (Similar to how on Bitcoin there are only sats).

Due to this parameter change, a sufficient governance deposit to enter on-chain voting must be in Osmo, which is a denomination that does not exist on chain. Thus no new governance proposals can enter a voting period and get decided on chain.

[Do not use] v3.0.0 Governance Patch

This upgrade is meant as a patch that must be hard forked in, due to a bug in proposal 16 breaking on-chain governance of Osmosis. It prevents governance proposals from moving into voting period. Details of the bug are at the bottom. This is the version that should be used, not v2.0.0.

This upgrade includes:

• Update to Cosmos-SDK v0.42.9, which fixes state syncing.
• At block height 712000
  • Fixing the immediate governance issue, by changing the min_deposit parameter to what was intended
  • Fixing the bug in min_commission_rate, that allowed validators to create a validator with a lower rate than the minimum. It also bumps up all validators to the minimum.

Proposed Upgrade Process

• Every node should upgrade their software version from v1.0.x to v3.0.x before the upgrade block height 712000. If you use cosmovisor, simply swap out the binary at genesis/bin to be v3.0.0, and restart the node.
• Upon upgrading their setup, every validator should place a deposit on a signalling proposal, to signal readiness for the upgrade. (1uosmo suffices)
• Every node should check in between August 10th 1AM UTC and 1PM UTC, and see if 2/3rds of validators have put a non-zero deposit on the proposal. If so, no further action needed (unless they didn't upgrade yet, in which case they should). If 2/3rds of validators have not signalled readiness by this time, then the upgrade is considered to have not reached agreement, and all nodes should downgrade their binary back to v1.0.x for further coordination.

Governance Bug

In proposal 16, the 'min_deposit' value on the proposal was set to 500osmo and not the intended 500000000uosmo. On chain, the denomination "osmo" doesn't exist, there is only "uosmo" (Similar to how on Bitcoin there are only sats).

Due to this parameter change, a sufficient governance deposit to enter on-chain voting must be in Osmo, which is a denomination that does not exist on chain. Thus no new governance proposals can enter a voting period and get decided on chain.

v2.0.0 Governance Patch Upgrade

This upgrade is meant as a patch that must be hard forked in, due to a bug in proposal 16 breaking on-chain governance of Osmosis. Details of the bug are at the bottom.

UPDATE: The version that will be used on-chain will not be this version, due to a bug in the cosmos-sdk version v0.42.7

This upgrade includes

• Fixing the immediate governance issue, by changing the min_deposit parameter to what was intended
• Fixing the bug in min_commission_rate, that allowed validators to create a validator with a lower rate than the minimum. It also bumps up all validators to the minimum.
• Update to Cosmos-SDK v0.42.7, which fixes state syncing.

Governance Bug

In proposal 16, the 'min_deposit' value on the proposal was set to 500osmo and not the intended 500000000uosmo. On chain, the denomination "osmo" doesn't exist, there is only "uosmo" (Similar to how on Bitcoin there are only sats).

Due to this parameter change, a sufficient governance deposit to enter on-chain voting must be in Osmo, which is a denomination that does not exist on chain. Thus no new governance proposals can enter a voting period and get decided on chain.

v2.0.0-rc2

Upgrade to SDK version v0.42.7 which fixes state sync