Osmosis v11.0.0 🧪

This release includes upgrades and improvements that helps prevent spam to both our governance and gamm modules.

What Changed

Improvements

• #2237 Enable charging fee in base denom for CreateGauge and AddToGauge.

SDK Upgrades

• #2245 Upgrade SDK for to v0.45.0x-osmo-v9.2. Major changes:
  • Minimum deposit on proposer at submission time: osmosis-labs/cosmos-sdk#302

Usage

🐳 Docker

The following Docker image is available in our registry:

docker run osmolabs/osmosis:11.0.0 version 
# v11.0.0

The image supports both arm64 and amd64 architectures.

🔨 Build from source

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

⚡️ Download binaries

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

Osmosis v10.1.1 🧪

This is a patch that improves epoch processing time.

What Changed

Improvements

• #2214 Speedup epoch distribution, superfluid component

Full Changelog: v10.1.0...v10.1.1

Usage

🐳 Docker

The following Docker image is available in our registry:

docker run osmolabs/osmosis:10.1.1 version 
# v10.1.1

The image supports both arm64 and amd64 architectures.

🔨 Build from source

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

⚡️ Download binaries

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

Osmosis v10.1.0 🧪

v10.1.0

This upgrade includes minor improvements and bug fixes.

The most visible change for the node operators represents the move of the commit store logs to the Debug level. Previously, these logs had been used for debugging live database issues. Since there is no need for them, they were moved to Debug to reduce noise.

All other changes can be found below.

What Changed

Bug Fixes

• 2011 Fix bug in TokenFactory initGenesis, relating to denom creation fee param.

Improvements

• #2130 Introduce errors in mint types.
• #2000 Update import paths from v9 to v10.

Golang API breaks

• #1937 Change lockupKeeper.ExtendLock to take in lockID instead of the direct lock struct.
• #2030 Rename lockup keeper ResetAllLocks to InitializeAllLocks and ResetAllSyntheticLocks to InitializeAllSyntheticLocks.

SDK Upgrades

• #2146 Upgrade SDK for to v0.45.0x-osmo-v9.1. Major changes:
  • Concurrency query client option: osmosis-labs/cosmos-sdk#281
  • Remove redacted message fix: osmosis-labs/cosmos-sdk#284
  • Reduce commit store logs (change to Debug): osmosis-labs/cosmos-sdk#282
  • Bring back the cliff vesting command: osmosis-labs/cosmos-sdk#272
  • Allow ScheduleUpgrade to come from same block: osmosis-labs/cosmos-sdk#261

Full Changelog: v10.0.1...v10.1.0

Usage

🐳 Docker

The following Docker image is available in our registry:

docker run osmolabs/osmosis:10.1.0 version 
# v10.1.0

The image supports both arm64 and amd64 architectures.

🔨 Build from source

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

⚡️ Download binaries

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

V10.0.0 Osmosis JoinPool relaunch

The v10.0.0 release fixes the JoinPool bug present in v9 of the Osmosis code.

It is state machine compatible with v9 until the ForkHeight.

Upgrade instrructions: https://github.com/osmosis-labs/osmosis/blob/main/networks/osmosis-1/upgrades/v10/guide.md

v9.0.0

The Nitrogen release brings with it a number of features enabling further Cosmwasm development work in Osmosis.
It including breaking changes to the GAMM API's, many developer and node operator improvements for Cosmwasm & IBC, along with new txfee and governance features. In addition to various bug fixes and code quality improvements.

GAMM API changes

API changes were done to enable more CFMM's to be implemented within the existing framework.
Integrators will have to update their messages and queries to adapt, please see https://github.com/osmosis-labs/osmosis/blob/main/x/gamm/breaking_changes_notes.md

Governance Changes

• #1191, #1555 Superfluid stakers now have their votes override their validators votes
• sdk #239 Governance can set a distinct voting period for every proposal type.

IBC

• #1535 Upgrade to IBC v3
• #1564 Enable Interchain account host module
  • See here for the supported messages

Txfees

#1145 Non-osmo txfees now get swapped into osmo everyday at epoch, and then distributed to stakers.

Cosmwasm

Upgrade from wasmd v0.23.x to v0.27.0. This has the following features:

• State sync now works for cosmwasm state
• Cosmwasm builds on M1 macs
• Many security fixes

The TokenFactory module is added to the chain, making it possible for users and contracts to make new native tokens.
Cosmwasm bindings have been added, to make swapping and creating these new tokens easier within the contract ecosystem.

Other Features

• #1629 Fix bug in the airdrop claim script
• #1570 upgrade sdk with app version fix for state-sync
• #1554 local dev environment
• #1541 Add arm64 support to Docker
• #1535 upgrade wasmd to v0.27.0.rc3-osmo and ibc-go to v3
• #1435 x/tokenfactory create denom fee for spam resistance
• #1253 Add a message to increase the duration of a bonded lock.

Full Changelog: v8.0.1...v9.0.0

v8.0.0

This upgrade is a patch that must be hard forked in, as on-chain governance of Osmosis approved proposal 227 and proposal 228.

This upgrade includes:

• Adding height-gated AnteHandler message filter to filter unpooling tx pre-upgrade.
• At block height 4402000
  • accelerates prop 225, which in turn moves incentives from certain pools according to props 222-224
  • Adds a msg allowing unpooling of UST pools. This procedure is initiated by whitelisting pools 560, 562, 567, 578, 592, 610, 612, 615, 642, 679, 580, 635. Unpooling allows exiting whitelisted pools directly, finish unbonding duration with the exited tokens instead of having to wait unbonding duration to swap LP shares back to collaterals. This procedure also includes locks that were already unbonding pre-upgrade and locks that were superfluid delegated.

