Ethereum: debug_traceTransaction on a full node not working

Ethereum: Debugging debug.traceTransaction on a full node doesn’t work

As a full node developer, you’re probably no stranger to running Ethereum nodes and querying their internal state. However, when trying to use the debug.traceTransaction command on a full node, you may encounter unexpected behavior or errors.

In this article, we’ll dive into the details of the issue and provide a step-by-step solution to help you troubleshoot and resolve the issue.

The Problem

When using debug.traceTransaction, you need to pass the transaction ID as a string argument. In your case, the error message indicates that the node is unable to process the transaction due to a missing argument:

TypeError: Unable to read property 'address' of undefined

This error occurs because the debug command expects the transaction ID as an integer value, but you’re passing it as a string.

Debugging Steps

To resolve this issue, follow these steps:

• Check your node configuration: Make sure your full node is configured to use the correct API version. The default API version for full nodes is 4.x, but in your case, you may be using an older version.

• Check transaction IDs: Double-check that the transaction ID (in this case, 0x4883a2cd5a260723ae65b88787d153864938e0cf0b811bc0597a80e3e820777a) is correct and matches the expected format.

• Check for typos or formatting issues: Run your node with the following command:

node --debug-full --network=mainnet --miner=eth2 --max-params 20000 --rpc-pools=4 --rpc-timeout=100000 --rpc-blockstore=uniswap-v2-rpc --rpc-api-version=4.7

This will help you identify any typos or formatting issues in your transaction ID.

• Check the internal state of the node

  

  : Use the debug.geth call to inspect the internal state of the node and verify that it matches the expected output for a successful debug.traceTransaction. For example:

node --debug-full --network=mainnet --miner=eth2 --max-params 20000 --rpc-pools=4 --rpc-timeout=100000 --rpc-blockstore=uniswap-v2-rpc --rpc-api-version=4.7
geth call debug.traceTransaction '0x4883a2cd5a260723ae65b88787d153864938e0cf0b811bc0597a80e3e820777a'

This should output the expected information about the transaction, including its ID and associated data.

Solution

If the above steps do not resolve the issue, try updating your node to the latest version using geth update. Additionally, make sure you are running a supported version of the Ethereum client.

By following these steps, you will be able to troubleshoot and resolve any issues related to the debug.traceTransaction command on your full node.

SMART CONTRACT CARDANO