Releases: Kava-Labs/kava
Gateway Release
This is the first major version for the kava-4 'Gateway' release.
Migration
This release is intended to be the canonical software version for the kava-4
mainnet upgrade. See the migration guide for full details.
Release notes
Harvest
- The
x/harvest
module introduces version 1 of cross-chain money market functionality to kava
BEP3
- Support for multiple assets was added. At launch, kava-4 will support BNB, BTC-b, XRP-b, and BUSD
- The bep-3 deputy account on kava no longer holds any coins - this improves the security of the assets pegged with bep3.
CDP
- Support for additional collateral types was added. At launch, kava-4 will support BNB, BTC-b, XRP-b, and BUSD
Dependencies
- Update
cosmos-sdk
to v0.39.1- Note that the pruning issue that affected v0.38.x has been resolved. Node operators can run using any of
pruning="default"
,pruning="nothing"
,pruning="everything"
, or a custom pruning strategy. Pruning options are managed in.kvd/config/app.toml
- Note that the pruning issue that affected v0.38.x has been resolved. Node operators can run using any of
- Bump
tendermint
to v0.33.7
Gateway Release Candidate 2
This is the second release candidate for the kava-4 'Gateway' release
Release notes
Harvest
The x/harvest
module introduces version 1 of cross-chain money market functionality to kava
BEP3
- Support for multiple assets was added. At launch, kava-4 will support BNB, BTC-b, XRP-b, and BUSD
- The bep-3 deputy account on kava no longer holds any coins - this improves the security of the assets pegged with bep3.
CDP
- Support for additional collateral types was added. At launch, kava-4 will support BNB, BTC-b, XRP-b, and BUSD
Gateway Release Candidate 1
This is the first release candidate for the kava-4 'Gateway' release
Release notes
Harvest
The x/harvest
module introduces version 1 of cross-chain money market functionality to kava
BEP3
- Support for multiple assets was added. At launch, kava-4 will support BNB, BTC-b, XRP-b, and BUSD
- The bep-3 deputy account on kava no longer holds any coins - this improves the security of the assets pegged with bep3.
CDP
- Support for additional collateral types was added. At launch, kava-4 will support BNB, BTC-b, XRP-b, and BUSD
Gateway Alpha 2
This alpha release includes the new harvest
module, which lays the foundation for cross-chain money markets on Kava. Use this version of the software for kava-testnet-10000
Note: This is an alpha release and is not compatible with the current 'kava-3' mainnet. Expect breaking changes and the potential for bugs.
Gateway Alpha 1
This minor release fixes a bug in the committee
module where the committee parameters did not reflect the updated parameters of the cdp
module. Use this version of the software for kava-testnet-9000.
Gateway Alpha 0
This is the first alpha release targeting the features expected to become a part of the kava-4 'Gateway' release'. The main features introduced include:
- Support for multiple bep3 assets
- Support for assets controlled by a single issuer
- CDP module upgrades to better support multiple collaterals
- CDP support for one collateral to have multiple CDP types
Note: This is an alpha release and is not compatible with the current 'kava-3' mainnet. Expect breaking changes and the potential for bugs.
[HOTFIX] Patch application panic
Mainnet patch - Critical
Patches an issue where rewards for denominations not initialized at genesis cause an application panic in the begin blocker.
This patch can safely be deployed with the existing database, do not reset your node or delete any data.
Diff: v0.9.1...v0.10.0
Update instructions
# from kava directory
git fetch origin
git checkout v0.10.0
make install
# restart kvd process
v0.9.1
Bump tendermint version to address tendermint security advisory syringa
Bep3 Patch Release
Kava Testnet 7000 Release Candidate
This release candidate patches an issue with v0.8.1
that prevented adjusting the asset supply limit for bep3 assets. This release candidate is intended to run on kava testnet 7000 to verify the bugfix. Note that for this release candidate, the bugfix takes effect on July 2nd, 2020 at 14:00 UTC. A different date will be used for the official release, and this release should not be run on mainnet.