How energy and bandwidth work on TRON when swaps burn TRX
How energy and bandwidth work on TRON: swaps use Energy for contract execution, and wallets burn TRX when staking or delegation leaves a shortfall.
By Web3 Hub Newsroom3 min read
A team wallet making daily SunSwap trades burns TRX when it lacks Energy: each swap calls a smart contract, and TRON burns TRX to cover any Energy shortfall. Review SunSwap next to identify the exchange your team uses while applying these resource costs to its swaps. Energy comes from staking TRX or receiving delegated Energy; without enough available, the wallet pays in TRX.
Energy pays for swaps; Bandwidth pays for transaction bytes
Energy measures the computation a smart contract runs, while Bandwidth covers the bytes in a transaction. A swap uses both resources, but Energy is usually the cost that makes a trading wallet’s TRX balance fall.
Approving a token and swapping it are separate contract calls, so each can consume Energy. The swap’s Energy use depends on the contract and route: a route with more hops can require more computation. The amount can therefore vary from one trade to another, even for the same wallet.
TRON first applies Energy available to the caller, including staked or delegated Energy. It burns TRX for the remaining shortfall, up to the transaction’s fee limit. The calculation is: Energy shortfall × the network’s Energy price, a rate set through network governance. Bandwidth has its own allowance and burn rules, but it covers transaction size rather than contract execution.
That is why a team wallet can pay TRX on every trading day: its Energy allowance may be empty or too small each time it submits a swap or approval. Unused Energy recovers over time, so recent activity affects how much is available for the next transaction.
A treasury can stake TRX and delegate Energy to trading wallets
Stake 2.0 lets one address stake TRX for Energy, then delegate that Energy to other addresses. A team can use a treasury address as its staking pool and send delegated Energy to each wallet that signs swaps.
In TronLink, the team can manage the treasury stake and its resource delegations, then check each trading wallet’s available Energy before setting its trading budget. Track Energy consumed per swap and the current network Energy price; together, those figures help estimate the TRX burn a wallet would face without delegation. Leave enough Energy available for both approvals and swaps, since an approval can use resources before the trade begins.
The deciding factor is whether a wallet has enough Energy when its contract call executes. Stake and delegate from the treasury, and regular team swaps can draw on that Energy instead of burning TRX for each shortfall.