Closed ongrid closed 1 year ago
The JS tracer has been deprecated as of v1.7.10 and we do not plan to re-introduce support for it.
You can find similar functionality in the existing call tracer (here's the go-ethereum documentation for it: https://geth.ethereum.org/docs/rpc/ns-debug#debug_tracetransaction), but the ability to upload your own JS tracer has been removed.
Why did you remove js tracer?
Why did you stop supporting the JS tracer? Also, could you please share with me the commitment that you removed?
If anyone is interested in info about in which commits it have been removed - here it is:
@dm3ch This is very helpful! Thank you
For better or worse, due to popular demand, the JS tracer was re-introduced in v1.9.9
Why was it ever removed?
Describe the bug
Both avalanchego (at least v1.7.18) and subnet-evm (v0.2.5-v0.2.9) have unsupported or broken JavaScript-based tracer returning "tracer not found" to such requests. This kind of requests is widely used in popular explorers like Blockscout.
To Reproduce Run avalanchego/subnet-evm archive node with the following config:
{"pruning-enabled": false, "eth-apis": ["public-debug", "private-debug", "debug-tracer"]}
After it gets bootstrapped run
It returns Error object
and raises the following log message
The same situation on evm-subnet as well.
It's noteworthy that the basic non-JS tracer seem to be operational and return trace data.
Expected behavior
Expected long dict with detailed trace of given transaction expected to be returned.
Logs
Operating System
Ubuntu Server LTS
Context
Blockscout's internal transaction fetcher uses JavaScript-based tracer. Both avalanchego v1.7.18 and subnet-evm v0.2.9 return "tracer not found" to such requests.
For more details see https://github.com/blockscout/blockscout/issues/5729