Discussion: Add input and output fields to InternalTransactions

未关闭
#816 29 条评论 3 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
databases

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
没有语言数据
星标
341
派生
347
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tronprotocol/tips 的其他 Issue

查看 tronprotocol/tips 的全部 Issue

相似的 Issue

更多 Databases Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。