stateOverrides of debug_traceCallMany does not work

[ET-Chan]

Describe the bug

stateOverride fails to override storage correctly.

Steps to reproduce

1. Send the following request to debug_traceCallMany endpoint to a RETH alpha.6 node

[{"transactions": [{"from": "0x1b5212AF6b76113afD94cD2B5a78a73B7d7A8222", "to": "0xdAC17F958D2ee523a2206206994597C13D831ec7", "data": "0x70a082310000000000000000000000001b5212af6b76113afd94cd2b5a78a73b7d7a8222"}]}]


{"blockNumber": "latest", "transactionIndex": -1},

{"tracer": "callTracer", "tracerConfig": {"onlyTopCall": false, "withLog": true}, "stateOverrides": {"0x1b5212AF6b76113afD94cD2B5a78a73B7d7A8222": {"balance": "0x39726378b58c400000", "stateDiff": {}}, "0xdAC17F958D2ee523a2206206994597C13D831ec7": {"stateDiff": {"0xede27e4e7f3676edbf125879f17a896d6507958df3d57bda6219f1880cae8a41": "0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"}}}}

The first tx is just asking for balanceOf 0x1b5212AF6b76113afD94cD2B5a78a73B7d7A8222 (this is a random address).

The 1st overwrite ensures the sender address has enough balances to pass gas fee checks.

The 2nd overwrite is overwriting the balances['0x1b5212AF6b76113afD94cD2B5a78a73B7d7A8222'] of 0xdAC17F958D2ee523a2206206994597C13D831ec7 (USDT)

2. It returns the following:

[{"from": "0x1b5212af6b76113afd94cd2b5a78a73b7d7a8222", "gas": "0x2faf080", "gasUsed": "0x13a7", "to": "0xdac17f958d2ee523a2206206994597c13d831ec7", "input": "0x70a082310000000000000000000000001b5212af6b76113afd94cd2b5a78a73b7d7a8222", "output": "0x0000000000000000000000000000000000000000000000000000000000000000", "value": "0x0", "type": "CALL"}]

3. If the exact same code is run against quicknode, the following response will be returned instead:

[[{"from": "0x1b5212af6b76113afd94cd2b5a78a73b7d7a8222", "gas": "0x23c2f248", "gasUsed": "0x675f", "to": "0xdac17f958d2ee523a2206206994597c13d831ec7", "input": "0x70a082310000000000000000000000001b5212af6b76113afd94cd2b5a78a73b7d7a8222", "output": "0x0000ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff", "value": "0x0", "type": "CALL"}]]

Node logs

There is no log related to this JSON request.

Platform(s)

Linux (x86)

What version/commit are you on?

reth 0.1.0-alpha.6 (f53fdd5)

What database version are you on?

Current database version: 1

If you've built Reth from source, provide the full command you used

RUSTFLAGS="-C target-cpu=native" cargo build --profile maxperf --features jemalloc

Code of Conduct

• I agree to follow the Code of Conduct