Skip to content

Latest commit

 

History

History
80 lines (63 loc) · 7.53 KB

CHANGELOG.md

File metadata and controls

80 lines (63 loc) · 7.53 KB
Raw

CHANGELOG

v.2.0.0

Date: June 1st, 2023

Unlike prior releases, the ICS v2.0.0 release will be based on the main branch. v2.0.0 will contain all the accumulated PRs from the various releases below, along with other PRs that were merged, but not released to production. After v2.0.0, we plan to revamp release practices, and how we modularize the repo for consumer/provider.

Upgrading a provider from v1.1.0-multiden to v2.0.0 will require state migrations. See migration.go. See the provider module's ConsensusVersion in module

Upgrading a consumer from v1.2.0-multiden to v2.0.0 will NOT require state migrations. See the consumer module's ConsensusVersion in module

High level changes included in v2.0.0

  • MVP for standalone to consumer changeover, see EPIC
  • MVP for soft opt out, see EPIC
  • Various fixes, critical and non-critical
  • Docs updates which should not affect production code

Notable PRs included in v2.0.0

  • (feat!) Add DistributionTransmissionChannel to ConsumerAdditionProposal #965
  • (feat/fix) limit vsc matured packets handled per endblocker #1004
  • (fix) cosumer key prefix order to avoid complex migrations #963 and #991. The latter PR is the proper fix.
  • (feat) v1->v2 migrations to accommodate a bugfix having to do with store keys, introduce new params, and deal with consumer genesis state schema changes #975 and #997
  • (deps) Bump github.com/cosmos/ibc-go/v4 from 4.4.0 to 4.4.2 #982
  • (fix) partially revert key assignment type safety PR #980
  • (fix) Remove panics on failure to send IBC packets #876
  • (fix) Prevent denom DOS #931
  • (fix) multisig for assigning consumer key, use json #916
  • (deps) Bump github.com/cosmos/ibc-go/v4 from 4.3.0 to 4.4.0 #902
  • (feat) Add warnings when provider unbonding is shorter than consumer unbonding #858
  • (chore) use go 1.19 #899, #840
  • (feat) Standalone to consumer changeover - recycle existing transfer channel #832
  • (deps) Bump IBC 862
  • (testing) Add tests for soft opt out #857
  • (feat) Standalone to consumer changeover - staking functionalities #794
  • (fix) prevent provider from sending VSCPackets with multiple updates for the same validator #850
  • (feat) Soft opt out #833
  • (fix) Correctly handle VSC packet with duplicate val updates on consumer #846
  • (deps) bump sdk to v0.45.15.ics #805
  • (refactor) Remove spm module #812
  • (feat) Standalone to consumer changeover part 1 #757
  • (chore) Swap names of e2e and integration tests #681
  • (fix) fix StopConsumerChain not running in cachedContext #802. Also in earlier releases with different commit order!
  • (docs) Introduce docs website #759
  • (fix) Serialize correct byte prefix for SlashLogKey #786
  • (feature) Improve keeper field validation #766
  • (docs) Contributing guidelines #744
  • (refactor) Key assignment type safety #725
  • (fix) Update protos and fix deps #752
  • (api) Add consumer QueryParams #746
  • (feature) New validation for keeper fields #740

v1.0.0

Date: February 6th, 2023

This is the first version of Interchain Security (ICS), also known as Replicated Security (RS). Replicated Security is a feature which will allow a chain -- referred to as the provider -- to share security with other chains -- referred to as consumers. This means that the provider's validator set will be granted the right to validate consumer chains. The communication between the provider and the consumer chains is done through the IBC protocol over a unique, ordered channel (one for each consumer chain). Thus, RS is an IBC application.

Features / sub-protocols

RS consist of the following core features:

  • Channel Initialization: Enables the provider to add new consumer chains. This process is governance-gated, i.e., to add a new consumer chain, a ConsumerAdditionProposal governance proposal must be sent to the provider and it must receive the necessary votes.
  • Validator Set Update: Enables the provider to (1) update the consumers on the voting power granted to validators (based on the changes in the active validator set on the provider chain), and (2) ensure the timely completion of unbonding operations (e.g., undelegations).
  • Consumer Initiated Slashing: Enables the provider to jail validators for downtime infractions on the consumer chains.
  • Reward Distribution: Enables the consumers to transfer to the provider (over IBC) a portion of their block rewards as payment for the security provided. Once transferred, these rewards are distributed on the provider using the protocol in the distribution module of Cosmos SDK.
  • Consumer Chain Removal: Enables the provider to remove a consumer either after a ConsumerRemovalProposal passes governance or after one of the timeout periods elapses -- InitTimeoutPeriod, VscTimeoutPeriod, IBCTimeoutPeriod.
  • Social Slashing: Equivocation offenses (double signing etc.) on consumer chains are logged, and then can be used in a governance proposal to slash the validators responsible.

In addition, RS has the following features:

  • Key Assignment: Enables validator operators to use different consensus keys for each consumer chain validator node that they operate.
  • Jail Throttling: Enables the provider to slow down a "worst case scenario" attack where a malicious consumer binary attempts to jail a significant amount (> 2/3) of the voting power, effectively taking control of the provider.