insumity

CCV's VSCMaturedPacket: What are the trust assumptions?

1

### Problem Clarify the trust assumptions we currently make for CCV. For example, can we trust the consumer chain when it provides the height of when a `VSCPacket` was applied,...

test: add E2E test for power-shaping features

1

## Description Added some _simple_ E2E tests to verify that the basic behavior of the power-shaping features works as expected. Specifically, we test that validator-set capping, validators-power capping, allowlisting, and...

Partial Set Security: Write documentation

1

Before PSS launches we need to: - [ ] provide a feature overview - [ ] provide validator documentation (joining, opting in etc) - [ ] provide query and transaction...

feat: add a query to retrieve validator set that was last sent to the consumer chain

1

## Description Closes: #XXXX This PR introduces a query to retrieve the validator set that was last sent to the consumer chain. **Note** that this does not necessarily mean that...

## Description Closes: #XXXX **Makes more sense to look at this PR by commit.** --- ### Author Checklist *All items are required. Please add a note to the item if...

## Problem This is a meta issue to track the work of [Permissinoless ICS](https://github.com/cosmos/interchain-security/blob/main/docs/docs/adrs/adr-018-permissionless-ics.md). Permissionless ICS allows _Opt In_ consumer chains to join ICS by simply issuing transactions, without having...

Clean up slash-log state

2

## Problem The `provider` module still stores state under `SlashLogBytePrefix`.`SlashLogBytePrefix` is used to construct the `SlashLogKey` that is used in `SetSlashLog` and `GetSlashLog` methods. `SetSlashLog` is used [here](https://github.com/cosmos/interchain-security/blob/main/x/ccv/provider/keeper/relay.go#L334) while `GetSlashLog`...

Allocate tokens before stopping a consumer chain

2

## Problem Currently if a consumer chain is stopped/removed, the rewards sent to this consumer chain might not be given to the consumer validators. This is because the reward distribution...

Provider's GenesisState consumer chains

1

## Problem Currently the [consumer states](https://github.com/cosmos/interchain-security/blob/v5.1.0/proto/interchain_security/ccv/provider/v1/genesis.proto#L56) of consumer chains included in the provider's `GenesisState` do not contain anything in relation to Partial Set Security (PSS). This seems problematic and probably...

## Problem As mentioned in this [comment](https://github.com/cosmos/interchain-security/pull/2079#discussion_r1689314023), power shaping parameters appear in multiple proto messages (e.g., in [`MsgConsumerAddition`](https://github.com/cosmos/interchain-security/blob/v5.1.0/proto/interchain_security/ccv/provider/v1/tx.proto#L169), [`MsgConsumerModification`](https://github.com/cosmos/interchain-security/blob/v5.1.0/proto/interchain_security/ccv/provider/v1/tx.proto#L305), [`ConsumerAdditionProposal`](https://github.com/cosmos/interchain-security/blob/v5.1.0/proto/interchain_security/ccv/provider/v1/provider.proto#L94)). It would be nice to get rid of those duplications...