Open AlbertMakhortov opened 2 months ago
Hi, thanks for posting the issue! :)
I've taken a look at this, and it seems like the transactions you mentioned are all from pre-bedrock. When using traceBlock on pre-bedrock blocks, we fallback to historical rpc, which is essentially legacy geth.
This addition of txHash
to the result of debug_traceBlock
was added around this time last year and doesn't seem like it was added to legacy geth. So, unfortunately, all responses of debug_traceBlock
on pre-bedrock blocks will not have the txHash
.
Is the txHash
essential to your service's logic? I think it would be best to handle this edge case where txHash
doesn't exist with something like 0x0
for now. Are there any instances of this happening on post-bedrock blocks as well by any chance?
@AlbertMakhortov Do you need any more help with this? Would it be okay to close this issue for now? :)
System information
Erigon version: 2.57.3-0.5.2-amd64
Expected behaviour
After making a debug_traceBlockByHash call txHash should be present in the response
Actual behaviour
At least for this blocks it is not present
0x8326c86e5528116e14e70238c16e39fb6b3eeb2255e41a8f2b71515a778b7719
0xeab0b969536d35ff771d76e9c3543078f37437b78b568d1c913c83a6c76a0699
0xe1ba72adf6dc8fac1381fc2e8c475064a2226ee6409fdda559a3eb883d08ec92
curl example:
part of the response, so we can observe that txHash is not there:
On most of the blocks it works as expected, with txHash in the response