How to Rent TRON Energy for a New TRON Wallet Address

Since I started in operations at a TRON energy rental platform, our support desk has received this kind of question almost every week: a user sends USDT into a brand-new wallet, but the money cannot be moved out, and the energy they rented ahead of time never arrives.

The root cause is this: a brand-new wallet address that has never had a transaction does not exist on the TRON blockchain, so it cannot receive an energy delegation. TRON does not create an account automatically. A TRX transfer is what triggers address activation, and that transaction formally creates the account on chain. Only once activation is complete can an energy delegation take effect.

Below I will explain the reason in detail and walk you through how to activate the address. At the end I go through, one by one, the causes that still burn TRX even after a rental has already taken effect.

Why a new address still cannot receive rented energy

Your wallet can generate an address in a second. But until that address first receives TRX, the chain does not know it exists. The two states look exactly the same in the wallet interface, yet their behaviour on the blockchain is completely different.

In your wallet, you hold a private key and a T-address, and you can receive USDT.

On chain it is another matter: only after the account is created on chain can it sign transfers, hold resources, and accept an energy delegation.

We verified this with our own node today. We constructed a valid T-address that had never received any funds, and the node returned {} for it. No account record means no resources at all, and nowhere to attach energy. If you want the fuller picture of what energy is and what it pays for, we cover it in What Is TRON Energy?.

This is why renting the energy first cannot work. A delegation names one receiving address, and the network requires that receiver to be an activated account. Placing a rental order for an address the chain has never seen leaves the delegation nowhere to land.

The misconception usually sits on the asset side: USDT can still be sent to an address the chain has not yet created. A token balance is recorded and held independently by the USDT contract — nothing more than a row inside that contract. So a new wallet can successfully receive and hold USDT, yet cannot move that money out.

Activate the address with a first TRX transfer

Send a small amount of TRX to the new address from a wallet you control. Two TRX is comfortable. Here is what that transfer costs and who pays for it.

• The chain burns 1 TRX as a one-time account creation fee. It is charged to the sender of the first transfer, not to the new address.
• If the sending wallet holds no staked or delegated bandwidth, the chain burns a further 0.1 TRX in place of bandwidth. The 600 free points a day cannot create an account. Those 600 points are a fixed daily allowance, and we break it down in What Is TRON Bandwidth?.
• Rented energy cannot do this job. A plain TRX transfer uses bandwidth, and never energy.
• The account record appears on the next block or two. TRON produces a block about every 3 seconds.

Rent the energy to that same address

You do not need to connect a wallet, nor do you need to grant any authorization. A platform only needs one piece of information from you: the public address you will use to initiate the USDT transfer — that is your new wallet address, not the recipient’s address.

1. Enter the new address as the delivery address. This is the field people get wrong. The energy has to sit on the address that signs the transfer.
2. Pick the amount, 65,000 or 130,000. The rule for choosing is in the next section.
3. Pick a window. A per-transfer package covers a single send, and longer coverage runs up to about 30 days, capped by the chain at 864,000 blocks.
4. Pay from a wallet that already holds funds. A wallet holding only USDT cannot pay this fee, because sending anything out needs energy or TRX, and it has neither.
5. Wait a few seconds. A delegation usually lands on the first or second block after your payment confirms.

Never hand your private key or seed phrase to a rental platform, whoever it is.

How much energy to order

The wallet receiving the USDT	Energy to order	Burned instead, if you send with no energy
Already holds USDT	65,000	6.5 TRX
USDT balance is zero right now	130,000	13.0 TRX

How much energy a transfer needs depends on the receiving wallet’s USDT balance, not on how old either address is. A new address sending to someone who already holds USDT falls into the cheaper row. Conversely, an address that has been in use for years but sits at zero today is charged the higher figure. For the detailed explanation and the calculation method, see our other article, How Much TRON Energy Do I Need to Send USDT.

How much TRX you burn when sending with no energy comes down to the price of energy. One unit of energy costs 100 sun, and 1 TRX equals 1,000,000 sun. So 65,000 units come to 6.5 TRX and 130,000 units come to 13 TRX.

Renting is cheaper than that. In a one-hour price survey across 18 platforms, quotes ranged from 26 to 74 sun, with an average near 49. Across the wider market range of 20 to 75 sun, renting is 25% to 80% cheaper than burning. One rule is worth remembering: 100 sun is the burn price, so any rental quoted above 100 sun is not worth buying.

The energy a transfer needs is not fixed either. Each contract has its own energy factor. A heavily used, frequently called contract recalculates its factor every 6 hours. TRON’s governance mechanism caps the surcharge factor at 3.4, which can raise the fee to as much as 4.4 times the base cost. That means the same USDT transfer, executed later in the day, may need more energy than it does in the morning.

Check the energy arrived before you send

Refresh the wallet first. A panel left open can still show zero even after the energy is already on chain.

Then read two numbers: the energy limit and the energy used. What actually pays for your transfer is the difference between them, never the limit on its own. That limit also includes the energy delegated to you.

