You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Expected behavior
The response should have an internal call data that transfer IOTA from 0x25d526ba7c9905c764aeb63bfe0b0ddf1c69bce1 to 0x38515a0a36ef49d313f447efdce8e525a08a925f
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
Expected behavior
The response should have an internal call data that transfer IOTA from 0x25d526ba7c9905c764aeb63bfe0b0ddf1c69bce1 to 0x38515a0a36ef49d313f447efdce8e525a08a925f
RPC response body:
Network and versioning
The text was updated successfully, but these errors were encountered: