[Failed-Request-Alert-Tuning] eth_getTransactionReceipt method returns too many 500 errors

[quiet-node]

Problem

On the mainnet, an excessive number of log entries indicate 500 errors for the eth_getTransactionReceipt endpoint. One notable error message is:

• Error invoking RPC: Invalid parameter: hashOrNumber – This appears to stem from an empty blockHash in the synthetics log.
• Cannot read properties of null (reading 'toString') - This could potentially fixed by #3349

Updated: The Error invoking RPC: Invalid parameter: hashOrNumber error was also triggered in scenarios where block_hash was set as an empty hex string ("0x"), as detailed in #3349. Consequently, this issue is expected to be resolved by the changes implemented in #3349.

Solution

Investigate and resolve the root cause of the 500 errors in the eth_getTransactionReceipt endpoint. Ensure robust error handling and accurate processing of block data to prevent invalid parameters and enhance system reliability.