v6.7.2

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.7.2

Highlights:

• cosmos-sdk update to v0.47.15
• quick fix for leveraged liquidate
• fix the max_withdraw query
• deps upgrade

CHANGELOG

Validators

Update Price Feeder to umee/2.4.4+.

NOTE: after the upgrade, you should restart your Price Feeder. We observed that Price Feeder doesn't correctly re-establish a connection after the chain upgrade.

libwasmvm update

Our dependencies have been updated. The binary requires libwasmvm v1.5.5. When you build the binary from source on the server machine you probably don't need any change. However, when you download a binary from GitHub, or from another source, make sure you update the /usr/lib/libwasmvm.<cpu_arch>.so. For example:

• copy from $GOPATH/pkg/mod/github.com/!cosm!wasm/[email protected]/internal/api/libwasmvm.$(uname -m).so
• or download from github wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.5.5/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

You don't need to do anything if you are using our Docker image.

Upgrade instructions

• Download latest binary or build from source.
• Make sure libwasmvm.$(uname -m).so is properly linked
  • Run the binary to make sure it works for you: umeed version
• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Swap binaries.
• Ensure latest Price Feeder (see compatibility matrix) is running and ensure your price feeder configuration is up-to-date.
• Restart the chain.
• Restart Price Feeder.

You can use Cosmovisor → see instructions.

Docker

Docker images are available in ghcr.io umee-network repository.

v6.7.2-rc1

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.7.2-rc1 (Note: only for testnet network (canon-4))

Highlights:

• cosmos-sdk update to v0.47.15
• quick fix for leveraged liquidate
• fix the max_withdraw query
• deps upgrade

CHANGELOG

Validators

Update Price Feeder to umee/2.4.4+.

NOTE: after the upgrade, you should restart your Price Feeder. We observed that Price Feeder doesn't correctly re-establish a connection after the chain upgrade.

libwasmvm update

Our dependencies have been updated. The binary requires libwasmvm v1.5.5. When you build the binary from source on the server machine you probably don't need any change. However, when you download a binary from GitHub, or from another source, make sure you update the /usr/lib/libwasmvm.<cpu_arch>.so. For example:

• copy from $GOPATH/pkg/mod/github.com/!cosm!wasm/[email protected]/internal/api/libwasmvm.$(uname -m).so
• or download from github wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.5.5/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

You don't need to do anything if you are using our Docker image.

Upgrade instructions

• Download latest binary or build from source.
• Make sure libwasmvm.$(uname -m).so is properly linked
  • Run the binary to make sure it works for you: umeed version
• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Swap binaries.
• Ensure latest Price Feeder (see compatibility matrix) is running and ensure your price feeder configuration is up-to-date.
• Restart the chain.
• Restart Price Feeder.

You can use Cosmovisor → see instructions.

Docker

Docker images are available in ghcr.io umee-network repository.

v6.7.1

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.7.1

Highlights:

• fix the max_withdraw query
• deps upgrade

What's Changed

• build(deps): Bump codecov/codecov-action from 4.6.0 to 5.0.2 by @dependabot in #2629
• build(deps): Bump github.com/stretchr/testify from 1.9.0 to 1.10.0 by @dependabot in #2634
• build(deps): Bump codecov/codecov-action from 5.0.2 to 5.0.7 by @dependabot in #2632
• build(deps): Bump DavidAnson/markdownlint-cli2-action from 17 to 18 by @dependabot in #2628
• build(deps): Bump github.com/mgechev/revive from 1.3.9 to 1.5.1 by @dependabot in #2627
• fix: fix the query for max withdraw by @gsk967 in #2638
• build(deps): Bump codecov/codecov-action from 5.0.7 to 5.1.1 by @dependabot in #2637
• docs: update the release notes and changelog for v6.7.1 by @gsk967 in #2639

Full Changelog: v6.7.0...v6.7.1

Validators

NOTE: A consensus chain upgrade is not required; simply replace the binary.

Update Price Feeder to umee/2.4.4+.

NOTE: after the upgrade, you should restart your Price Feeder. We observed that Price Feeder doesn't correctly re-establish a connection after the chain upgrade.

libwasmvm update

Our dependencies have been updated. The binary requires libwasmvm v1.5.5. When you build the binary from source on the server machine you probably don't need any change. However, when you download a binary from GitHub, or from another source, make sure you update the /usr/lib/libwasmvm.<cpu_arch>.so. For example:

