v1.7.5

Bugfixes

• Fix RPC eth_getBlockReceipts crash when querying old block with duplicate transactions.
• BLOBBASEFEE Opcode Nil Pointer Dereference
• Unauthenticated IBC ClientStates Query Causes ABCI Panic

Features

• Support eth_simulateV1 json-rpc

v1.7.5-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.4

Additional fixes for a stability issue and improved chain reliability.

v1.7.4-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.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.

v1.7.1

Bugfixes

Fix RPC eth_getBlockReceipts crash when querying old block with duplicate transactions.

Descriptions of issue

In Cronos versions prior to v0.7, a vulnerability allows the same transaction to be executed multiple times across different blocks. This results in duplicate transaction hashes existing at different block heights. Because standard Ethereum-style indexers and RPC nodes assume transaction hashes are unique identifiers, this causes data inconsistency and retrieval failures.

Solution

When calling eth_getTransactionReceipt for a duplicated hash, the RPC returns only the receipt for the transaction at the most recent block height, effectively "shadowing" or overwriting the visibility of the earlier execution (match with Cronos Explorer)

When relying on eth_getBlockByNumber or eth_getTransactionByBlockNumberAndIndex, indexers may still encounter duplicate transactions. In these instances, the indexer must implement a custom reconciliation strategy to handle non-unique transaction hashes

v1.7.0-windowfix

Fix window binary for v1.7.0 release

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.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