Add Support for eth_simulateV1 Method in Tron JSON-RPC
維護者通常 1 天內回覆
評估
這個 Issue 還沒有評估資料。
描述
Background
Currently, Ethereum provides the eth_simulateV1 method, which allows developers to simulate transactions before broadcasting them. This is useful for estimating gas usage, detecting potential reverts, and debugging smart contract interactions. However, Tron Protocol does not currently support this method, which limits the ability of developers to perform pre-execution checks efficiently.
Rationale
Why should this feature exist?
- Enhances developer experience by allowing transaction simulation before execution.
- Reduces the risk of failed transactions due to insufficient resources or contract failures.
- Aligns Tron’s JSON-RPC API with Ethereum’s, improving compatibility for developers building cross-chain applications.
What are the use-cases?
- Gas and Energy Estimation: Developers can estimate energy consumption and fees before executing a transaction.
- Smart Contract Debugging: Allows developers to test interactions with contracts without submitting real transactions.
- Transaction Outcome Prediction: Helps applications check whether a transaction will succeed before submitting it to the network.
Specification
The eth_simulateV1 method should be implemented in the Tron JSON-RPC API, following Ethereum’s standard behavior. The method should:
- Accept transaction input parameters similar to
eth_call. - Return execution results, including status, logs, and estimated energy used.
- Handle different contract call scenarios, including internal calls and delegate calls.
- Provide error messages if the transaction would fail.
Scope Of Impact
- Requires changes to the Tron JSON-RPC API.
- May require modifications to the execution engine to provide accurate simulation results.
- No backward compatibility issues, as this is a new method.
Status
Blocked by:
- #6289
- 主要語言
- Java
- 星號
- 4.2k
- 分支
- 1.8k
- 平均合併
- 3 天 21 小時
- 30 天內合併 PR
- 13
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
tronprotocol/java-tron 的其他 Issue
-
type:feature
難度 4/5 3-5 天 新手友好度 35/100
tronprotocol/java-tron#7013 · 2 則留言 ·
維護者通常 1 天內回覆
-
[Feature] Validate ECKey inputs and improve key handling可能已有人在做 @Federico2014 於 16 天前認領。 未關閉type:feature
難度 4/5 3-5 天 新手友好度 40/100
tronprotocol/java-tron#6994 · 2 則留言 ·
維護者通常 1 天內回覆
-
type:feature
難度 5/5 一週以上 新手友好度 25/100
tronprotocol/java-tron#6989 · 2 則留言 ·
維護者通常 1 天內回覆
-
Robustness fixes for multiple issues可能已有人在做 @xxo1shine 於 18 天前認領。 未關閉
難度 5/5 一週以上 新手友好度 35/100
tronprotocol/java-tron#6969 · 8 則留言 ·
維護者通常 1 天內回覆
-
[Feature] decouple json-rpc filter processing from Manager可能已有人在做 @0xbigapple 於 17 天前認領。 未關閉type:feature
難度 5/5 一週以上 新手友好度 48/100
tronprotocol/java-tron#6963 · 8 則留言 ·
維護者通常 1 天內回覆
查看 tronprotocol/java-tron 的全部 Issue
相似的 Issue
-
[BUG] S3 CORS responses omit Access-Control-Allow-Credentials for matched origins可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
sqlcipher/sqlcipher-android#97 · 1 則留言 ·
-
area-integrations
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
bug IIIF interoperability
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 2/5 1-3 小時 新手友好度 72/100