v4.0.0

Release Notes

Release Procedure is defined in the CONTRIBUTING document.

v4.0.0

This release contains the Historacle Upgrade, a pricing update which improves the way we treat quickly-changing prices in the leverage module.

• See the Historacle Design Doc for a description of how these prices are calculated.
• See the Leverage Module Spec for a description of how these prices are treated by the leverage protocol.

Please Note:

• This upgrade requires the use of Price Feeder V2.0.3 immediately after the Umee v4.0 Upgrade. Prior to this upgrade, you should stay on Price Feeder V2.0.2.
• To run the provided binary, you have to have libwasmvm.x86_64.so v1.1.1 in your system lib directory.

Building from source will automatically link the libwasmvm.x86_64.so created as a part of the build process (you must build on the same host as you run the binary, or copy the libwasmvm.x86_64.so your lib directory).

If you build on system different than Linux amd64, then you need to download appropriate version of libwasmvm (eg from CosmWasm/wasmvm Relases) or build it from source (you will need Rust toolchain).

Otherwise you have to download libwasmvm. Please check Supported Platforms. Example:

wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.1.1/internal/api/libwasmvm.$(uname -m).so -P /lib/

Additional highlights:

• 1694 MsgMaxWithdraw, MsgMaxBorrow and MsgRepay won't return errors if there is nothing to withdraw, borrow or repay respectively. Leverage ErrMaxWithdrawZero and ErrMaxBorrowZero has been removed.

Please see the CHANGELOG for an exhaustive list of changes.

Update instructions

• Note: Skip this step if you build binary from source and are able to properly link libwasmvm.
  • Download libwasmvm:

$ wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.1.1/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Run latest Price Feeder (v2.0.3) - updated
• Swap binaries.
• Restart the chain.

You can use Cosmovisor → see instructions.

NOTE: BEFORE the upgrade, make sure the binary is working and libwasmvm is in your system. You can test it by running ./umeed-v4.0.0 --version.

Docker

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

price-feeder/v2.0.3

Changelog

v2.0.3

The main change in this version of the price feeder is to be compatible with the umeed v4.0.0 binary. Please see the Release Compatibility Matrix.

v4.0.0-rc3

Release Notes

Release Procedure is defined in the CONTRIBUTING document.

v4.0.0-rc3

v4.0.0-rc3 is the third release candidate for the historical upgrade.

v4.0.0-rc2

Release Notes

Release Procedure is defined in the CONTRIBUTING document.

v4.0.0-rc2

This is the second release candidate for our v4.0.0 release.
This release focuses on historacle pricing, and will be deployed on the canon-2 testnet.

v4.0.0-rc1

Release Notes

Release Procedure is defined in the CONTRIBUTING document.

v4.0.0-rc1

This is the first release candidate for our v4.0.0 release.
This release focuses on historacle pricing, and will be deployed on the canon-2 testnet.

price-feeder/v2.0.3-rc1

Changelog

v2.0.3-rc1

This is the first release candidate for price feeder v2.0.3.

The main change in this version of the price feeder is to be compatible with the umeed v4.0.0 binary. Please see the Release Compatibility Matrix.

v3.3.0

Release Notes

Release Procedure is defined in the CONTRIBUTING document.

v3.3.0

• For the mainnet, this release includes update from v3.1.x → v3.3.x. Please also look at the v3.2 Release Notes, notably the Gravity Bridge Slashing.
• For the Canon-2 testnet, this release includes update from v3.2.x → v3.3.x

v3.2.0 was not released on mainnet due to a bug in x/leverage gov messages migration to the new format which utilizes x/gov/v1 authorization system. The bug caused legacy token registry updates to break x/gov proposal queries. In v3.3 we fix that bug.

Additional highlights:

• Added QueryMaxWithdraw and MsgMaxWithdraw to allow user easily withdraw previously supplied tokens from the module back to the user balance.
• Updated Cosmos SDK to v0.46.7

Please see the CHANGELOG for an exhaustive list of changes.

Github Release

Sinice v3.2.0 new experimental features (disabled by default) are part of the linked binary. That changed the build process. Umeed officially doesn't support static CGO build (with CGO_ENABLED=1) any more. Github Actions only support build using Linux on amd64 -- we can not make a cross platform build using Github Actions (possible solution is to do it through Qemu emulator). So our Github release only contains source code archive and amd64 Linux binary.

To run the provided binary, you have to have libwasmvm.x86_64.so v1.1.1 in your system lib directory.

Building from source will automatically link the libwasmvm.x86_64.so created as a part of the build process (you must build on the same host as you run the binary, or copy the libwasmvm.x86_64.so your lib directory).

If you build on system different than Linux amd64, then you need to download appropriate version of libwasmvm (eg from CosmWasm/wasmvm Relases) or build it from source (you will need Rust toolchain).

