eth_getLogs returns no logs when a specific pre-bedrock block range is queried

[AntonieDavid]

Describe the bug

We identified a block range that returns no logs when queried using an op-reth node, while the same range returns multiple logs when queried on an op-geth node.

Steps to reproduce

curl -H "Content-Type: application/json" \ -X POST http://localhost:8545 \ --data '{"jsonrpc":"2.0","method":"eth_getLogs","params":[{"fromBlock":"0x173756C","toBlock":"0x17378C6"}],"id":1}'

Node logs

Platform(s)

No response

Container Type

Other

What version/commit are you on?

v1.5.1

What database version are you on?

.

Which chain / network are you on?

optimism mainnet

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

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

No response

Code of Conduct

• I agree to follow the Code of Conduct

[emhane]

unless you have explicitly imported pre-bedrock state, then the default op-reth mainnet node doesn't have pre-bedrock state as it has no support for syncing ovm state from the network.

[mattsse]

@emhane do you know if the historical rpc nodes can handle this endpoint?

[emhane]

@emhane do you know if the historical rpc nodes can handle this endpoint?

not sure, have emailed @AntonieDavid