Support debug_traceTransaction

Moralis General
#1

Hi,

I have this code:

const provider = new ethers.providers.JsonRpcProvider(moralisBscSpeedyNodeUrl);
const trace = await provider.send("debug_traceTransaction", txHash);
console.log(trace);

And this gives me this error:

Error: processing response error (body="{\"jsonrpc\":\"2.0\",\"id\":42,\"error\":{\"code\":-32601,\"message\":\"the method debug_traceTransaction does not exist/is not available\"}}\n", error={"code":-32601}, requestBody="{\"method\":\"debug_traceTransaction\",\"params\":[\"0x5a5a01a053998f352cb7fe8d2b7ed4ea1a4fce7f7c831677d0f0ca3d8b0d55ef\"],\"id\":42,\"jsonrpc\":\"2.0\"}", requestMethod="POST", url="https://speedy-nodes-nyc.moralis.io/f488460c8148b37d4654fee2/bsc/mainnet/archive", code=SERVER_ERROR, version=web/5.3.0)

It seems Moralis doesn’t support debug_traceTransaction. Do you plan to support it?

Thank you for making Moralis!

1 Like
#2

Hey @lcswillems

I’m not ready for answering your question now:

Do you plan to support it?

Why do you try debug_traceTransaction? If you want get status of the transaction you can use:

const transactionReceipte = await provider.getTransactionReceipt(transactionHash);
console.log(transactionReceipte.status);

The status of a transaction is 1 is successful or 0 if it was reverted.

#3

I don’t want to get the status of the transaction, I want to debug it! I.e. to know why the transaction failed on the mainnet.

#4

Hello! Any update on this?
It would be very useful enable the debug module.

#5

Hi @TokenDev

That method is not supported. It’s a very unstable method which causes a lot of bugs.

#6

On https://docs.moralis.io/misc/rate-limit#speedy-node-requests there are listings for trace_replayTransaction and debug_traceTransaction, which leads to believe that the methods are supported. Are they supported now or is that documentation inaccurate?

#7

Hello I did not get an email for discord invite. I am trying both trace_replayTransaction and debug_traceTransaction with my paid speedy nodes (fantom and avalanche) and I get does not exist method errors in the response. Please advise!

I am simply trying to find out all the native token transfers within a transaction (ftm on fantom and avax on avalanche). Is there a better way with RPC? Can I fetch the internal CALLs instead somehow?

#8

did you look in all the folders for that email?

debug_traceTransaction may not be supported, as it not included in the list of allowed calls

I don’t know how you could fetch the internal calls

#9

Nope, cannot find the email. How about trace_replayTransaction ?

#10

I asked the team about it, I don’t know the exact answer now

1 Like
#11

Hi @ajb413, please let me know your email in DMs, I’ll check what happened!

Thanks

#12

Hi, I’m also looking for a provider that supports debug_traceTransaction and/or trace_replayBlockTransactions across EVM chains. My use-case is internal calls for a given tx as well. Happy to use any other APIs that may provide these too

#13

you can try to use chainstack: https://moralis.io/largenodes

#14

Basically we need this to be able to support native token deposits from a smart contract. I don’t think there’s any alternative for this use case. Please consider supporting!