v1.6.2-unsafe

⚠️ Warning: This binary is not safe for use in production or critical environments.

It will panic if any staking-related transaction is submitted on-chain. If a panic occurs, immediately fall back to a “safe” binary.

Use this binary with extreme caution and only as a temporary workaround when experiencing severe latency issues or difficulty staying in sync with the main node.

v1.7.0-unsafe

⚠️ Warning: This binary is not safe for use in production or critical environments.

It will panic if any staking-related transaction is submitted on-chain. If a panic occurs, immediately fall back to a “safe” binary.

Use this binary with extreme caution and only as a temporary workaround when experiencing severe latency issues or difficulty staying in sync with the main node.

v1.6.2

Security patch:

• Patch comet bft to include security advisory GHSA-c32p-wcqj-j677

v1.7.0

WARNING: DO NOT upgrade to this binary immediately;

Upgrade Plan

The plan name for testnet is v1.7-testnet and the plan name for dryrun/mainnet is v1.7.

Improvements:

• Refactor Cronos Store
• Add db migration/patch CLI tool
• Support for preinstalls
• Support for eip2935
• Support create_access_list

Bugfixes

• Better estimation for eth_estimateGas
• Add check on evm transaction tip
• Eip712 legacy signature verify
• Replace MsgEthereumTxResponse with EthCallResponse in EVM call

See CHANGELOG

v1.6.1-unsafe

⚠️ Warning: This binary is not safe for use in production or critical environments.

It will panic if any staking-related transaction is submitted on-chain. If a panic occurs, immediately fall back to a “safe” binary.

Use this binary with extreme caution and only as a temporary workaround when experiencing severe latency issues or difficulty staying in sync with the main node.

---

Improvements:

Optimizes the staking module’s endblock processing by using a cache, significantly reducing storage access overhead and improving execution speed for archive nodes reducing endblock execution time by up to 10x

A new configuration is added to control the cache size

[staking]
# cache-size defines the maximum number of time-based queue entries to cache
# for unbonding validators, unbonding delegations, and redelegations.
# cache-size = 0 means unlimited cache (no size limit).
# cache-size < 0 means the cache is disabled.
# cache-size > 0 sets a size limit for the cache.
cache-size = 0

v1.6.1

WARNING: DO NOT upgrade to this binary immediately;

Add a security patch on top of v1.6.0

---

Upgrade Plan

The plan name for dryrun/mainnet upgrade is v1.6.

Improvements:

• E2ee logic improvements

Bugfixes

• Cleanup and improve x/mint params validation and test in cosmos-sdk

New configurations

Please add those following line in your app.toml

[mempool]
# Setting max-txs to 0 will allow for a unbounded amount of transactions in the mempool.
# Setting max_txs to negative 1 (-1) will disable transactions from being inserted into the mempool (no-op mempool).
# Setting max_txs to a positive number (> 0) will limit the number of transactions in the mempool, by the specified amount.
#
# Note, this configuration only applies to SDK built-in app-side mempool
# implementations.
max-txs = 0

# Required percentage threshold for the transaction replacement policy to take effect.
feebump = 10

###############################################################################
###                             Cronos Configuration                       ###
###############################################################################

[cronos]

# Set to true to disable tx replacement.
disable-tx-replacement = false

# Set to true to disable optimistic execution (recommended to set to true on NON validator nodes).
disable-optimistic-execution = true

Please refer to CHANGELOGS

v1.6.0

⚠️ Warning: Do not apply this version and use v1.6.1 instead

v1.5.4

Improvements🚀:

• Support new flags to controls mempool

Bugfixes

• Missing feebump for priority nonce mempool (tx replacement)

• Patch priority nonce mempool logic

• Please refer to CHANGELOGS

New configurations

Please add those following line in your app.toml

[mempool]
# Setting max-txs to 0 will allow for a unbounded amount of transactions in the mempool.
# Setting max_txs to negative 1 (-1) will disable transactions from being inserted into the mempool (no-op mempool).
# Setting max_txs to a positive number (> 0) will limit the number of transactions in the mempool, by the specified amount.
#
# Note, this configuration only applies to SDK built-in app-side mempool
# implementations.
max-txs = 0

# Required percentage threshold for the transaction replacement policy to take effect.
feebump = 10

###############################################################################
###                             Cronos Configuration                       ###
###############################################################################

[cronos]

# Set to true to disable tx replacement.
disable-tx-replacement = false

# Set to true to disable optimistic execution (recommended to set to true on NON validator nodes).
disable-optimistic-execution = true

v1.5.3

Bug fixes:

• Update BlockAddressesDecorator to check authorization list
• Please refer to CHANGELOGS

v1.5.2

⚠️ Experimental: Do not use this upgrade as it contains breaking changes.