Can I send TRON energy from one wallet to another? We run an energy pool at Tronsell.io, so this question comes up every week. The confusion usually comes from one wrong assumption: that energy is something you can hold in your hand, like a token. It is not. It is a daily resource allowance tied to a specific address.
So can TRON energy actually be transferred between wallets? No. You cannot send TRON energy from one wallet to another the way you send TRX or USDT. Energy is not a token. It is a resource tied to a specific address, and it exists only after you stake TRX for that address.
What you can do is delegate energy. You stake TRX on your own address, then hand the energy that stake produced to another address for a set period. The receiving address can spend that energy, but it never owns it, and it can never pass it on to a third wallet.
The short answer
| Question | Answer |
| Can I send energy to another wallet like a token? | No. There is no “send energy” transfer. |
| Can another wallet use my energy? | Yes, but only through delegation. |
| Does the receiver own the energy? | No. It is borrowed and expires. |
| Can the receiver send the energy onward? | No. |
| Do I lose my TRX by delegating energy? | No. The TRX stays staked and stays yours. |
| Can I get the TRX back? | Yes, after you undelegate and wait 14 days. |
If your only goal is to make a USDT transfer cheaper, you do not need to move energy between wallets at all. You just need energy on the address that sends. That is far simpler than it sounds. For the wider cost picture, see How to Reduce TRON Transaction Fees.
Why energy is not a token
Every TRON address that stakes TRX receives two resources each day: energy and bandwidth. Energy pays for smart contract calls — a USDT transfer is one. Bandwidth pays for the raw size of the transaction. Both drive what a USDT transfer costs on every network. We break that cost down in USDT Transaction Fee: How Much It Costs on Every Network.
Those resources are calculated for an address, from that address’s own staked TRX. They are not balances sitting in a contract that you can move. TRON’s account model keeps TotalEnergyWeight and TotalNetWeight for the whole network, and divides the daily pool across all staked TRX. Every address’s share is recomputed from its own stake.
So there is no field in an address that says “energy: 65,000, transferable”. There is only “this address staked X TRX, therefore it may spend Y energy today”. Delegation is the one mechanism that lets a different address spend that Y.
How delegation actually works
This is the whole process, on-chain:
- You freeze TRX for energy. In TronLink, open Wallet → Resources → Energy → Freeze, choose the energy option, and confirm. Your TRX becomes staked, not spent. You can unstick it later.
- You delegate to a receiver. Open Wallet → Resources → Energy → Delegate, paste the receiver’s address, and enter either a TRX amount or an energy amount. Confirm the transaction.
- The chain records a DelegateResourceContract. This is a real transaction with a fee. It writes down four things: who delegated, who received, how much TRX was staked for it, and the lock period.
- The receiver’s energy allowance goes up immediately. No claim step. No acceptance step. The receiver does not have to be online or do anything.
- The receiver spends it. The next smart contract call from that address draws the delegated energy first, before touching its own TRX.
- The delegation expires. When the lock period ends, the energy returns to you. Unused energy is not saved up — it is gone.
One detail matters here more than any other, and it is the one people miss. You delegate a share of staked TRX, not a fixed number of energy units. When you enter an energy figure, the wallet works out the TRX you need to stake for it. That stake is what gets delegated. That is why the cost of “65,000 energy” keeps moving. It tracks the network-wide staked total, and that total never stands still.
What the receiver can and cannot do
The receiver can:
- use the delegated energy for its own transactions, including a USDT transfer
- keep using it for the whole lock period
The receiver cannot:
- move the energy to a third wallet
- sell it or convert it back to TRX
- keep it after the lock period ends
- use it for something unrelated to its own transactions
One more hard limit matters here. Delegated energy is spent only when that address actually makes a contract call. If the receiver does nothing all day, that day’s energy is simply lost. Energy does not accumulate, and it does not roll over to the next day.
What delegation costs
Delegating a resource costs a network fee. Delegating a resource is a normal TRON transaction, paid once, not per day. Your TRX is not burned — it stays staked, and you get it back after you undelegate.
Now compare that with making no preparation at all. Say the address has no energy and just fires off a USDT transfer. The system burns TRX directly. The burn follows the network energy price: 65,000 energy × 100 sun = 6,500,000 sun = 6.5 TRX. If the receiver has no USDT balance yet, the transfer must write a fresh balance. That needs roughly 130,000 energy = 13 TRX.
So you can pay a one-time fee to stake and delegate, or you can burn 6.5–13 TRX on every single transfer. The energy number itself shifts with transfer size, which is why How Much TRON Energy Do I Need to Send USDT? Why It Doubles is worth checking before you size a delegation.
| Path | Cost for one USDT transfer |
| Stake your own TRX, delegate energy | One-time network fee, then energy covers the transfer |
| No energy, no delegation | 6.5 TRX burned (13 TRX if the receiver has no USDT balance) |
| Rent energy from a provider | Market rate per energy unit, no TRX staked |
Why you cannot chain delegations
Many people land on the same idea: “I will receive energy delegated to me, then re-delegate it to my friend.” That does not work. The reason is in how the chain is built.
Energy is produced by staked TRX, and it is bound to the address that staked it. A receiver never owns staked TRX. It only gets a spending allowance, and that allowance cannot be delegated again. There is no stake in the receiver’s name to delegate.
So if you want to get energy to a friend, either stake your own TRX or rent from a platform that stakes on your behalf.
How to verify a delegation yourself
Do not take our word for it. Any delegation can be checked on-chain in about a minute.
- Open tronscan.org and search the receiver’s address.
- Open the Resources tab.
- You will see the address’s own staked energy and, listed separately, energy received from others, with the delegator address and the lock period.
- Cross-check the sender’s side at api.trongrid.io/wallet/getdelegatedresourcev2, which returns the raw delegation record for a pair of addresses.
If the receiver’s Resources tab shows energy that is not matched by its own staked TRX, that energy was delegated.
Delegating or renting: which one fits you
Choose by how often you transfer, not by which option sounds cheaper.
- You transfer often, and you have idle TRX. Stake it and delegate. You pay a fee only once.
- You transfer a few times a month. Renting energy is usually the better deal. You do not have to lock up TRX for 14 days, and you pay for the energy itself instead of buying and staking TRX. Rent TRON Energy: Pay 70-90% Less on USDT Transfers covers how the rental side works and what it costs. Once you have a few quotes in hand, How Do I Compare Different Energy Rental Quotes? shows what to check before you pay.
- You received energy and want to pass it on. You cannot. Either stake your own TRX or rent from a platform.
- You only need one transfer today. Burning TRX on that single transaction is the fastest option, and the only one that needs no setup at all.
Common mistakes
Trying to “send” energy. Use Delegate, inside the Resources panel. There is no send box for energy.
Delegating to an address that does not exist yet. A delegation to a brand-new address must create that account. That costs an extra 1 TRX (1,000,000 sun on-chain), carried by whoever initiates the transaction. Delegate to an address that is already active, unless you intend to pay for the creation.
Forgetting the 14-day wait. Undelegating does not release your TRX right away. TRON applies a 14-day waiting period to unstaking. Build that into your plan.
Setting a lock period beyond the cap. The maximum delegation lock is 864,000 blocks, about 30 days at roughly 3 seconds per block. You cannot lock longer in one go.
Assuming the receiver needs an approval step. It does not. Once the delegation transaction is confirmed, the energy is usable. If it is not showing, check the transaction status, not the receiver’s wallet.
FAQ
Is TRON energy the same as TRX?
No. TRX is the token you hold. Energy is a daily resource your staked TRX produces. You stake TRX to get energy, but energy is not TRX and cannot be traded for TRX directly.
Can I delegate to my own second wallet?
Yes. Delegation is not restricted to other people. Many people delegate from a cold storage address to a hot wallet they use daily.
Does the receiver need TRX to make the transfer?
No, if the delegated energy covers the contract call and the receiver’s free daily bandwidth covers the transaction size. TRC-20 transfers are roughly 350 bytes against a free allowance of 600 points per active address per day, so bandwidth is usually not the bottleneck.
What happens to unused energy?
It expires. Delegated energy has no carry-over. If the receiver does not transact, that day’s allowance is simply not used.
Can I cancel a delegation early?
Yes, before the lock period ends. The energy comes back after the network processes it. Your staked TRX still falls under the normal 14-day unstaking wait.
Can a delegation be reversed by the receiver?
No. Only the delegator can undelegate. The receiver cannot send the energy back or redirect it.
How much can I delegate per address?
There is no small per-address cap that ordinary users hit. The constraint is how much TRX you have staked. The one hard ceiling is the lock period, capped at 864,000 blocks.
Why did the cost of “65,000 energy” change since last month?
Because the delegation amount is priced in staked TRX. The network splits a fixed daily energy pool across all staked TRX. When the network-wide staked total rises, each staked TRX yields a little less energy, so more TRX is needed to produce the same energy figure. That is why any honest platform quotes you a rate with a date attached to it.
The one thing to remember
You cannot transfer TRON energy between wallets the way you transfer a token. You can delegate it, but delegation can only be done from the address that staked the TRX. The receiver can spend that energy, but it does not own it, cannot hand it to anyone else, and cannot keep it.
If you just want to make a USDT transfer cheaper, stop thinking about moving energy around. You only need energy on the address that sends.
Sources
- TRON Mainnet getchainparameters endpoint (api.trongrid.io) — energy price 100 sun; energy per staked TRX weight 180,000,000,000 / 18,728,842,417; network parameter count 80; account creation fee in system contract 1,000,000 sun; free bandwidth 600; unfreeze delay 14 days; maximum delegation lock 864,000 blocks; queried 2026-10-13.
- TRON Mainnet getaccountresource and getdelegatedresourcev2 endpoints (api.trongrid.io) — live energy weight and per-address resource fields used to confirm delegated versus self-staked energy; queried 2026-10-13.
- TronScan account resource view — independent sighting of the same energy price, energy weight and bandwidth figures against the API values above; checked 2026-10-13.
- TRON Mainnet getnowblock endpoint (api.trongrid.io) — block height 87,063,188 and block interval used to convert the 864,000-block lock cap into roughly 30 days; queried 2026-10-13.
- USDT TRC-20 energy requirement, ~65,000 units for a receiver with an existing USDT balance and ~130,000 units for a receiver with a zero balance — measured range from the transaction receipts we process through the Tronsell.io pool; last reviewed 2026-10-13.
Disclaimer
This article is general information, not financial advice. TRON network parameters are governed by on-chain votes and change without notice. The values above are dated 2026-10-13; re-check the chain before you rely on any figure in a live transaction.