0g-chain/CHANGELOG.md
Nick DeLuca a68ef74b07
Query old blocks for proposals in CLI (#598)
* move file to query.go (we are adding functionality so specific name
doesn't fit anymore)

* Add tx search for proposals in cli query proposal

* add rest support, height support for rest api, and add go doc string

* add in deadline calculation

* update changelog

Co-authored-by: Kevin Davis <kjydavis3@gmail.com>
2020-06-29 19:39:35 -04:00

5.8 KiB

Changelog

[Unreleased]

#591 Add a raw-params cli method to query raw parameter values for use in manual verification of gov proposals.

#596 Add REST client and CLI query to get module account information for the CDP module

#590 Add CLI query to return kavadist module account balance

#584 Add REST client and CLI queries for kavadist module

#578 Add v0.3 compatible REST client that supports

/v0_3/node_info
/v0_3/auth/accounts/<address>
/v0_3/<hash>
/v0_3/txs
/v0_3/staking/delegators/<address>/delegations
/v0_3/staking/delegators/<address>/unbonding_delegations
/v0_3/distribution/delegators/<address>/rewards

#598 CLI and REST queries for committee proposals (ie kvcli q committee proposal 1) now query the historical state to return the proposal object before it was deleted from state

v0.8.1 kava-3 Patch Release

This version mitigates a memory leak in tendermint that was found prior to launching kava-3. It is fully compatible with v0.8.0 and is intended to replace that version as the canonical software version for upgrading the Kava mainnet from kava-2 to kava-3. Note that there are no breaking changes between the versions, but a safety check was added to this version to prevent starting the node with an unsafe configuration.

Bugfix

The default tendermint pruning strategy, pruning="syncable" is currently unsafe due to a memory leak that can cause irrecoverable data loss. This patch release prevents kvd from being started with the pruning="syncable" configuration. Until a patch for tendermint is released, the ONLY pruning strategies that are safe to run are everything (an archival node) or nothing (only the most recent state is kept). It is strongly recommended that validators use pruning="nothing" for kava-3. It is expected that a patch to tendermint will be released in a non-breaking manner and that nodes will be able to update seamlessly after the launch of kava-3.

The steps for upgrading to kava-3 can be found here. Please note the additional section on pruning.

v0.8.0 kava-3 Release

This version is intended to be the canonical software version for upgrading the Kava mainnet from kava-2 to kava-3. As a result, no subsequent versions of Kava will be released until kava-3 launches unless necessary due to critical state-machine faults that require a new version to launch successfully.

Migration

The steps for upgrading to kava-3 can be found here

Features

This is the first release that includes all the modules which comprise the CDP system.

State Machine Breaking Changes

(sdk) Update Cosmos-SDK version to v0.38.4. To review cosmos-sdk changes, see the changelog.

v0.3.5

Bump tendermint version to 0.32.10 to address cosmos security advisory Lavender

v0.3.2

#364 Use new BIP44 coin type in the CLI, retain support for the old one through a flag.

v0.3.1

#266 Bump tendermint version to 0.32.7 to address cosmos security advisory Periwinkle

v0.3.0

Features

#253 Add a new validator vesting account type, which releases coins on a periodic vesting schedule based on if a specific validator signed sufficient pre-commits. If the validator didn't sign enough pre-commits, the vesting coins are burned or sent to a return address.

#260 Pin to cosmos-sdk commit #18de630 (tendermint 0.32.6)

Improvements

#257 Include scripts to run large-scale simulations remotely using aws-batch