Regression in `get-balance-blockhash` hive rpc-compat test

[Rjected]

Describe the bug

The hive test get-balance-blockhash fails with the following logs:

>>  {"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["0xaa00000000000000000000000000000000000000","0x898753d8fdd8d92c1907ca21e68c7970abd290c647a202091181deec3f30a0b2"]}
<<  {"jsonrpc":"2.0","result":"0x0","id":1}
response differs from expected:
 {
   "id": 1,
   "jsonrpc": "2.0",
-  "result": "0x0"
+  "result": "0x1"
 }

workflow run showing the failure: https://github.com/paradigmxyz/reth/actions/runs/5205918462/jobs/9392179645#step:6:82

This last succeeded on the following workflow run, which was on commit 43f421d0b60723b5aee13095d38edc3781f8bc15: https://github.com/paradigmxyz/reth/actions/runs/5150404477/jobs/9274781042#step:6:82

Steps to reproduce

Run the hive eth_getBalance/get-balance-blockhash test:

./hive --client reth --sim "ethereum/rpc-compat$" --sim.limit "/eth_getBalance/get-balance-blockhash"

Node logs

No response

Platform(s)

No response

What version/commit are you on?

No response

Code of Conduct

• [X] I agree to follow the Code of Conduct

[mattsse]

can we get auto issues for this?

did this occur even later, from #2945 to two days ago there are a lot of commits..

[Rjected]

can we get auto issues for this?

I'm not sure how to do this, but it would be amazing if we could get this somehow

did this occur even later, from https://github.com/paradigmxyz/reth/pull/2945 to two days ago there are a lot of commits..

The first failing workflow run is this: https://github.com/paradigmxyz/reth/actions/runs/5160721090/jobs/9297220869

which occurred at commit 2e406c1791a51ae94d1e4e8201d4796f6ef9c3e9

So it should be in this range: https://github.com/paradigmxyz/reth/compare/48bf3990a0fed4c1c06f2c649b83286a028ed0b7...2e406c1791a51ae94d1e4e8201d4796f6ef9c3e9