Skip to content

debug_traceTransaction, debug_traceBlockByHash, debug_traceBlockByNumber return missing internal transfer #3520

@nhattm-lotussoft

Description

@nhattm-lotussoft

Describe the bug
When run either debug_traceBlockByNumber, debug_traceBlockByHash, or debug_traceBlockByNumber method to get trace data of internal transfer on some transaction, IOTA internal transfer call is not found in the result, only the external call found.

The IOTA balance history does shown that there is internal transfer; and the contract logic (contract code verified) does shown to have IOTA transfer in the function.

To Reproduce
Run the following

curl -sL \
  -H "Content-Type:application/json;charset=utf-8" \
  -d "{
      \"jsonrpc\": \"2.0\",
      \"id\": 1,
      \"method\": \"debug_traceTransaction\",
      \"params\": [
          \"0xd77045b2f858a170e35d9ce2e24fca6cfc6ed63a0742237e3e7ff47d8bae211b\",
          { \"tracer\": \"callTracer\"}
      ]
  }" \
https://json-rpc.evm.iotaledger.net

RPC response body:
{
  type: 'CALL',
  from: '0x38515a0a36ef49d313f447efdce8e525a08a925f',
  gas: '0xdb648',
  gasUsed: '0x0',
  to: '0x25d526ba7c9905c764aeb63bfe0b0ddf1c69bce1',
  input: '0x81c2fdfb0000000000000...',
  value: '0x0'
}

Expected behavior
The response should have an internal call data that transfer IOTA from 0x25d526ba7c9905c764aeb63bfe0b0ddf1c69bce1 to 0x38515a0a36ef49d313f447efdce8e525a08a925f

RPC response body:

{
  type: 'CALL',
  from: '0x38515a0a36ef49d313f447efdce8e525a08a925f',
  to: '0x25d526ba7c9905c764aeb63bfe0b0ddf1c69bce1',
  input: '0x81c2fdfb0000000000000...',
  value: '0x0',
  gas: '0xdb648',
  gasUsed: '0x0',
  calls": [
        {
            "type": "CALL",
            "from": "0x25d526ba7c9905c764aeb63bfe0b0ddf1c69bce1",
            "to": "0x38515a0a36ef49d313f447efdce8e525a08a925f",
            "value": "0x...",
            "input": "0x...",
            "gas": "0x...",
            "gasUsed": "0x..."
        }
    ]
}

Network and versioning

  • Type of L1 network: IOTA EVM Mainnet
  • Type of Wasp chain: unknown
  • Interaction method: JSON/RPC HTTP
  • Interaction software: API
  • Version of Wasp unknown

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions