v4.0.0

Replicated Security v4.0.0 Release Notes

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

Refer to the upgrading guide when migrating from a version >= v3.1.x to v4.0.x.

❗ We recommend consumer chains to upgrade to this version of ICS as soon as possible.

🚀 Highlights

This release introduces the following noteworthy changes:

• It sets the minimum required version of Go to 1.21.
• It adds the provider-side changes for jail throttling with retries and, as a result, it fully enables the jail throttling with retries feature (cf. ADR 008).
• Fixes a bug in the soft opt-out protocol -- it avoids jailing validators immediately once they can no longer opt-out from validating consumer chains.
• Fixes a bug the validation of VSCPackets caused by marshaling to string using Bech32.

v3.3.0

Replicated Security v3.3.0 Release Notes

❗ Note this release is ONLY for providers. Do not use on consumer chains.

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

This release introduces the following noteworthy changes:

• The cryptographic verification of equivocation feature is ported to SDK 0.47.
  The feature is already running on the Cosmos Hub as part of the v2.4.0-lsm release.

• It splits out consumer genesis state to reduce shared data between provider and consumer.
  As a result, the consumer CCV genesis state obtained from the provider chain needs to be transformed to be compatible with different versions of consumer chains. For more details, see the documentation.

• A query (QueryAllPairsValConAddrByConsumerChainID) is added to get a list of all assigned consumer keys for a given consumer chainId. For more details, see the documentation.

❤️ Contributors

• Decentrio (@decentriolabs)
• Informal Systems (@informalinc)

This list is non-exhaustive and ordered alphabetically.
Thank you to everyone who contributed to this release!

v3.2.0

Replicated Security v3.2.0 Release Notes

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

The main highlight of this release are the consumer-side changes for jail throttling with retries (cf. ADR 008).

⚠️ These changes are compatible with providers running previous versions (such as v2.1.0-provider-lsm or v2.4.0-lsm). Once all consumers have deployed these changes, the provider-side changes will also be deployed to production, fully enabling jail throttling with retries.

v2.4.0-lsm

Replicated Security v2.4.0-lsm Release Notes

❗ Note this release is ONLY relevant to the Cosmos Hub

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last (production ready) release.

🚀 Highlights

This is a special release of Replicated Security meant for the Cosmos Hub, introducing the new cryptographic verification of equivocation feature. Once cryptographic equivocation is integrated, validators performing double-signing or light-client attacks on consumer chains will be automatically tombstoned and have their tokens slashed. This new feature eliminates the need for equivocation proposals, such as proposal 818, thus signifying the deprecation of equivocation proposals with this release.

Note that this release fixes issues found in the v2.2.0-provider-lsm and v2.3.0-provider-lsm releases, both of which were deprecated and should not be used in production. For more details, see the changelog.

v2.3.0-provider-lsm

Replicated Security v2.3.0-provider-lsm Release Notes

❗ Note this release is ONLY relevant to the Cosmos Hub

❗ This release is deprecated and should not be used in production.

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

This is a special release of Replicated Security meant for the Cosmos Hub, introducing the new cryptographic verification of equivocation feature. Once cryptographic equivocation is integrated, validators performing double-signing or light-client attacks on consumer chains will be automatically tombstoned and have their tokens slashed. This new feature eliminates the need for equivocation proposals, such as proposal 818, thus signifying the deprecation of equivocation proposals with this release.

Note that this release fixes a bug found in v2.2.0-provider-lsm. For more details, see the changelog.

v2.3.0-provider-lsm-rc0

Replicated Security v2.3.0-provider-lsm-rc0 Release Notes

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

• (fix!) #1422 Fix a bug in the misbehaviour handling by verifying the signatures of byzantine validators.

v2.2.0-provider-lsm

Replicated Security v2.2.0-provider-lsm Release Notes

❗ Note this release is ONLY relevant to the Cosmos Hub

❗ This release is deprecated and should not be used in production.

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

This is a special release of Replicated Security meant for the Cosmos Hub, introducing the new cryptographic verification of equivocation feature. Once cryptographic equivocation is integrated, validators performing double-signing or light-client attacks on consumer chains will be automatically tombstoned and have their tokens slashed. This new feature eliminates the need for equivocation proposals, such as proposal 818, thus signifying the deprecation of equivocation proposals with this release.

v2.1.0-provider-lsm

Replicated Security v2.1.0-provider-lsm Release Notes

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

This is a special release of Replicated Security meant for the Cosmos Hub. It adds a governance proposal that enables the community to decide on the accepted denominations for consumer rewards.

v2.0.0-lsm

Replicated Security v2.0.0-lsm Release Notes

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

This is a special release of Replicated Security meant for the Cosmos Hub. It bumps Cosmos SDK to v0.45.16-ics-lsm, which introduces the Liquid Staking Module (LSM).

❤️ Contributors

• Binary Builders (@binary_builders)
• Informal Systems (@informalinc)
• Iqlusion (@iqlusioninc)
• Stride (@stride_zone)

This list is non-exhaustive and ordered alphabetically.
Thank you to everyone who contributed to this release!

v3.1.0

Replicated Security v3.1.0 Release Notes

📝 Changelog

Check out the changelog for a list of relevant changes or compare all changes from last release.

🚀 Highlights

A minor upgrade to v3.0.0, which removes the panic in the consumer ccv module which would occur in an emergency scenario where the ccv channel is closed. This release also fixes how a distribution related event is emitted, and bumps cometbft.

• (feat) #1127 Remove consumer panic when ccv channel is closed
• (fix) #720 Fix the attribute AttributeDistributionTotal value in FeeDistribution event emit.
• (deps) #1119 bump cometbft from v0.37.1 to 0.37.2.