Checking this browser’s read-aloud support…
Two resources, different jobs
Distinguish transaction data costs from smart-contract execution costs.
TRON names two resources that are easy to mistake for token balances: Bandwidth and Energy.
- Transaction data: Bandwidth
- Token contract execution: Energy
- Receipt: result and resource use
Bandwidth is not Energy
Bandwidth accounts for transaction data. Energy accounts for smart-contract computation. A simple TRX transfer and a TRC-20 transfer therefore do not have the same resource profile: the token transfer calls a contract. Resource availability and current network parameters affect the cost; a token balance alone does not establish fee readiness.
Identify the token contract
TRX is the native asset. A TRC-20 token is represented by a smart contract implementing standard balance, transfer and allowance methods. Record its network and full contract address. A familiar name or symbol can be copied, so it cannot replace that identity when checking a balance or application.
Classify two transaction examples
Use the official resource documentation without signing anything.
- Create a row for a simple TRX transfer and a row for a TRC-20 transfer.
- Mark where transaction bytes and contract execution apply.
- Add the exact token-contract identity field to the TRC-20 row.
A token transfer is contract activity, not simply a native transfer with a different label.
Check the asset identity and the resources needed for its operation.
Progress stays on this device.
Source library
Reviewed