Discussion: Add input and output fields to InternalTransactions

Open
#816 29 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
databases

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
No language data
Stars
341
Forks
347
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tronprotocol/tips

All issues in tronprotocol/tips

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.