Otherwise you have to download libwasmvm. Please check Supported Platforms. Example:

wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.1.1/internal/api/libwasmvm.$(uname -m).so -P /lib/

Update instructions

• Note: Skip this step if you build binary from source and are able to properly link libwasmvm.
  • Download libwasmvm:

$ wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.1.1/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Run latest Peggo (v1.4.0) - updated (you should update as soon as you can, it's compatible with the existing chain version).
• Run latest Price Feeder (v2.0.2) - updated (you should update as soon as you can, it's compatible with the existing chain version).
• Swap binaries.
• Restart the chain.

There is a new option available in app.toml (in Base Configuration). Set iavl-disable-fastnode to true if you want to disable fastnode cache and reduce RAM usage (default is false).

# IAVLDisableFastNode enables or disables the fast node feature of IAVL.
# Default is false.
iavl-disable-fastnode = false

You can use Cosmovisor → see instructions.

• If you use Cosmovisor, and you didn't build binary from source in the validator machine, you have to download the respective libwasmvm into your machine. See the previous section for more details.

NOTE: BEFORE the upgrade, make sure the binary is working and libwasmvm is in your system. You can test it by running ./umeed-v3.3.0 --version.

Docker

Docker images: https://github.com/umee-network/umee/pkgs/container/umeed

v3.3.0-rc3

Release Notes

Please see the CHANGELOG for an exhaustive list of changes.

Gravity Bridge

This is the final step for enabling Gravity Bridge. We enable slashing.
Validators must run Peggo and must process claims to not be slashed.

Github Release

New experimental features which are part of the linked binary changed the build process. Umeed doesn't support static CGO build (with CGO_ENABLED=1). Github Actions only support build using Linux on amd64, we can not make a cross platform build using Github Actions. So our Github release only contains source code archive and amd64 Linux binary.

Moreover to run the provided binary, you need to have libwasmvm.x86_64.so v1.1.1 in your system lib directory.

Building from source will automatically link the libwasmvm.x86_64.so created as a part of the build process (you must build on same host as you run the binary, or copy the libwasmvm.x86_64.so your lib directory).

Please check Supported Platforms for libwasmvm

Update instructions

• Note: Skip this step if you build binary from source
  • Download libwasmvm

$ wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.1.1/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

• Wait for software upgrade proposal to pass and trigger the chain upgrade.
• Run latest Peggo (v1.3.0) - updated
• Run latest Price Feeder (v2.0.0) - updated
• Swap binaries.
• Restart the chain.

You can use Cosmovisor → see instructions.

• If you use Cosmovisor, and you didn't build binary from source in the validator machine, you have to download the respective libwasmvm into your machine.

$ wget https://raw.githubusercontent.com/CosmWasm/wasmvm/v1.1.1/internal/api/libwasmvm.$(uname -m).so -O /lib/libwasmvm.$(uname -m).so

NOTE: As described in the previous section, you need to have libwasmvm.x86_64.so correctly linked to the binary. BEFORE the upgrade, make sure the binary is working. You can test it by running ./umeed-v3.2.0 --version.

price-feeder/v2.0.2

Changelog

89959cc fix: price-feeder module version (#1660) (#1661)
6cc62f2 docs: update price-feeder changelog for v2.0.1 (#1636) (#1643)

v3.3.0-rc1

Release Notes

Release Procedure is defined in the CONTRIBUTING document.

What's Changed

• build(deps): Bump github.com/umee-network/umee/v3 from 3.1.0 to 3.2.0 in /price-feeder by @dependabot in #1623
• build(deps): Bump cosmossdk.io/math from 1.0.0-beta.3 to 1.0.0-beta.4 by @dependabot in #1622
• docs: historic spec updates by @adamewozniak in #1624
• chore: update the instuction for running v3.2.0 with cosmwasm by @gsk967 in #1629
• fix(price-feeder): handle missing rates properly by @adamewozniak in #1635
• fix(price-feeder): add minimum candle volume by @adamewozniak in #1634
• chore: price-feeder config update by @adamewozniak in #1625
• build(deps): Bump github.com/cosmos/cosmos-proto from 1.0.0-alpha8 to 1.0.0-beta.1 by @dependabot in #1641
• fix: increase price calc precision for high exponent assets by @toteki in #1633
• docs: update price-feeder changelog for v2.0.1 by @adamewozniak in #1636
• feat: add QueryMaxWithdraw and MsgWithdrawMax by @toteki in #1642
• docs: update canon-2 instructions by @robert-zaremba in #1626
• fix: leverage gov proposal migrations by @robert-zaremba in #1640
• docs: update historacle API and computation docs by @robert-zaremba in #1631
• chore: remove duplicate code in tests of leverage module by @gsk967 in #1644

Full Changelog: v3.2.0...v3.3.0-rc1