We are running a Substrate-based EVM chain using Frontier stable2503. During integration testing, we observed that internal transaction tracing is not available, as Frontier does not expose debug_traceTransaction or other Trace API methods required by EVM explorers and debugging tools.
This aligns with the previously reported issue:
#703
Before building our own implementation, we would like clarification on whether Frontier currently supports any Debug / Trace API modules in recent versions, or if these APIs remain unimplemented and must be added externally (as done by Moonbeam).
Environment
- Frontier version:
stable2503 (fp-*, fc-*, and EVM pallets all pinned to this branch)
- Node type: Substrate + Frontier EVM runtime
Observed Behavior
debug_traceTransaction and trace_transaction return method not found.
- Internal transfer data cannot be retrieved since the RPC layer does not emit execution traces.
- Local Geth/Anvil nodes do return full trace data, confirming the Web3 implementation is correct.
Expected Behavior
Frontier should expose APIs compatible with:
debug_traceTransaction
debug_traceCall
trace_transaction
trace_block
trace_call
…or provide an equivalent mechanism for generating and returning internal transaction traces from within the node.
Questions for Maintainers
-
Does Frontier stable2503 include any implementation of the Debug / Trace API?
Current documentation suggests it may still be missing, but confirmation would help us plan.
-
If not implemented, is there a roadmap or recommended approach for adding Trace API support to Frontier?
Request
Please confirm whether the Debug / Trace API is implemented in any active branch or release, and whether contributions in this area would be welcomed.
Thank you.
We are running a Substrate-based EVM chain using Frontier
stable2503. During integration testing, we observed that internal transaction tracing is not available, as Frontier does not exposedebug_traceTransactionor other Trace API methods required by EVM explorers and debugging tools.This aligns with the previously reported issue:
#703
Before building our own implementation, we would like clarification on whether Frontier currently supports any Debug / Trace API modules in recent versions, or if these APIs remain unimplemented and must be added externally (as done by Moonbeam).
Environment
stable2503(fp-*,fc-*, and EVM pallets all pinned to this branch)Observed Behavior
debug_traceTransactionandtrace_transactionreturn method not found.Expected Behavior
Frontier should expose APIs compatible with:
debug_traceTransactiondebug_traceCalltrace_transactiontrace_blocktrace_call…or provide an equivalent mechanism for generating and returning internal transaction traces from within the node.
Questions for Maintainers
Does Frontier
stable2503include any implementation of the Debug / Trace API?Current documentation suggests it may still be missing, but confirmation would help us plan.
If not implemented, is there a roadmap or recommended approach for adding Trace API support to Frontier?
Request
Please confirm whether the Debug / Trace API is implemented in any active branch or release, and whether contributions in this area would be welcomed.
Thank you.