Osmosis v18.0.0 🧪

In the v17 upgrade, more CL pools were launched that are linked to a balancer pool with the same token pair.

Due to a historic issue specific to mainnet, a state entry now used in incentive distribution was in an invalid state, causing a panic.
The issue was not caught in the state exported from mainnet to testnet because it executes InitGenesis() logic which corrects the problem, meaning that this issue was not replicated on testnet. (And could not have been, without custom logic to recreate this invalid state)

While this issue does not cause a chain halt, it currently silently fails and prevents incentives from being distributed to any Osmosis pool.

All funds are safe and are NOT at risk. The rewards that have not been distributed since v17 will be distributed after the v18 upgrade.

For internal OSMO incentives, the day after the upgrade, users will get 2x the regular amount (for the missed epoch and for the current epoch).

For external incentives, the rewards will continue distributing in regular amounts, with a delay by one epoch.

Future testing procedures will export mainnet state to testnet in a different manner to ensure that InitGenesis() does not overwrite any invalid historical states from Mainnet.

What Changed

See the full changelog here

Usage

🐳 Docker

The following Docker images are available in our registry:

Image	Description
osmolabs/osmosis:18.0.0	Default image. Based on Distroless image
osmolabs/osmosis:18.0.0-distroless	Distroless image (same as above)
osmolabs/osmosis:18.0.0-nonroot	Distroless non root image
osmolabs/osmosis:18.0.0-alpine	Alpine image

Example:

docker run osmolabs/osmosis:18.0.0 version
# v18.0.0

All the images have support for arm64 and amd64 architectures.

🔨 Build from source

git clone https://github.com/osmosis-labs/osmosis
cd osmosis && git checkout v18.0.0
make install

⚡️ Download binaries

Binaries for linux amd64 and arm64 are available below.
Darwin users should build binaries from source.