Bitcoin Forum
November 18, 2026, 02:32:10 PM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: TRON USDT Transfer Failed with OUT_OF_ENERGY: What Happened to Your TRX?  (Read 6 times)
Tronilend (OP)
Newbie
*
Offline

Activity: 1
Merit: 0


View Profile
Today at 01:09:33 PM
 #1

TRON USDT Transfer Failed with OUT_OF_ENERGY: What Happened to Your TRX?

This question keeps coming up in different threads, so here is a single write-up. The situation: someone sends USDT (TRC-20), the wallet or TronScan shows FAILED – OUT OF ENERGY, the recipient gets nothing, and yet the sender's TRX balance went down. Is the USDT lost? Can the TRX be recovered? What should be fixed before the next try?

Short answers: the USDT is almost always still on the sender's address, burned TRX cannot be recovered, and sending the same thing again without changing anything will usually fail the same way.

Why the USDT did not move

A USDT transfer on TRON is not a plain balance change like a TRX transfer. It calls the transfer function of the USDT smart contract, and contract execution is paid in Energy (Bandwidth covers the transaction size). When the Energy budget runs out before the contract finishes, execution stops with OUT_OF_ENERGY and every state change is rolled back. The token balances return to where they were, so the recipient receives nothing and the USDT stays with the sender.

Why TRX was still charged

Rollback applies to the token balances, not to the resources. The network already executed part of the contract before the budget ran out. According to the TRON developer docs on VM exceptions, an OUT_OF_ENERGY execution counts all Energy that was available to it as consumed, and TRX burned to pay for Energy is not returned. So the loss is whatever budget the call had: delegated or staked Energy that got used, plus TRX burned for the rest. If the address had no Energy and almost no TRX, the call may fail almost immediately and cost very little; if it had a partial budget, that whole budget can be spent on an attempt that delivers nothing.

The part people miss: the recipient changes the cost

As rough orientation, a USDT transfer to an address that already holds USDT needs about 65,000 Energy. To an address with a zero USDT balance it needs about 131,000. These are not guaranteed numbers: TRON's Dynamic Energy Model adjusts the cost of busy contracts over time. The amount sent does not matter; 1 USDT and 10,000 USDT cost the same.

A hypothetical illustration: a sender has 65,000 rented Energy and 3 TRX. At the current network price of 100 sun per Energy (0.0001 TRX), 3 TRX buys 30,000 Energy, so the total budget is about 95,000. The recipient has never held USDT, so the transfer needs about 131,000. The contract runs out of budget, the USDT stays put, the rented Energy is used up and the 3 TRX are burned. About 36,000 Energy (≈3.6 TRX at that price) was missing.

fee_limit is a ceiling, not a fee

Every contract call carries a fee_limit in sun. The network takes the smaller of (a) what your Energy plus TRX can pay for and (b) what fee_limit allows. A fee_limit set too low can cause OUT_OF_ENERGY even when you hold plenty of Energy. Raising fee_limit alone does not help if your Energy and TRX are not enough. Most wallets set it for you; some let you edit it.

How to check the TXID properly

  • Open the failed transfer in your wallet history and copy the transaction hash (TXID, 64 characters).
  • Paste it into TronScan's search. Look at the result code, Energy and Bandwidth consumed, TRX burned, and whether a USDT transfer actually happened.
  • Make sure the code really is OUT_OF_ENERGY. "FAILED" alone says nothing about the cause.
  • If TronScan has no record yet, wait. Do not create a new transfer before you know what happened to the first one.

What TronScan showsLikely causeWill more Energy help?
OUT_OF_ENERGYThe Energy budget ran outYes, together with enough TRX and a sane fee_limit
REVERTThe contract stopped on its own conditionNo, check the parameters / reason
OUT_OF_TIMECPU time limit or a protocol checkNo, read the exact error message
BANDWITH_ERROR / rejected before executionNot enough Bandwidth or TRX, or validation failedFix the stated cause first
Wallet error, no TXID at allThe transfer may never have reached the networkCheck the address history in the explorer
(BANDWITH_ERROR is the protocol's own spelling.)

What to fix before sending again

  • Confirm the USDT is still on your address.
  • Check what the address has now: available Energy, Bandwidth (600 free units per activated account per day, recovering gradually) and TRX.
  • If Energy was delegated to you, confirm it arrived and has not expired (look for the DelegateResource record).
  • Estimate for this exact recipient. An estimate for a different address can be off by a factor of two.
  • Cover the whole requirement: stake TRX, rent Energy, or keep enough TRX to burn for the gap.
  • Create a new transaction. A transaction that already failed cannot succeed by re-broadcasting it; TRON's error docs say to fix the cause and sign a new one.

Common traps
  • Renting Energy but paying from an exchange: Energy is delegated to the paying address, which is the exchange's, not yours.
  • Letting a short delegation expire before sending.
  • Wallet "pay fee in USDT" / gas-free modes that do not use the Energy on your address.
  • Treating every FAILED as an Energy problem. REVERT and wrong addresses are not fixed by Energy.

If you want a quick way to see how much Energy a transfer from your address is likely to need before you send, Tronilend has a free address checker: tronilend.com/check-address. It only needs the public address; no keys, no wallet connection.

Questions and corrections are welcome, especially if you have seen OUT_OF_ENERGY with an unusual fee_limit setup.

Disclosure: I'm posting on behalf of Tronilend, a TRON Energy rental service. Sources: FeeLimit & Energy cost, VM exception handling, Errors and debugging.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!