September 20, 2024
- Remove duplicate event emission on cached context. (#2282)
[x/provider]
Add patch to enable ICS rewards from Stride to be distributed. (#2288)
[x/provider]
Add patch to enable ICS rewards from Stride to be distributed. (#2288)
September 12, 2024
-
[x/provider]
Add the Permissionless ICS feature on the provider (as per ADR-019), which entails the following api-breaking changes on the provider. (#2171)-
Deprecate the
chain-id
parameter in favour ofconsumer-id
for all transactions and queries targeting a unique consumer chain. Below is a list highlighting the changes in the CLI commands. All commands assume the prefixinterchain-security-pd tx|q provider
.-
Transactions:
assign-consensus-key [consumer-id] [consumer-pubkey]
-- submit a MsgAssignConsensusKeyopt-in [consumer-id] [consumer-pubkey]
-- submit a MsgOptInopt-out [consumer-id]
-- submit a MsgOptOutset-consumer-commission-rate [consumer-id] [commission-rate]
-- submit a MsgSetConsumerCommissionRate
-
Queries:
-
consumer-genesis [consumer-id]
-- query for consumer chain genesis state by consumer id.- REST:
/interchain_security/ccv/provider/consumer_genesis/{consumer_id}
- REST:
-
validator-consumer-key [consumer-id] [provider-validator-address]
-- query assigned validator consensus public key for a consumer chain.- REST:
/interchain_security/ccv/provider/validator_consumer_addr/{consumer_id}/{provider_address}
- REST:
-
validator-provider-key [consumer-id] [consumer-validator-address]
-- query assigned validator consensus public key for the provider chain.- REST:
/interchain_security/ccv/provider/validator_provider_addr/{consumer_id}/{consumer_address}
- REST:
-
consumer-opted-in-validators [consumer-id]
-- query opted-in validators for a given consumer chain.- REST:
/interchain_security/ccv/provider/opted_in_validators/{consumer_id}
- REST:
-
consumer-validators [consumer-id]
-- query the last set consumer-validator set for a given consumer chain.- REST:
/interchain_security/ccv/provider/consumer_validators/{consumer_id}
- REST:
-
validator-consumer-commission-rate [consumer-id]
-- query the consumer commission rate a validator charges on a consumer chain.- REST:
/interchain_security/ccv/provider/consumer_commission_rate/{consumer_id}/{provider_address}
- REST:
-
all-pairs-valconsensus-address [consumer-id]
-- query all pairs of valconsensus address by consumer id.- REST:
/interchain_security/ccv/provider/address_pairs/{consumer_id}
- REST:
-
-
-
Deprecate the following queries, proposals and all legacy governance proposals:
-
Queries:
-
list-start-proposals
-- query consumer chains start proposals on provider chain.- REST:
/interchain_security/ccv/provider/consumer_chain_start_proposals
- REST:
-
list-stop-proposals
-- consumer chains stop proposals on provider chain.- REST:
/interchain_security/ccv/provider/consumer_chain_stop_proposals
- REST:
-
list-proposed-consumer-chains
-- query chain ids in consumer addition proposal before voting finishes.- REST:
/interchain_security/ccv/provider/proposed_consumer_chains
- REST:
-
-
Proposals:
- MsgConsumerAddition -- deprecated in favor of MsgCreateConsumer
- MsgConsumerRemoval -- deprecated in favor of MsgRemoveConsumer
- MsgConsumerModification -- deprecated in favor of MsgUpdateConsumer
-
Legacy Proposals:
-
-
-
[x/provider]
Add the Inactive Provider Validators feature (as per ADR-017), which entails the following changes on the provider. (#2079)- Add
max_provider_consensus_validators
, a provider module param that sets the maximum number of validators that will be passed to the provider consensus engine. - Add
no_valupdates_genutil
andno_valupdates_staking
, "wrapper" modules around the Cosmos SDK's native genutil and staking modules. Both modules provide the exact same functionality as the native modules, except for not returning validator set updates to the provider consensus engine. - Return the first
max_provider_consensus_validators
validators (sorted by largest amount of stake first) to the provider consensus engine. - Use the
max_validators
validators as basis for the validator sets sent to the consumers (max_validators
is a staking module param).
- Add
-
[x/provider]
The removal ofVSCMaturedPackets
entail several API breaking changes. (#2098)- Remove the
oldest_unconfirmed_vsc
query -- used to get the send timestamp of the oldest unconfirmed VSCPacket. - Deprecate the
init_timeout_period
andvsc_timeout_period
parameters from the provider module.
- Remove the
- Bump CometBFT to v0.38.11. (#2200)
- Bump cosmos-sdk to v0.50.9 (#2200)
- Bump ibc-go to v8.5.0. (#2200)
-
[x/provider]
Addallow_inactive_vals
, a power shaping configuration parameter that enables consumers to specify whether validators outside the active provider validator set are eligible to opt-in. (#2066) -
[x/provider]
Addmin_stake
, a power shaping configuration parameter that enables consumers to set the minimum amount of provider stake every validator needs to be eligible to opt-in. (#2035) -
[x/provider]
Add a query to get the blocks until the next epoch begins (#2106) -
[x/provider]
Add the Inactive Provider Validators feature (as per ADR-017), which entails the following changes on the provider. (#2079)- Add
max_provider_consensus_validators
, a provider module param that sets the maximum number of validators that will be passed to the provider consensus engine. - Add
no_valupdates_genutil
andno_valupdates_staking
, "wrapper" modules around the Cosmos SDK's native genutil and staking modules. Both modules provide the exact same functionality as the native modules, except for not returning validator set updates to the provider consensus engine. - Return the first
max_provider_consensus_validators
validators (sorted by largest amount of stake first) to the provider consensus engine. - Use the
max_validators
validators as basis for the validator sets sent to the consumers (max_validators
is a staking module param).
- Add
-
[x/provider]
Add the Permissionless ICS feature (as per ADR-019), which entails the following CLI and API enhancements on the provider. (#2171)-
Introduce new CLI commands and gRPC endpoints to manage consumer chains. All commands listed below assume the prefix
interchain-security-pd tx|q provider
.-
Transactions:
-
create-consumer [consumer-parameters]
-- submit a MsgCreateConsumer -- replace ConsumerAdditionProposal -
update-consumer [consumer-parameters]
-- submit a MsgUpdateConsumer -- replace ConsumerModificationProposal -
remove-consumer [consumer-id]
-- submit a MsgRemoveConsumer -- replace ConsumerRemovalProposal
These new TX commands should be used instead of their corresponding deprecated proposals. To update consumer chains owned by the governance module, a proposal containing a
MsgUpdateConsumer
message must be submitted. -
-
Queries:
consumer-chain [consumer-id]
-- query details of a consumer chain associated with the consumer id.- REST:
interchain-security/ccv/provider/consumer_chain/{consumer_id}
- REST:
consumer-id-from-client-id [client-id]
-- get the consumer id of a chain from a client id.- REST:
interchain-security/ccv/provider/consumer_id/{client_id}
- REST:
blocks-until-next-epoch
-- query number of blocks remaining until the next epoch begins.- REST:
interchain-security/ccv/provider/blocks_until_next_epoch
- REST:
-
-
Improve the
list-consumer-chains
query to accept optional parameters[phase]
and[limit]
:[phase]
: Filters returned consumer chains by their phase.[limit]
: Limits the number of consumer chains returned.
-
-
[x/provider]
RemoveVSCMaturedPackets
from the provider module, which entails the following changes to the provider. (#2098)- Remove unbonding operations pausing.
- Remove the CCV channel initialization timeout.
- Remove
VSCPackets
timeout. - Redesign key assignment pruning -- prune old consumer keys after the unbonding period elapses.
-
[x/provider]
Remove provider migrations to consensus versions lower than 7. To migrate the provider module from consensus version 3, 4, or 5 to consensus version 7 or higher, users should use v4.3.x in production to migrate to consensus version 6. (#2211)
[x/provider]
Addallow_inactive_vals
, a power shaping configuration parameter that enables consumers to specify whether validators outside the active provider validator set are eligible to opt-in. (#2066)[x/provider]
Addmin_stake
, a power shaping configuration parameter that enables consumers to set the minimum amount of provider stake every validator needs to be eligible to opt-in. (#2035)[x/provider]
Add the Inactive Provider Validators feature (as per ADR-017). (#2079)[x/provider]
Add the Permissionless ICS feature (as per ADR-019). (#2171)[x/provider]
RemoveVSCMaturedPackets
from the provider module (as per ADR-018). (#2098)