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