Tron `eth_call` returns "CPU timeout" for contract view functions

[bbaktaeho]

Summary

eth_call on certain Tron contracts consistently returns -32000 / "CPU timeout for '<OPCODE>' operation executing". Reproduces against the public Tron JSON-RPC (https://api.trongrid.io/jsonrpc), so it is a network-level limit — not a node-specific issue.

Reproduction

• Contract: TEWiwo3sttmmbJrHtq25rVNtZuREo7asgb (0x31d664ca251e3ebc30f2d90d1d9b1aae33f87e62)
• Endpoint: https://api.trongrid.io/jsonrpc

ADDR="0x31d664ca251e3ebc30f2d90d1d9b1aae33f87e62"
URL="https://api.trongrid.io/jsonrpc"

# balanceOf(address,uint256)
curl -s -X POST -H "Content-Type: application/json" -d \
"{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"eth_call\",\"params\":[{\"to\":\"$ADDR\",\"data\":\"0x00fdd58e000000000000000000000000f79db8d4e9baf5266b2578790363f027ae550b7a0000000000000000000000000000000000000000000000000000000000000001\"},\"latest\"]}" $URL

Response: {"error":{"code":-32000,"message":"CPU timeout for 'DUP1' operation executing"}}

[yanghang8612]

It appears that any call to this contract ultimately results in an infinite self-recursion.

Additionally, smart contract transactions on TRON have an 80-millisecond execution time limit, which is a built-in part of the protocol. This limit also applies to interfaces that simulate execution.

Therefore, we suspect that there may be some issues with the implementation of your contract code or that the overall logic is relatively complex, causing certain calls to consistently result in timeouts during execution.

We recommend that you carefully review your contract code.