• copy from $GOPATH/pkg/mod/github.com/!cosm!wasm/[email protected]/internal/api/libwasmvm.$(uname -m).so
• or download from github wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.5.5/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

You don't need to do anything if you are using our Docker image.

Upgrade instructions

• Download latest binary or build from source.
• Make sure libwasmvm.$(uname -m).so is properly linked
  • Run the binary to make sure it works for you: umeed version
• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Swap binaries.
• Ensure latest Price Feeder (see compatibility matrix) is running and ensure your price feeder configuration is up-to-date.
• Restart the chain.
• Restart Price Feeder.

You can use Cosmovisor → see instructions.

Docker

Docker images are available in ghcr.io umee-network repository.

v6.7.0

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.7.0

Highlights:

• cosmos SDK v0.47.14 update.
• cometbft v0.37.13 update.
• wasmvm v1.5.5 update.
• ibc-go v7.8.0 update.

CHANGELOG

Validators

Upgrade Title (for Cosmovisor): v6.7.0.

Update Price Feeder to umee/2.4.4+.

NOTE: after the upgrade, you should restart your Price Feeder. We observed that Price Feeder doesn't correctly re-establish a connection after the chain upgrade.

libwasmvm update

Our dependencies have been updated. The binary requires libwasmvm v1.5.5. When you build the binary from source on the server machine you probably don't need any change. However, when you download a binary from GitHub, or from another source, make sure you update the /usr/lib/libwasmvm.<cpu_arch>.so. For example:

• copy from $GOPATH/pkg/mod/github.com/!cosm!wasm/[email protected]/internal/api/libwasmvm.$(uname -m).so
• or download from github wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.5.5/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

You don't need to do anything if you are using our Docker image.

Upgrade instructions

• Download latest binary or build from source.
• Make sure libwasmvm.$(uname -m).so is properly linked
  • Run the binary to make sure it works for you: umeed version
• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Swap binaries.
• Ensure latest Price Feeder (see compatibility matrix) is running and ensure your price feeder configuration is up-to-date.
• Restart the chain.
• Restart Price Feeder.

You can use Cosmovisor → see instructions.

Docker

Docker images are available in ghcr.io umee-network repository.

Full Changelog: v6.6.0...v6.7.0

v6.7.0-rc1

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.7.0-rc1

Highlights:

• cosmos SDK v0.47.14 update.
• cometbft v0.37.13 update.
• wasmvm v1.5.5 update.
• ibc-go v7.8.0 update.

CHANGELOG

Validators

Upgrade Title (for Cosmovisor): v6.7.0-rc1.

Update Price Feeder to umee/2.4.4+.

NOTE: after the upgrade, you should restart your Price Feeder. We observed that Price Feeder doesn't correctly re-establish a connection after the chain upgrade.

libwasmvm update

Our dependencies have been updated. The binary requires libwasmvm v1.5.5. When you build the binary from source on the server machine you probably don't need any change. However, when you download a binary from GitHub, or from another source, make sure you update the /usr/lib/libwasmvm.<cpu_arch>.so. For example:

• copy from $GOPATH/pkg/mod/github.com/!cosm!wasm/[email protected]/internal/api/libwasmvm.$(uname -m).so
• or download from github wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.5.5/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

You don't need to do anything if you are using our Docker image.

Upgrade instructions

• Download latest binary or build from source.
• Make sure libwasmvm.$(uname -m).so is properly linked
  • Run the binary to make sure it works for you: umeed version
• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Swap binaries.
• Ensure latest Price Feeder (see compatibility matrix) is running and ensure your price feeder configuration is up-to-date.
• Restart the chain.
• Restart Price Feeder.

You can use Cosmovisor → see instructions.

Docker

Docker images are available in ghcr.io umee-network repository.

v6.6.0

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.6.0

Highlights:

• Cosmos SDK v0.47.13 update.
• Adding new auction module to our app.
• Removing crisis module from our app.

Auction module

We propose a new Cosmos SDK module, that will provide mechanism for protocol owned auctions. UX Chain will now auction a portion of collected fees and introduce a token burning mechanism, unlocking a way to a potentially deflationary UX token.
Documentation: x/auction/README.md

Validators

Upgrade Title (for Cosmovisor): v6.6

Update Price Feeder to umee/2.4.3+.

NOTE: after the upgrade, you should restart your Price Feeder. We observed that Price Feeder doesn't correctly re-establish a connection after the chain upgrade.

libwasmvm update

Our dependencies have been updated. The binary requires libwasmvm v1.5.2. When you build the binary from source on the server machine you probably don't need any change. However, when you download a binary from GitHub, or from another source, make sure you update the /usr/lib/libwasmvm.<cpu_arch>.so. For example:

• copy from $GOPATH/pkg/mod/github.com/!cosm!wasm/[email protected]/internal/api/libwasmvm.$(uname -m).so
• or download from github wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.5.2/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

You don't need to do anything if you are using our Docker image.

Upgrade instructions

• Download latest binary or build from source.
• Make sure libwasmvm.$(uname -m).so is properly linked
  • Run the binary to make sure it works for you: umeed version
• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Swap binaries.
• Ensure latest Price Feeder (see compatibility matrix) is running and ensure your price feeder configuration is up-to-date.
• Restart the chain.
• Restart Price Feeder.

You can use Cosmovisor → see instructions.

Docker

Docker images are available in ghcr.io umee-network repository.

Full Changelog: v6.5.0...v6.6.0

v6.6.0-rc1

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.6.0-rc1 (This release only for canon-4 testnet)

Highlights:

• Cosmos SDK v0.47.13 update.
• Adding new auction module to our app.
• Removing crisis module from our app.

CHANGELOG

Auction module

We propose a new Cosmos SDK module, that will provide mechanism for protocol owned auctions. UX Chain will now auction a portion of collected fees and introduce a token burning mechanism, unlocking a way to a potentially deflationary UX token.
Documentation: x/auction/README.md

Validators

Upgrade Title (for Cosmovisor): v6.6-rc1.

Update Price Feeder to umee/2.4.3+.

NOTE: after the upgrade, you should restart your Price Feeder. We observed that Price Feeder doesn't correctly re-establish a connection after the chain upgrade.

libwasmvm update

Our dependencies have been updated. The binary requires libwasmvm v1.5.2. When you build the binary from source on the server machine you probably don't need any change. However, when you download a binary from GitHub, or from another source, make sure you update the /usr/lib/libwasmvm.<cpu_arch>.so. For example:

• copy from $GOPATH/pkg/mod/github.com/!cosm!wasm/[email protected]/internal/api/libwasmvm.$(uname -m).so
• or download from github wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.5.2/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

You don't need to do anything if you are using our Docker image.

Upgrade instructions

• Download latest binary or build from source.
• Make sure libwasmvm.$(uname -m).so is properly linked
  • Run the binary to make sure it works for you: umeed version
• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Swap binaries.
• Ensure latest Price Feeder (see compatibility matrix) is running and ensure your price feeder configuration is up-to-date.
• Restart the chain.
• Restart Price Feeder.

You can use Cosmovisor → see instructions.

Docker

Docker images are available in ghcr.io umee-network repository.

Full Changelog: v6.5.0...v6.6.0-rc1

New Contributors

• @closeobserve made their first contribution in #2573

v6.5.0

What's Changed

In this release, we are introducing validations for the IBC transfer message receiver address and memo fields. These enhancements aim to address and resolve the recent incident involving spam IBC transfer transactions.

• Maximum length for IBC transfer memo field: 32'768 characters
• Maximum length for IBC transfer receiver address field: 2'048 characters
• Bump cosmos-sdk to v0.47.12
• Bump ibc-go to v7.6.0

Full Changelog: v6.4.1...v6.5.0

Docker

Docker images are available in ghcr.io umee-network repository.

v6.5.0-rc2

In this release, we are introducing validations for the IBC transfer message receiver address and memo fields. These enhancements aim to address and resolve the recent incident involving spam IBC transfer transactions.

• Maximum length for IBC transfer memo field: 32'768 characters
• Maximum length for IBC transfer receiver address field: 2'048 characters
• Bump ibc-go to v7.5.1.

Full Changelog: v6.4.1...v6.5.0-rc2

v6.4.1

Release Notes

The Release Procedure is defined in the CONTRIBUTING document.

v6.4.1

This release updates our dependencies and applies latest patches to the v6.4.x line. All validators must update to this patch release.

Docker

Docker images are available in ghcr.io umee-network repository.