Skip to content

Fix Typo: Correct "TransactionExtention" to "TransactionExtension" in Documentation #458

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix Typo: Correct "TransactionExtention" to "TransactionExtension" in Documentation #458

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/releases/history.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2081,7 +2081,7 @@ Source code：https://github.com/tronprotocol/java-tron/pull/4045
In GreatVoyage-v4.4.0 (Rousseau), the following optimizations have been introduced to the `TriggerConstantContract` interface:
- Execute contract creation when `ContractAddress` is empty
- Remove the check of the incoming parameters `callvalue` and `tokenvalue`
- The log list and internal transaction list are added to `TransactionExtention`
- The log list and internal transaction list are added to `TransactionExtension`

Source Code： https://github.com/tronprotocol/java-tron/pull/4032

Expand Down Expand Up @@ -2164,7 +2164,7 @@ GreatVoyage-v4.3.0 (Bacon) provides a new ABI type Error, which is a custom erro

### API

#### 1. Add a New Field: `energy_used` in `TransactionExtention`
#### 1. Add a New Field: `energy_used` in `TransactionExtension`
Users cannot forecast the energy usage of smart contract transactions in versions earlier to GreatVoyage-v4.3.0 (Bacon).
The version of GreatVoyage-v4.3.0 (Bacon) adds the `energy_used` field to the `TransactionExtension`. When the user invokes the contract method via `TriggerConstantContract`, a sandbox environment based on the most recently synchronized block at the current node is created to supply TVM with this method call. Following the execution, the actual energy consumption figure is written to the `energy_used` field(this operation will not generate an on-chain transaction, nor will it change the status of the current node).

Expand Down