Releases: crypto-org-chain/chain-main
v3.3.6
October 19, 2022
This version is identical to v3.3.5, but Cosmos SDK 0.44 fork's was upgraded
to have an option to turn off the IAVL upgrade (using the IAVLDisableFastNode
option in app.toml) and it contains a security patch for the Dragonberry vulnerability.
WARNING: If you have previously upgraded to the pre-disclosure v3.3.5-dragonberry
binary, you should still upgrade to the v3.3.6 binary,
because it contains additional fixes.
NOTE that the upgrade plan name is still expected to be "v3.0.0" and that the upgrade proposal plan has incorrect links to v3.3.0 binaries (DO NOT use v3.3.0 binaries during the upgrade).
WARNING: DO NOT upgrade to this binary immediately; you can upgrade to it after the block height 3,526,800. Please follow the upgrade instructions described here https://crypto.org/docs/getting-started/upgrade_guide_draco_2.html .
v4.0.0-beta1-croeseid
This is the testnet beta
release of Crypto.org Chain's v4.0.0
. It contains following changes (when compared with v3
):
Added
- Support for interchain accounts. #730 #732 #733
- IBC Fee middleware for incentivizing relayers. #763 #834
- Add support for NFT transfer via IBC. #860
- Set default
min_commission_rate
to5%
. #845
Changed
- Upgrade
cosmos-sdk
tov0.46.1
andibc-go
tov5.0.0
. #850 #869 - Changed go version to
1.18
. #803 - Add
url
inx/nft
'sDenom
. #860
Deprecated
- Marked
x/supply
module, including its CLI and gRPC, as deprecated. #724
Security
- Security fixes for Swagger UI. #704
v4.0.0-alpha6-croeseid
This is the testnet alpha
release of Crypto.org Chain's v4.0.0
. It contains following changes (when compared with v4.0.0-alpha5-croeseid
):
Added
Changed
v3.3.5
September 5, 2022
This version is identical to v3.3.3, but Cosmos SDK was upgraded to a
custom fork that is based on its latest v0.44.x release (v0.44.8),
but reverted the state machine breaking change introduced in v0.44.6
and cherry-picked the IAVL upgrade-related changes from v0.45.x release.
NOTE: The IAVL v0.19 upgrade introduces a new index that improves performance,
but when the node is started up for the first time, it may take a while
for the index to be initialized (a few minutes or hours depending on the node
configuration and underlying hardware).
NOTE that the upgrade plan name is still expected to be "v3.0.0" and that the upgrade proposal plan has incorrect links to v3.3.0 binaries (DO NOT use v3.3.0 binaries during the upgrade).
WARNING: DO NOT upgrade to this binary immediately; you can upgrade to it after the block height 3,526,800. Please follow the upgrade instructions described here https://crypto.org/docs/getting-started/upgrade_guide_draco_2.html .
v4.0.0-alpha5-croeseid
v4.0.0-alpha4-croeseid
This is the testnet alpha
release of Crypto.org Chain's v4.0.0
. It contains following changes (when compared with v4.0.0-alpha3-croeseid
):
Added
Changed
Security
- Upgraded CodeQL scanning pipeline. #773
v4.0.0-alpha3-croeseid
This is the first testnet alpha
release of Crypto.org Chain's v4.0.0
. It contains following changes (when compared with v4.0.0-alpha1):
Added
- IBC Fee middleware for incentivizing relayers (only for IBC transfers). #763.
Testing
v4.0.0-alpha1
v3.3.4
March 1, 2022
This release is identical to v3.3.3 except for following changes:
cosmos-sdk
was upgraded tov0.44.6
ibc-go
was upgraded tov2.0.3
tendermint
was upgraded tov0.34.16
- Security fixes for Swagger UI
NOTE that the upgrade plan name is still expected to be "v3.0.0" and that the upgrade proposal plan has incorrect links to v3.3.0 binaries (DO NOT use v3.3.0 binaries during the upgrade).
WARNING: DO NOT upgrade to this binary immediately; you can upgrade to it after the block height 3,526,800. Please follow the upgrade instructions described here https://crypto.org/docs/getting-started/upgrade_guide_draco_2.html .
v1.2.2
January 27, 2022
This release is identical to v1.1.1, but is built with Go 1.17 and supports Arm64 binaries as well as a RocksDB database backend.
Improvements
- support release for Arm64 (Linux and macOS)
- support rocksdb in makefile
Bug Fixes
- resolve go module name v1 issue