TRC-20 Transaction Fees on TRON Explained
How TRC-20 transfers are paid on TRON with Energy and Bandwidth, what burning TRX costs, how to estimate it, and how to lower it. Paymaster is deprecated.
Reviewed by Maurice Sobiera
A TRC-20 transaction fee is the cost of calling a token contract on TRON. It is paid in Energy for contract execution and in Bandwidth for transaction size. If the sending address has no staked or delegated resources, the network burns TRX instead, at 0.0001 TRX per Energy and 0.001 TRX per Bandwidth on mainnet, according to the TRON documentation.
Why does a TRC-20 transfer need TRX?
A TRC-20 transfer is a smart contract call, and TRON charges resources for every contract call. The token itself never pays. According to the TRON resource documentation, Bandwidth covers the byte size of a transaction and Energy covers smart contract execution.
The standard for fungible tokens on TRON is TIP-20, known as TRC-20. A contract that follows it exposes functions such as transfer, approve and balanceOf, and each state-changing call runs on the TRON Virtual Machine.
Accounts get Bandwidth and Energy in two ways: by staking TRX, or by receiving resources that another account delegated. Each activated account also has a free Bandwidth quota of 600, but Energy has no free quota. If an address holds tokens and no TRX, no stake and no delegation, the transfer cannot be paid for. In our API such a send fails with status 422 and the message balance is not sufficient.
How much does a TRC-20 transfer cost?
The cost is the Energy used multiplied by the Energy price, plus the Bandwidth cost, when the TRX burn fallback applies. The paying for resources page lists the current mainnet burn rates:
| Resource | Burn rate | In TRX |
|---|---|---|
| Energy | 100 sun per Energy | 0.0001 TRX |
| Bandwidth | 1,000 sun per Bandwidth | 0.001 TRX |
Both rates are chain parameters that can change by proposal, so query wallet/getchainparameters for the current values. The Energy used depends on the contract and on the state of the recipient, so there is no fixed price per transfer.
As an illustration, a call that uses 65,000 Energy and 345 Bandwidth, with no resources staked, would burn 65,000 × 0.0001 = 6.5 TRX for Energy and 345 × 0.001 = 0.345 TRX for Bandwidth, so 6.845 TRX in total. These two numbers are placeholders, not measurements of a specific token. Measure your own transfer before you plan with a number.
What is the fee limit?
The fee limit is the maximum amount, in sun, that a contract call may spend on Energy. Every state-changing smart contract transaction on TRON carries a fee_limit field. According to the paying for resources page, a transaction that would use more Energy than the limit allows reverts with OUT_OF_ENERGY, and the Energy already consumed is still charged up to that limit.
The mainnet cap for fee_limit is 15,000 TRX at the time of writing, from the chain parameter getMaxFeeLimit. Set the limit above your measured Energy cost, with a margin, so that a transfer does not fail midway and still cost Energy. A high limit weakens the protection the limit gives against runaway contracts, so keep the margin modest.
How do you estimate the Energy of a transfer?
Simulate the call with the TriggerConstantContract method of the TRON node API. According to the TriggerConstantContract reference, it can estimate the Energy consumption of a contract call without broadcasting it. After a real transfer, GetTransactionInfoById returns the Energy that was actually used. Our TRON energy calculator and the TRON fee guide help with the conversion to TRX.
How can you lower TRC-20 fees?
You can stop burning TRX by supplying Energy from another source. The usual options are:
| Option | How it works | Trade-off |
|---|---|---|
| Burn TRX | The default fallback | Highest cost per transfer at the rates above |
| Stake TRX | Staking gives the account Energy and Bandwidth | TRX is locked for the duration |
| Delegate resources | Another account delegates Energy to the sender | Needs a resource provider |
| Rent Energy | A third party rents Energy from stakers in bulk | Needs a separate service |
Which option is cheapest depends on your transfer volume and on the current prices, so compare them using the measured Energy of your own transfers.
What happened to the Chaingateway Paymaster?
The Chaingateway Paymaster is deprecated. It used to cover Bandwidth and Energy inside the API, so a wallet did not need TRX before it sent TRC-20 tokens. Integrations that already call the Paymaster endpoints keep working, but you should not build new ones on them.
For sponsoring fees today we recommend TronFuel, a separate service that rents Energy in bulk from stakers. It has no endpoint in the Chaingateway API. The Sponsor TRC20 Fees guide in our documentation describes the current situation. Earlier versions of this article quoted a fixed percentage saving. We removed it because we cannot back it with a measurement: the saving depends on the burn rate, the Energy price and your volume.
How do you send a TRC-20 token with the API?
Call POST /api/v2/tron/transactions/trc20 with the sender, receiver, token contract and amount, plus the sender’s password or privatekey. The sender must have enough Energy and Bandwidth, either from staking and delegation or from TRX that can be burned. The API reference lists the parameters.
Before you send a batch of TRC-20 transfers, run through this checklist:
- Measure the Energy of one real transfer with
GetTransactionInfoById. - Check that the sending address has staked or delegated Energy, or enough TRX to cover the burn.
- Remember that the 600 free Bandwidth covers a transaction only if the whole transaction fits into it.
- Keep a record of the Energy price at the time, since it can change by proposal.
Ready to build this yourself? Get your API key — 7-day trial, no card required — or see the Tron API for the full endpoint reference.