Proposed Upgrade Process

• Every node should upgrade their software version to v8.0.0 before the upgrade block height 4402000. If you use cosmovisor, simply swap out the binary at upgrades/v7/bin to be v8.0.0, and restart the node. Do check cosmovisor version returns v8.0.0

v7.3.0

This release focuses on fixing more concurrency issues related to queries.

A few months ago there was a change allowing GRPC queries to be concurrent with the ABCI commit flow that introduced several data races. These were stemming from incorrect propagation of the requested height as well as relaxing the synchronization requirements too much. This release eliminates these data races by propagating the requested height correctly. Additionally, simulation and Tendermint queries are now synchronous with the ABCI commit flow. As a result, node operators may experience slower query performance when simulating transactions or querying Tendermint in exchange for safety.

What's Changed

• fix(cli): add chain-id to PrepareGenesis cmd (backport #1393) by @mergify in #1395
• chore: upgrade sdk to v0.45.0x-osmo-v7.9 by @p0mvn in #1390

Full Changelog: v7.2.1...v7.3.0

v7.2.1

What's New

Main features and issues addressed in this upgrade:

• Add new forceprune command to the CLI developed by Valnodes. This allows users to prune their state.db and blockstore.db on command, preventing database size creep as we are currently experiencing. This update adds back the tendermint command. (backport #1262) by @moniya12 in #1320
• Add upcoming-gauges-per-denom query to the CLI (backport #1195) by @xBalbinus in #1257
• chore: upgrade sdk to v0.45.0x-osmo-v7.8.1 by @czarcas7ic in #1357
  • fix: tendermint command added back into the daemon (backport #193) by @czarcas7ic in osmosis-labs/cosmos-sdk#194
  • refactor: address snapshot/pruning refactor comments upstream (backport #184) by @p0mvn in osmosis-labs/cosmos-sdk#209
  • feat: support send and recv msg size for gRPC (backport #170) by @alexanderbez in osmosis-labs/cosmos-sdk#210
• fix: Enable build in pre-montery machines (backport #1351) by @mattverse in #1358

Osmosis Full Changelog: v7.2.0...v7.2.1
Osmosis SDK Fork Full Changelog: v0.45.0x-osmo-v7.7...v0.45.0x-osmo-v7.8.1

v7.2.0

Description

This release focuses on the upgrade to Tendermint v0.34.19. The summary of the 2 main Tendermint improvements follows:

• Reduced lock contention in p2p

In earlier versions, there were lock contentions in the Tendermint p2p logic, causing instabilities during epoch processing, especially with sentry setups. These instabilities were causing sentries to execute a block before gossiping it to the validator, resulting in missed blocks. Furthermore, nodes were forced to reconnect to the entire p2p network at long epoch times / queries. These problems are now alleviated with the new release.

• reset-state command added

It removes the following tendermint databases while preserving the private validator data:

• blockstore.db
• state.db
• cs.wal
• evidence.db
• tx_index.db
• peerstore.db

For more info, see:

Osmosis Full Changelog: v7.1.0...v7.2.0
Osmosis SDK Fork Full Changelog: osmosis-labs/cosmos-sdk@v0.45.0x-osmo-v7.6...v0.45.0x-osmo-v7.7
Tendermint Changelog: https://github.com/tendermint/tendermint/blob/v0.34.19/CHANGELOG.md#v0.34.19-v0.34.15

v7.1.0

Description

This release focuses on various stability improvements. Furthermore, it has a change to the epoch event. The summary follows:

Block.Header.AppHash Crash Mitigation

Several data races have been fixed to mitigate the impact of the app hash bug. Some of them were related to concurrently committing and querying a node which explains relayers having the highest impact. Due to the non-deterministic nature of this bug, there is no guarantee that the issue has been resolved completely. However, no app hash bug has been observed with the new changes so far. We would appreciate any feedback on this from people running nodes in production. Additionally, more logs were added to help with debugging if the app hash bug does happen again.

Cache Reconfiguration to Reduce RAM Usage

An additional fast storage cache was introduced in v6.3.0. Its size was determined by iavl-cache-size in app.toml. However, the default value was simply too large for the new cache. As a result, it was causing the cache to grow as nodes stayed online, exhausting memory. The fast node cache size is now separated from the iavl-cache-size config and lowered in the v7.1.0 release. Currently, it is non-configurable but that should become possible in a subsequent release.

Pruning and Snapshot Settings

Fast storage change introduced overhead related to taking snapshots with rigorous pruning settings. It had become possible to attempt to prune a height that is being snapshotted. As a result, a node would fail with this error. To temporarily mitigate, we required node operators to have unnecessarily large pruning-keep-recent. With this change, this requirement is no longer needed. Snapshots may work on pruning-everything or rigorous custom pruning.

Changes to pruning config in app.toml:

• pruning-keep-every was removed and no longer exists (This change is done in a future SDK release as well)
• The most rigorous pruning settings are pruning = "everything". It is equivalent to pruning = "custom" with pruning-keep-recent = "10" and pruning-interval = "10"
• If more rigorous than the mentioned-above pruning settings are selected, the node will fail to start. In such a case, an error is printed, guiding to select the appropriate configuration.

Epoch Event Change

The AfterEpochEnd event was being called with an epoch number that is off by one, so anyone parsing epoch data off of that event will need to correct the off by one error. See #830 for more details.

Full Changelog

v7.0.4...v7.1.0