Add TracerConfig Support and Implement Contract Tracer

[JukLee0ira]

Proposed changes

1. Add TracerConfig to Existing Tracer:

   • Added a TracerConfig option, primarily for onlyTopCall, to provide more control over which calls are traced.

2. Implement ContractTracer:

   • Introduced a new ContractTracer to locate created contracts and return their addresses.
   • Added configuration options to retrieve the corresponding contract bytecode when needed.

Example

Request

RPC="http://172.16.3.16:8547"
NUMBER="0x399e"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 1002,
  "method": "debug_traceBlockByNumber",
  "params": [
    "'"${NUMBER}"'", {
        "tracer":"contractTracer"
    }
  ]
}' | jq

Response

{
  "jsonrpc": "2.0",
  "id": 1002,
  "result": [
    {
      "result": [
        "0xf63f8ba05d790b93db0005de3e65d90cd0b68bf6"
      ]
    }
  ]
}

Request

RPC="http://172.16.3.16:8547"
NUMBER="0x3a9e"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 1002,
  "method": "debug_traceBlockByNumber",
  "params": [
    "'"${NUMBER}"'", {
        "tracer":"contractTracer","tracerConfig": {"opCode": "PREVRANDAO"}
    }
  ]
}' | jq

Response

{
  "jsonrpc": "2.0",
  "id": 1002,
  "result": [
    {
      "result": [
        "0xf63f8ba05d790b93db0005de3e65d90cd0b68bf6"
      ]
    }
  ]
}

Request

RPC="http://172.16.3.16:8547"
NUMBER="0x399e"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 1002,
  "method": "debug_traceBlockByNumber",
  "params": [
    "'"${NUMBER}"'", {
        "tracer":"contractTracer","tracerConfig": {"opCode": "PRO"}
    }
  ]
}' | jq

Response

{
  "jsonrpc": "2.0",
  "id": 1002,
  "result": [
    {
      "error": "opcode PRO not defined"
    }
  ]
}

Types of changes

What types of changes does your code introduce to XDC network?
Put an ✅ in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)
• Regular KTLO or any of the maintaince work. e.g code style
• CICD Improvement

Impacted Components

Which part of the codebase this PR will touch base on,

Put an ✅ in the boxes that apply

• Consensus
• Account
• Network
• Geth
• Smart Contract
• External components
• Not sure (Please specify below)

Checklist

Put an ✅ in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

• This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
• Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
• Tested the backwards compatibility.
• Tested with XDC nodes running this version co-exist with those running the previous version.
• Relevant documentation has been updated as part of this PR
• N/A

[s1na]

Can you please explain what this is for?

[JukLee0ira]

If we only need to return the code without specifying an opcode, we should record the contract address here.

To find the CALL opcode, we should search within CaptureState. The CALL opcode here isn’t part of the contract’s internal opcodes. I was confused about this but have now corrected it.