Skip to content

Releases: ChihuahuaChain/chihuahua

v5.0.0

01 Aug 13:45
Compare
Choose a tag to compare

Version bumps

  • cosmos-sdk v0.47.4
  • ibc-go v7.2.0
  • wasmd v0.41.0

What's Changed

  • Integrated ICA
  • Implemented fee burn module and moved fee burn param from auth to fee burn module

v4.2.3 - Huckleberry patch

25 May 22:25
Compare
Choose a tag to compare

This release applies the security patch "Huckleberry" to ibc-go, upgrading it to version 4.2.2.

The details of the security advisory can be found here: IBC huckleberry security advisory.

This release is NOT consensus breaking

While this change can be applied at your own convenience, we recommend doing that at the earliest opportunity.

v4.2.2

21 Apr 01:17
Compare
Choose a tag to compare

Full Changelog: v4.2.1...v4.2.2

wasmvm version bump to v1.1.2
v4.2.1 -> v4.2.2 is non-consensus breaking

v4.2.1

26 Feb 22:55
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.2.0...v4.2.1

v4.2.0

03 Feb 16:48
Compare
Choose a tag to compare

Version bumps

  • cosmos-sdk v0.45.12
  • ibc-go v4.2.0
  • wasmd v0.30.0

What's Changed

New Contributors

Full Changelog: v4.1.0...v4.2.0

v4.1.0

15 Nov 19:02
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.0.0...v4.1.0

v4.0.0

09 Nov 15:30
ef7a6b9
Compare
Choose a tag to compare

What's Changed

  • Burnmech by @lydia-pierce in #74 burns 50% of all transaction fees
  • add static binaries by @octo-node in #72 adds a 'make build-reproducible' command
  • snapshot by @faddat in #73 fixes the wasm directory issue with snapshots

New Contributors

Full Changelog: v3.1.0...v4.0.0

v3.1.0: Revert Tombstone

31 Oct 14:28
d6e9f55
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.0.0...v3.1.0

v2.4.1: reboot the puppy

22 Oct 17:24
378d2ba
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.2.2...v2.4.1

Note: This release contains state-breaking changes

Dragon-related:

  • use wasmvm 1.1.1 (state breaking)
  • use wasmd v0.29.1 (state breaking)
  • Remove Starport / Ignite CLI (not state breaking)
  • enable iavl fast node (likely the reason the chain could only make one block at a time)

Routine TLC:

  • tendermint v0.34.22

Adverse events

This patch should work just fine. Validators should review the patch before applying it to their nodes. All validators should run this version, because mixed versions will lead to the same set of adverse events as before.

This patch could malfunction, even disastrously, but there should not be a risk to historical state of the chain. From the validator set, state exports should be made before applying the patch just in case. It would be wise to identify one or more operators of archive nodes, just in case.

If this patch either produces only one block, or burns more than it is expected to, validators should take the chain down again, and the highest VotePower validators would do well to carefully monitor the chain. Taking the chain down requires that 1/3 of VotePower go offline.

v2.2.2

14 Oct 18:40
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.2.1...v2.2.2