You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
shekhirin
changed the title
Anvil's debug_traceTransaction behaviour differences from geth
Anvil's debug_traceTransaction behaviour differs from geth
Sep 14, 2022
Good catch. Yep we want this to be 1:1 compatible. cc @mattsse to keep this in mind for reth, we want byte compatibility I think with Geth RPC (esp. for debug_traceTransaction) and with Parity's tracing responses
Component
Anvil
Describe the bug
As of 6e5a613, Anvil's
debug_traceTransaction
differs from geth in several places which are also on screenshots:Incorrect memory state duringIt was fixed for Geth in ethereum/go-ethereum@97f308a but my RPC uses Erigon which doesn't have these changes and still does memory expansion before tracing: https://github.com/ledgerwatch/erigon/blob/cd8cad6a8908970fa092aa5e2dcd8f38aedccd89/core/vm/interpreter.go#L316-L323MSTORE
foundry/evm/src/executor/inspector/tracer.rs
Lines 138 to 139 in 6e5a613
The text was updated successfully, but these errors were encountered: