If a transaction has no nested traces, the response of debug_traceTransaction should contain the data from the original transaction (other EVM JSON RPC clients do that). Thus, instead {"jsonrpc":"2.0","id":1,"result":{"type":"","from":"","gas":"","gasUsed":"", "input":""}}, we expect the data (example with arbitrary data, they're unrelated to tested transaction hash):
Describe the bug
debug_traceTransaction
JSON RPC method returns an empty traceTo Reproduce
For instance, multiple transactions at IOTA Shimmer Testnet or IOTA EVM return a trace like this (the example hash is from Shimmer Testnet)
Expected behavior
If a transaction has no nested traces, the response of
debug_traceTransaction
should contain the data from the original transaction (other EVM JSON RPC clients do that). Thus, instead{"jsonrpc":"2.0","id":1,"result":{"type":"","from":"","gas":"","gasUsed":"", "input":""}}
, we expect the data (example with arbitrary data, they're unrelated to tested transaction hash):Network and versioning
This issue interferes to properly indexing internal transactions on the mentioned chains in the Blockscout explorer.