Energy in TronLink, Trust Wallet and SafePal

Where the number lives, and what to do when it reads zero.

No wallet holds energy. The address does. Energy is a property of a TRON account in the network state, so every app that opens the same address sees the same balance. Moving from TronLink to Trust Wallet changes nothing about it. What changes is how clearly the app shows you the number.

Where the number is

TronLink. The resource block on the account screen, with bandwidth and energy counted separately. Energy delegated to you appears in that same counter, next to whatever you produced by staking.
Trust Wallet. TRON resources are barely surfaced. Read the address in a network explorer instead of trusting the app to tell you.
SafePal. On the account card, with nothing to switch on first.

The big TRX figure before you sign

When a wallet warns that a USDT transfer will cost several TRX, that number is not a fee going to anyone. It is the burn: the network pricing the energy you do not have and destroying TRX for it. At this moment it prices one such transfer at — TRX when the receiving side already holds USDT. Put energy on the address and the same screen quotes something far smaller, because only the bandwidth is left to pay for. The two resources and the two failure modes are set out on energy and bandwidth.

The fee limit on the same screen is a different thing again. It is a ceiling on what the wallet may spend, not a sum it will spend, and set below the real cost it cuts the transaction off on your own instruction: OUT_OF_ENERGY.

What the wallet cannot do for you

No wallet produces energy. It reports the balance, and TronLink additionally lets you stake TRX to make your own. Everything else on that screen is reporting rather than producing, which is why switching apps in search of cheaper transfers gets nobody anywhere.

Check that it actually landed

1. Open your address in a TRON explorer, not the wallet screen.
2. Read the energy line and compare it with what the transfer needs: 65,000 or 131,000.
3. Open the txid from the delivery. The delegation to your address is in the transaction itself.

Wallets cache. A balance that looks unchanged for a minute after delivery is usually the app being slow, and the explorer settles the argument.

Right address, not just the right wallet

One wallet app often holds several accounts, and energy sits on the exact address it was delegated to. The address that spends the energy is the one the USDT leaves from, so that is the address to name when ordering. A deposit address at an exchange belongs to the exchange, not to you, and energy sent there is spent by them.

When the hour ends

The delegation expires by itself. There is nothing to switch off, no approval to revoke and no allowance left standing. Anything unspent inside the hour simply goes unused, so several transfers in a row can run off one delivery if you send them while it lasts. That is worth knowing before you order: line the transfers up first, then take the energy, rather than buying an hour and spending half of it finding addresses.

Run out mid-session and the next transfer falls back to burning TRX, or fails outright: OUT_OF_ENERGY covers what that looks like. A fresh hour goes for —, so stopping to buy one costs less than pushing a single transfer through the expensive way.

Three things to check before you order

1. The address the USDT will leave from. Not the recipient, and not a different account inside the same app. The sender is the one that spends the energy.
2. Whether the receiving address has ever held USDT. That is what sets the amount, and it takes one look in an explorer: how much energy a transfer needs.
3. That your own address exists on chain. A wallet created five minutes ago and never funded is not an account yet.

A brand-new wallet will not take it

An address the network has never recorded cannot receive a delegation, because there is no account to delegate to yet. Send it something first: activating a TRON address explains what that costs and who pays.