Energy and bandwidth: one transfer, two meters

One pays for bytes. The other pays for code. Neither covers for the other.

TRON has no single gas. It bills two resources, and they do not substitute for each other. Bandwidth pays for the size of your transaction in bytes. Energy pays for the contract code that runs when the transaction executes. A USDT TRC-20 transfer spends both, and nearly the whole bill is energy.

Which is why a wallet can tell you the free daily allowance is untouched and still refuse to send USDT. The allowance is bandwidth. The transfer is stuck on the other meter.

One fee on Ethereum, two budgets here

If your habits come from Ethereum or BSC, you expect one fee that covers everything and one balance that pays it. TRON splits the bill. Bytes are one budget, computation is another, and each runs out separately. The split is not a billing detail: it decides which error you get and which fix works.

Why energy is the expensive half

Every account gets a free bandwidth allowance. It renews each day and covers roughly one token transfer, which is why light users never think about it. Energy has no free allowance at all. It comes from staking TRX yourself, or from someone delegating theirs to you, or it does not arrive and the chain settles the gap by destroying TRX out of your balance at a rate it sets itself.

That last sentence is the whole of what people mean by expensive TRON fees. A single transfer into a wallet that has seen USDT before goes for — TRX that way, against — to rent the same amount of energy for an hour.

How each one comes back

The three sources refill on three different clocks, and mixing them up is how people end up stranded halfway through a batch.

• The free bandwidth allowance resets on its own daily cycle. Nothing to do, nothing to buy, and no way to raise the ceiling.
• Energy from your own stake regenerates gradually over a day rather than arriving in one lump. Spend it all in an hour and you wait for it, not for a payment to clear.
• Delegated energy is a block of units that sits on the address for a fixed window and then lifts. Inside that window it behaves exactly like energy you staked for.

Full on one meter, empty on the other

Bandwidth to spare, no energy. The transaction is accepted, reaches a block, runs out partway through the contract and reverts. Your USDT never moves and the TRX spent getting that far is gone. This is OUT_OF_ENERGY.

Energy delegated, no bandwidth and no TRX. Nothing gets that far. The bytes are paid for before the network accepts the transaction at all, and an empty allowance next to an empty TRX balance leaves nothing to pay with. That is the trap in a wallet holding only USDT: sending USDT with zero TRX.

Neither, but plenty of TRX. Both meters fall back to TRX, the transfer goes through and you pay the expensive way for something you could have rented.

How energy moves without any coins moving

An address holding staked TRX can point its energy at another address for a set time. The coins stay staked where they are, the receiving address gets the resource, and the arrangement expires on a timer. The network needs to know one thing to do it: which address the energy is for. No key, no signature, no wallet connection, on either side. That is the whole product here, sold by the hour.

The number to plan is energy

Bandwidth looks after itself for most people. Energy is the one worth deciding in advance: 65,000 for a transfer to an address that already holds USDT, 131,000 for one that has never seen it. The reason it doubles is on how much energy a transfer needs, and the three ways of paying for it are weighed on burning, staking or renting.