Discussion: Add input and output fields to InternalTransactions

Summary

This proposal adds input (call data) and output (return data) fields to InternalTransactions in the TRON protocol.

The Problem

TRON currently does not persist these specific fields in its database. As a result, indexers and explorers cannot fetch critical information regarding internal actions, such as:

• Function call parameters within contract-to-contract interactions.
• Deployment data for contracts created via factory patterns (internal CREATE/CREATE2).

The Solution

By capturing and storing these fields, TRON will provide complete execution traces (similar to EVM standards). This will:

• Improve Transparency: Provide full visibility into nested contract execution.
• Enable Better Indexing: Allow tools to accurately track internal state changes and factory deployments.
• Enhance Developer Experience: Simplify debugging by exposing return values from internal calls.

Reference Implementation

The code changes for java-tron are available here:
https://github.com/tronprotocol/java-tron/pull/6511

The proposal concerns InternalTransactions in the TRON protocol and points to java-tron PR #6511 as its reference implementation. Read that pull request first, then verify how input and output are persisted and exposed for indexers and explorers; completion should provide the execution-trace data described in the proposal.