Skip to content

Releases: crypto-org-chain/cronos

v1.2.0-rc1

08 Apr 05:40
1aea999
Compare
Choose a tag to compare
v1.2.0-rc1 Pre-release
Pre-release

v1.2.0-rc1 is a non-breaking upgrade that includes a RPC fix for querying legacy EVM parameters.

v1.2.0-rc0

02 Apr 08:07
1ca1b14
Compare
Choose a tag to compare
v1.2.0-rc0 Pre-release
Pre-release

v1.2.0 is a consensus breaking version that fixes the randao opcode issue (see: #1367) in the v1.1.x.

Upgrade Plan

The upgrade plan name is v1.2.

v1.1.1

26 Mar 03:15
10b8eeb
Compare
Choose a tag to compare

v1.1.1 release adds additional logging, validator nodes should use this version for the v1.1.0 upgrade.

See release notes of v1.1.0: https://github.com/crypto-org-chain/cronos/releases/tag/v1.1.0

v1.1.0

19 Mar 08:39
526bc80
Compare
Choose a tag to compare

v1.1.0 is a major consensus-breaking release, which introduces precompiles and interchain-account(ICA).

Mainnet upgrade plan name: v1.1.0.

Update Highlights

  • IBC relayer precompiled contracts
  • ICA controller integration and ICA precompiled contracts
  • Transaction execution speedup
    • sender address cache
    • parameters migrated from json to protobuf

Dependency bumps

  • cosmos-sdk: v0.47.x
  • cometbft: v0.37.x
  • ibc-go: v7.3.x
  • ethermint -> crypto-org-chain/ethermint v0.21.x-cronos

Config Changes Compared To v1.0.15

config.toml

  • Renamed

    • Top-level config fast_sync is renamed to block_sync, should set to true as before.
    • The config section [fastsync] is renamed to [blocksync].
  • Deleted

  • Added

    • mempool.type = "flood"

      Keep it to the default value.

    • mempool.experimental_max_gossip_connections_to_persistent_peers = 0 and mempool.experimental_max_gossip_connections_to_non_persistent_peers = 0, see cometbft/cometbft#1584.

      Options to improve p2p network bandwidth efficiency.

app.toml

  • Added

    • mempool.max-txs = 5000.

      App side mempool is not used in Cronos v1.1.x, so ignore it.

    • json-rpc.allow-indexer-gap = true, json-rpc.return-data-limit = 100000

      Keep them to the default values.

v1.1.0-rc5

28 Feb 03:06
01d9dc6
Compare
Choose a tag to compare
v1.1.0-rc5 Pre-release
Pre-release

v1.1.0-rc5 includes a security issue fix in latest cosmos-sdk v0.47.10, it's technically consensus breaking, but if the testnet haven't slashed a re-delegation since the last upgrade, it should be fine.

CHANGELOGS

v1.1.0-rc4

20 Feb 06:38
ef3d26c
Compare
Choose a tag to compare
v1.1.0-rc4 Pre-release
Pre-release

v1.1.0-rc4 is a breaking upgrade on top of v1.1.0-rc3

Upgrade Plan Name

  • Testnet: v1.1.0-testnet-1.

Update Highlights

  • Add packet_sequence index in relayer event
  • Fix filter rule for eth_getLogs rpc API.
  • Update cosmos-sdk to latest v0.47.9.

CHANGELOG

v1.1.0-rc3

05 Feb 09:35
b7b261a
Compare
Choose a tag to compare
v1.1.0-rc3 Pre-release
Pre-release

v1.1.0-rc3 is a non-breaking upgrade based on v1.1.0-rc2.

Update Highlights

  • ⁠Graceful shutdown in memiavl.
  • ⁠Fix concurrent map access in rootmulti store.
  • ⁠Avoid version mismatch in versiondb.
  • ⁠Update ibc-go and ethermint with bug fix and improvement.

CHANGELOGS

v1.1.0-rc2

08 Jan 01:19
3317719
Compare
Choose a tag to compare
v1.1.0-rc2 Pre-release
Pre-release

v1.1.0-rc2 is a breaking upgrade based on v1.1.0-rc1, the upgrade plan name for testnet is v1.1.0-testnet.

Update Highlights

  • Adjust gas requirement of ibc precompiles.
  • Remove authz module.
  • Refactor websocket/subscription system.
  • New json-rpc API debug_traceCall.
  • Many bug fixes.

CHANGELOGS

v1.0.15

05 Jan 07:44
1f5e261
Compare
Choose a tag to compare

v1.0.15 is a non-breaking upgrade, fix two panic issues in json-rpc APIs.

CHANGELOGS

v1.0.14

16 Dec 13:46
594b5e7
Compare
Choose a tag to compare

v1.0.14 did an emergency hardfork style upgrade to update feemarket parameters, all the mainnet nodes need to update to v1.0.14 before block 11608760, otherwise you'll face app-hash mismatch error.
If you didn't update the binary in time and got the app-hash mismatch situation, you need to do a cronosd rollback first to recover, then start the node with new binary.