The figure that arrives will not match exactly the round number you rented. In our own checks, a nominal 65,000 order read 64,485 on chain, and nominal 130,000 orders read 131,008 and 131,000. That is normal. The platform stakes and locks TRX, then hands you the energy that TRX produces. On 24 September 2026 the network ratio was 9.52 energy per staked TRX, so a 65,000 order means roughly 6,830 TRX locked. Whenever the network’s total stake changes, this ratio moves with it.

If you would rather read the raw numbers, any TRON node returns them straight from a browser address bar:https://api.trongrid.io/wallet/getaccountresource?address=<YOUR_T_ADDRESS>&visible=true

In Tronscan, the same figures sit in the Resources area of the account page.

If the transfer still burns TRX

Almost every case we see comes down to one of the following.

1. The energy is on another address. It sits on the address you named when you placed the order. A transfer signed by a different account draws on that account’s own resources instead.
2. The energy has already been spent. Rented energy is a 24-hour quota on one address, not a ticket for a single transfer. A batch script, an approval, or a colleague on the same wallet all draw on the same limit.
3. What ran short was bandwidth, not energy. A TRC-20 transfer is about 345 bytes, and the 600 free points a day cover only one of them. Once the quota is used up, those bytes burn at 1,000 sun each, about 0.345 TRX per transfer. Adding more energy will not fix this one.

If you want the specific fixes, see our detailed article on why TRX is still burned after renting energy, Why Is TRON Still Burning TRX After Renting Energy? Causes and Fixes, which explains how to resolve each one.

FAQ

Do I have to activate the address before I rent energy for it? 

Yes. The receiver of a delegation must be an activated account. Until the first TRX lands, there is no record to attach the energy to.

Can rented energy activate a new wallet? 

No. Activation happens through a TRX transfer, and a plain TRX transfer uses bandwidth only. Energy pays for contract calls such as a USDT transfer. It cannot create an account, and it cannot pay the 1 TRX creation fee.

Should the energy go to my address or to the wallet I am paying? 

To your own sending address. Energy is charged to the address that signs the transaction. If the recipient’s address goes in the delivery field, your own send is the one that burns TRX.

How long does the energy last? 

One order is locked for the period you choose, up to about 30 days on mainnet. Inside that window the energy refills over a rolling 24 hours, so a 65,000 order covers roughly one USDT transfer a day. Unused energy is not refunded.

Why does my wallet show 64,485 instead of 65,000? 

Because the energy comes from TRX the platform locked, converted at the network ratio of about 9.52 energy per staked TRX. A few percent either way is normal, not a shortfall.

Sources

1. TRON Developer Hub, Resource Model (bandwidth and energy mechanics; the 600 free bandwidth per rolling 24 hours; charging order).
2. TRON Developer Hub, Accounts and keys (an address exists locally before activation and cannot be queried until activated; 1 TRX creation fee; 0.1 TRX burned in place of bandwidth; TRC-20 balances are not held in the account object).
3. TRON Developer Hub, Bandwidth and Energy (delegation through DelegateResourceContract; the receiving account uses the energy without staking; 24-hour recovery window).
4. TRON Developer Hub, Paying for resources & Energy sharing (burn rates of 1,000 sun per byte and 100 sun per energy; dynamic energy model, maximum factor 34,000, up to 4.4 times the base cost).
5. TRON protocol documentation, DelegateResource (verbatim validation errors, including Account[] not exists for a receiver the chain holds no record of).
6. TRON chain parameters, read through /wallet/getchainparameters, 24 September 2026 (energy 100 sun; free bandwidth 600; 1,000 sun per excess byte; 6-hour maintenance interval, which is where the 6-hour window above comes from; creation fee 1,000,000 sun plus 0.1 TRX when bandwidth is short; delegation lock cap 864,000 blocks; dynamic energy max factor 34,000).
7. Network energy ratio through /wallet/getaccountresource, 24 September 2026 (180,000,000,000 divided by 18,906,461,882 = 9.52 energy per staked TRX, the rate behind the 6,830 TRX figure; EnergyLimit is documented as staked energy only, so its inclusion of delegated energy is our own measurement).
8. Tronsell.io node probe, 24 September 2026 (getaccountresource and getaccount both return {} for a valid address that has never received anything).
9. Tronsell.io on-chain measurement, September 2026 (one USDT transfer charges 345 bandwidth and about 64,300 energy, which is where the 345-byte figure above comes from; a plain TRX transfer charges 267).
10. Tronsell.io on-chain measurement, September 2026 (delivered energy: 64,485 for a 65,000 order, 131,008 and 131,000 for 130,000 orders; addresses taken from ordinary USDT transfer activity).
11. Tronsell.io energy rental price survey, 18 platforms, 1-hour orders, September 2026 (lowest 26 sun, average about 49 sun, highest 74 sun, against the 100 sun burn price).
12. TRON energy rental platform documentation, Tronsell.io, on the delegation flow (no wallet connection, no token approval, no private key or seed phrase; unused energy is not refunded).

This article is a general guide to TRON energy rental on a new address. On-chain parameters and platform interfaces change over time, so confirm the current values on chain before a large payment.