Discrepancy between reth and geth debug_traceTransaction

[cody-wang-cb]

Describe the bug

There's a transaction on Base that was reverted
https://basescan.org/tx/0x583c2ac33aa9071d1087a020581625c9191cb73c1e3b5d6ca8dd2e79727c0620

However when curling with

curl -X POST \
  -H "Content-Type: application/json" \
  --data '{
  "id": 0,
  "method": "debug_traceTransaction",
  "params": [
    "0x583c2ac33aa9071d1087a020581625c9191cb73c1e3b5d6ca8dd2e79727c0620",
    {
      "timeout": "60s",
      "tracer": "flatCallTracer",
      "tracerConfig": {
        "convertParityErrors": true
      }
    }
  ],
  "jsonrpc": "2.0"
}'

the response from reth does not contain "error": "Reverted",, while the geth response contains that.

geth.json

reth.json

Same thing with callTracer as well.

Steps to reproduce

Check debug trace on 0x583c2ac33aa9071d1087a020581625c9191cb73c1e3b5d6ca8dd2e79727c0620 to a reth vs. geth node to see the discrepancy

Node logs

Platform(s)

No response

Container Type

Docker

What version/commit are you on?

1.5.0

What database version are you on?

N/A

Which chain / network are you on?

Base 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

[cody-wang-cb]

just saw this actually
#17255

[mattsse]

probably the same issue, fixed here #17412

evaluating when to cut a patch, primarily for this issue

[cody-wang-cb]

Sounds good. Btw some others reported that this issue didn't exist in reth 1.4.3, so probably was introduced in some later releases

[mattsse]

confirmed this has been fixed on main