Closed iron4548 closed 2 months ago
Looks like some failed Ethereum transactions don't have an transactionRecord.ethereumHash
populated and we're not properly copying HAPI transaction hash in those cases. Need to also check if consensus nodes should always be populating the ethereum hash.
https://mainnet.mirrornode.hedera.com/api/v1/contracts/results?timestamp=1722306953.589947003 https://mainnet.mirrornode.hedera.com/api/v1/transactions?timestamp=1722306953.589947003
Description
DexScreener have been running into an issue using JSON RPC using ethers. They've passed this on to us to report here.
The following code resulted in a 'invalid hash' error via ethers at block 67137631. This isn't the first time they encountered it. They encountered the same issue using hashio.io and validation cloud.
Investigation is required why some transactions without a hash is returned from a mirror node. Ideally the transactions that doesn't contain a valid hash should not be returned via JSON RPC.
Steps to reproduce
Run this code:
Additional context
No response
Hedera network
mainnet
Version
live
Operating system
None