Kava-Labs/kava v0.25.0

Kava 15 Release (v0.25.0)

on GitHub

For deployment to Kava Mainnet at height 7637070 around 2023-12-07 15:00:00 UTC.

Click to view upgrade instructions.

This release adds improvements to the x/community module and param changes, along with prerequisite handlers for consolidating community pool funds, disabling inflation, and adjusting staking rewards at a future date.

For a complete list of changes, including client breaking changes, see CHANGELOG.md.

Please note that if you run your node with rocksdb as the database, this update will require an update to v8 of rocksdb. Recommended rocksdb verison: v8.1.1

Upgrade Changes

These changes occur on the mainnet upgrade height 7637070.

x/community

• New API endpoint for staking reward calculation. This has also been backported to v0.24.1 to ease transition, details can be found here.

x/staking

• The minimum validator commission rate set to 5% for all existing and new validators to align with proposal #128.

x/gov

• New x/authz grant for management of x/kavadist funds via gov proposals.
• Tally quorum set to 20%, requiring less votes for proposals to be considered for acceptance/denial.

x/incentive

• Rewards for bkava Earn deposits updated from 5,000,000 KAVA to 600,000 KAVA per year.

Switchover Changes

These changes do not take effect on upgrade height, but instead are automatically applied on the first block after the "Switchover Time" listed below. No additional binary changes or upgrade is necessary to support these changes, as these timed upgrades are included in this version.

Inflation & Staking Rewards

Inflation will be disabled in x/mint and x/kavadist. This means the total supply of KAVA will be fixed after the switchover time. Staking rewards will be paid from a fixed per second rate from community pool funds, calculated from the annualized staking rewards listed in the table above.

x/distribution community tax will be reduced to 0%.

Community Funds

Prior to switchover, community funds are stored in the x/distribution community pool, x/community account, and x/kavadist account. All community funds will be consolidated to be contained in the x/community module account.

For additional technical details, see the x/community spec.