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
As an infra provider, I want debug_trace* to support a variety of tracers, including flatCallTracer so that I have feature parity between my Besu and Geth/Reth nodes.
Acceptance Criteria
debug_trace* methods allow configuration of the tracer used. Accepted options include flatCallTracer, callTracer and prestateTracer.
Output is identical and consistent with other clients
Example request: {"method":"debug_traceBlockByHash","params":["0xa300bb5b420026615bf2e31b2ea0a8b187afeab8a228cc62a663b1e8a974bac8",{"tracer":"flatCallTracer"}],"id":1,"jsonrpc":"2.0"}
Description
As an infra provider, I want debug_trace* to support a variety of tracers, including
flatCallTracer
so that I have feature parity between my Besu and Geth/Reth nodes.Acceptance Criteria
tracer
used. Accepted options include flatCallTracer, callTracer and prestateTracer.Example request:
{"method":"debug_traceBlockByHash","params":["0xa300bb5b420026615bf2e31b2ea0a8b187afeab8a228cc62a663b1e8a974bac8",{"tracer":"flatCallTracer"}],"id":1,"jsonrpc":"2.0"}
Some useful links:
Geth Tracer Examples https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers#prestate-tracer
Reth Tracing guide https://github.com/paradigmxyz/ultimate_evm_tracing_reference
The text was updated successfully, but these errors were encountered: