Energy and bandwidth: what each one pays for
Energy accounts for contract computation and bandwidth for encoded transaction size. A plain TRX transfer primarily involves bandwidth accounting; a USDT transfer is a contract call and may consume both. Renting energy therefore does not supply or replace bandwidth.
Why the network splits them at all
The two resources measure different work. Bandwidth accounts for storing and relaying the encoded transaction in proportion to its size. Energy accounts for computation performed while a contract executes. Keeping them separate lets the network account for data and computation independently.
Why current account resources matter
The bandwidth available to an account can depend on its current allowance, staking or delegations, prior usage, and current network rules. Energy availability likewise depends on the account's current resource state and any delegation. Do not assume a universal account allowance or a fixed number of transactions: inspect the account resources and estimate the actual transaction before sending.
How to identify the resource involved
Start with the node or receipt message, then verify the account's current resources. OUT_OF_ENERGY points to the computation budget for contract execution; a bandwidth-related result points to accounting for encoded transaction size. The appropriate response depends on the actual transaction, the account's current resources and balance, and current network rules — not simply on renting whichever label appears.
How to compare costs
There is no fixed production ratio or categorical winner. Compare the transaction's estimated energy and encoded size with the account's current resources, current network parameters, and live rental quotes, including duration, fees, and liquidity. Energy and bandwidth are priced and delegated separately, so the result depends on the actual transaction and current conditions.
If you are sending USDT at volume, budget for both
A USDT payout is a contract call, so its resource accounting may involve both energy and bandwidth. A pipeline that rents only energy still has to account for the encoded transaction size. Before a batch, inspect the sending account's current resources, estimate both the computation and actual encoded transaction size, and compare them with current network rules and live market availability.
Frequently asked questions
Does renting energy give me bandwidth too?
No. They are separate resources with separate delegations and markets; renting or receiving one does not automatically add the other. A USDT contract call may consume both, so inspect and budget them separately.
How much bandwidth does a transfer need?
For planning, a plain TRX transfer is often estimated at about 268 encoded bytes and a USDT TRC-20 transfer at about 345, but the actual serialized size varies with the transaction's fields and encoding. Measure the prepared transaction or obtain a fresh estimate, then compare it with the account's current bandwidth and leave headroom.
Why does my wallet say the fee is zero?
A zero estimate can reflect the wallet's own estimation method and the account's current resources; the display alone does not prove which resource will cover the transaction. Inspect the transaction estimate, the account's current energy and bandwidth, and the confirmed receipt or actual balance impact.
Can I stake for one and rent the other?
When current staking and rental options support it, you can obtain the two resources separately. Choose only after comparing the actual transaction profile, current account resources, network parameters, and live market quote.