Discussion: Add input and output fields to InternalTransactions
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tronprotocol/tips
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
tronprotocol/tips#950 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#945 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#944 · 6 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
tronprotocol/tips#941 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#938 · 15 comments ·
All issues in tronprotocol/tips
Similar issues
-
bug rust
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
check:passed logos:edit
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Upgrade GeoTrellis to 3.8.1+47-304ec619-SNAPSHOTPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Open-EO/openeo-geotrellis-extensions#976 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
timescale/homebrew-tap#66 ·