|
| 1 | +--- |
| 2 | +title: v15.1.0 |
| 3 | +order: 1 |
| 4 | +--- |
| 5 | + |
| 6 | +This document outlines API breaking changes that were introduced in `gaia v15.1.0`. |
| 7 | + |
| 8 | +This release is based on cosmos-sdk `v0.47.x` and ibc-go `v7.x`. |
| 9 | + |
| 10 | +You can find the comprehensive API docs at: |
| 11 | +* https://docs.cosmos.network/api |
| 12 | + |
| 13 | +Module reference manuals (with CLI instructions) can be found at: |
| 14 | +* https://docs.cosmos.network/v0.47/build/modules |
| 15 | + |
| 16 | +Comprehensive list of changes: |
| 17 | +* https://github.com/cosmos/gaia/blob/release/v15.1.x/CHANGELOG.md#api-breaking |
| 18 | + |
| 19 | +## Supported modules: |
| 20 | +cosmos-sdk `v0.47.10-ics-lsm` |
| 21 | +* x/auth |
| 22 | +* x/authz |
| 23 | +* x/bank |
| 24 | +* x/capability |
| 25 | +* x/consensus |
| 26 | +* x/crisis |
| 27 | +* x/distribution |
| 28 | +* x/evidence |
| 29 | +* x/feegrant |
| 30 | +* x/gov |
| 31 | +* x/mint |
| 32 | +* x/params |
| 33 | +* x/slashing |
| 34 | +* x/staking (with LSM changes) |
| 35 | +* x/upgrade |
| 36 | + |
| 37 | +ibc-go `v7.x` |
| 38 | +* transfer |
| 39 | +* ica (host) |
| 40 | + |
| 41 | +interchain-security/provider `v3.3.x` |
| 42 | + |
| 43 | +packetforward `v7.x` |
| 44 | + |
| 45 | +gaia |
| 46 | +* x/globalfee `v15.x` |
| 47 | +* x/metaprotocols `v15.x` |
| 48 | + |
| 49 | + |
| 50 | +# Important changes |
| 51 | +Changes are outlined compared to `gaiad <= v14.x` |
| 52 | + |
| 53 | +## Behaviour changes |
| 54 | + |
| 55 | +Starting `v15.1.0` all users must have at least `1 ATOM` staked in order to cast a vote on a governance proposal. |
| 56 | + |
| 57 | +Votes from accounts whose staked amounts are `< 1 ATOM` will be rejected. |
| 58 | + |
| 59 | +## REST/RPC Changes |
| 60 | + |
| 61 | +### DenomOwners |
| 62 | + |
| 63 | +The `DenomOwners` query is not supported on the Cosmos Hub chain. |
| 64 | +* querying `<RPC_ADDR>.cosmos/bank/v1beta1/denom_owners/{denom}` always returns an empty result. |
| 65 | + |
| 66 | + |
| 67 | +### Querying latest block |
| 68 | + |
| 69 | +`curl <RPC>/blocks/latest` no longer works and returns `{"code":12,"message":"Not Implemented","details":[]}` |
| 70 | + |
| 71 | +The endpoint was moved to: `<RPC>/cosmos/base/tendermint/v1beta1/blocks/latest` |
| 72 | + |
| 73 | + |
| 74 | +# CLI Changes |
| 75 | + |
| 76 | +## Genesis commands |
| 77 | + |
| 78 | +`gaiad` no longer uses a custom genesis commands and instead relies on the commands defined in the [x/genutil module](https://docs.cosmos.network/v0.47/build/modules/genutil). |
| 79 | + |
| 80 | +These queries no longer work: |
| 81 | +```shell |
| 82 | +gaiad gentx |
| 83 | +gaiad collect-gentx |
| 84 | +gaiad validate-genesis |
| 85 | +gaiad add-genesis-account |
| 86 | +``` |
| 87 | + |
| 88 | +Use the `genesis` subcommands instead: |
| 89 | +```shell |
| 90 | +gaiad genesis gentx |
| 91 | +gaiad genesis collect-gentx |
| 92 | +gaiad genesis validate-genesis |
| 93 | +gaiad genesis add-genesis-account |
| 94 | +gaiad genesis migrate |
| 95 | +``` |
| 96 | + |
| 97 | +## Governance commands |
| 98 | + |
| 99 | +Governance commands are aligned with cosmos-sdk v0.47.x [x/gov module](https://docs.cosmos.network/v0.47/build/modules/gov). |
| 100 | + |
| 101 | +### submit-legacy-proposal |
| 102 | + |
| 103 | +Some proposal types can be submitted using the `gaiad tx gov submit-legacy-proposal` command: |
| 104 | +```sh |
| 105 | +gaiad tx gov submit-legacy-proposal |
| 106 | + |
| 107 | +Available Commands: |
| 108 | + cancel-software-upgrade Cancel the current software upgrade proposal |
| 109 | + change-reward-denoms Submit a change reward denoms proposal |
| 110 | + consumer-addition Submit a consumer addition proposal |
| 111 | + consumer-removal Submit a consumer chain removal proposal |
| 112 | + ibc-upgrade Submit an IBC upgrade proposal |
| 113 | + param-change Submit a parameter change proposal |
| 114 | + software-upgrade Submit a software upgrade proposal |
| 115 | + update-client Submit an update IBC client proposal |
| 116 | +``` |
| 117 | + |
| 118 | +Most cosmos-sdk modules no longer allow their parameters to be upgraded using a `param-change` proposal. Use the corresponding `MsgUpgradeParams` message instead and create a JSON file proposal using `draft-proposal` (listed below). |
| 119 | + |
| 120 | +List of proposals available for submission via `submit-legacy-proposal` will be further decreased in subsequent releases. |
| 121 | + |
| 122 | +More information is available in cosmos-sdk [x/gov docs](https://docs.cosmos.network/v0.47/build/modules/gov#submit-legacy-proposal). |
| 123 | + |
| 124 | +### draft-proposal |
| 125 | + |
| 126 | +`gaiad tx gov draft-proposal` command is available. You can use this command to create a draft proposal in JSON format. |
| 127 | +* more information is available in the cosmos-sdk [x/gov docs](https://docs.cosmos.network/v0.47/build/modules/gov#draft-proposal) |
| 128 | + |
| 129 | +### submit-proposal |
| 130 | + |
| 131 | +`gaiad tx gov submit-proposal` command is available. Use `draft-proposal` (listed above) to create a proposal JSON and submit it as a transaction. |
| 132 | + |
| 133 | +More information is available in cosmos-sdk [x/gov docs](https://docs.cosmos.network/v0.47/build/modules/gov#submit-proposal) |
0 commit comments