Are there plans to support parameter passing via the `input` field for `eth_call`?

[leonway336]

As stated in the title, when calling eth_call in TRON's JSON-RPC, changing the parameter name from data to input will result in a JSON parsing exception.

[leonway336]

#6467 Maybe this could work.

[leonway336]

Is there a release plan for version v4.8.1? Last October, it was already nearing completion. Perhaps we'll have to wait for version v4.8.2. This may be hindering many developers who need to integrate TRON JSON-RPC. eth_call is one of the most commonly used interfaces, and the lack of support for input parameters causes integration issues with SDKs across different languages.

[0xbigapple]

I’ve been following it as well.Once I see that version 4.8.1 has been released, I’ll move forward with including this feature in the next version and update here.

[halibobo1205]

v4.8.1 is approaching soon; it would be good to discuss this in the Core Devs Community Call 54 before the release.

[leonway336]

Thank you very much for your response. I look forward to your progress.

[yuval99g]

I would like to see this too

[waynercheung]

The input field alias for eth_call is a common compatibility requirement across EVM-compatible SDKs. PR #6467 has been raised as a candidate fix. We'll bring this up in Core Devs Community Call 58 to confirm the approach, and target inclusion in the next release if the discussion reaches consensus.