Energy rental is unusual among crypto services in one respect: the safe way to rent TRX energy requires almost nothing from you. No transaction to sign, no contract to approve, no wallet to connect. You name an address, someone delegates energy to it, and it appears.

That property makes the category easy to secure and easy to fake. The legitimate flow is so undemanding that any provider asking for more is asking for something it does not need — which is exactly the gap that gets exploited.

This article covers the mechanics honestly, including where the real risks sit, which are not where most checklists put them.

First, what delegation actually is

When you rent TRX energy, the provider stakes its own TRX for energy and delegates that energy to your address. Delegation is a chain-level operation on the provider’s side. Nothing moves out of your wallet. Your private key is not involved. Your TRX balance is unchanged. Your address does not need to hold any TRX at all.

When you rent TRX energy, the energy arrives with an expiry. When the delegation window ends, the resource is reclaimed automatically and any unused energy is gone — it does not accumulate, and it is not refunded.

That is the entire mechanism behind every legitimate service that will rent TRX energy to you. It has one immediate consequence worth stating plainly: receiving energy is not something you do. It is something that happens to an address you nominate. There is no acceptance step.

The rule that prevents most losses

If you take one thing from this article, take this:

If a flow asks you to sign a transaction or approve a contract in order to receive energy, stop. That is not energy rental.

Every legitimate provider can delegate to any address without your cooperation, which is why the sequence to rent TRX energy has never needed a signature. A request for a signature, an approve, a wallet connection with write permissions, or a “claim” step is either a badly built product or a drain. From the outside the two look identical, and the outcome is the same for you.

The subtle version of this attack is well constructed. It presents a familiar interface, shows a plausible order summary, and asks for an approval “to authorise the delegation”. The approval is for USDT, with an amount that is either unlimited or far above the order value. Once granted, the allowance can be exercised at any time, by anyone holding it, without further interaction from you.

This is why the rule is absolute rather than a judgement call. You cannot evaluate a malicious approval by looking at the interface, and you do not need to — the legitimate product never asks.

The three failure modes that actually cost money

Ranked by observed frequency rather than by severity.

1. Paid, never delegated. The most common loss is not a hack. It is an off-chain payment to a provider that does not deliver. Because nothing is enforced on-chain, your only protection is the provider’s behaviour. This is why reputation is load-bearing in this category and why “we have a Telegram support channel” is not a control.

2. Approved something you should not have. Covered above. The damage is not limited to the order — an unlimited allowance persists after the order expires, after the provider disappears, and after you stop using the service.

3. Delegated to the wrong address. Human error, and increasingly address poisoning: an attacker sends a zero-value transfer from an address that shares the first and last characters of a counterparty you have paid before, so it appears in your history. You copy the wrong one. The energy lands on an address you do not control, and the transfer you funded fails.

Notice what is absent from that list: someone stealing your private key via a rental service. That does happen in this ecosystem, but through generic phishing rather than through the rental mechanism. Treating rental as inherently dangerous misallocates attention; treating it as inherently safe misallocates it worse.

Verifying that energy actually arrived

When you rent TRX energy, do not trust an order page. Read the account. Three values answer the whole question:

• Available energy on your address. If it is at or above your requirement, the delegation landed.
• Delegated-in energy, by source address. Confirms it came from the provider you paid, not from somewhere else.
• Expiry. Confirms you have the window you paid for, which matters more than the amount when your cadence is slower than the delegation window.

A practical habit: verify with a fresh read immediately before releasing any batch that depends on the energy. Not because providers routinely fail, but because the check is nearly free and it converts a payment failure into a delayed payment.

The specific reads and what each field means are set out in the guide to how renting TRX energy works end to end, including how expiry interacts with batch timing. This article is about not losing funds; that one is about not losing time.

What a legitimate flow looks like, step by step

Because the safe pattern for renting TRX energy is so minimal, it is worth spelling out what normal looks like. If a provider’s flow contains a step that is not here, that step is the thing to examine.

1. You supply an address. You generate it, or you use an existing one. You read it in full before pasting it anywhere.
2. You state a quantity in energy. Not “one transfer” — an energy amount, or a transfer count the provider converts using an energy assumption you can check.
3. You pay. Off-chain by invoice or on-chain by a plain TRX transfer. A plain transfer sends TRX; it grants nothing. There is no approval step in either case.
4. The provider stakes and delegates. This happens entirely on their side, from their address, using their TRX.
5. Energy appears on your address. You confirm by reading account resources. There is no claim, no swap, no receipt to sign.
6. The delegation expires. The energy is reclaimed automatically. There is nothing to cancel and nothing to unsubscribe from.

Six steps, zero signatures from you, zero contract approvals. That is the complete legitimate surface area of renting TRX energy.

Now consider the inverse — the shape of a flow that is not what it claims. It asks you to connect a wallet with write access. It presents a “claim energy” button. It requires an approve before the delegation “can be authorised”. It offers to “verify ownership” by having you sign a message that turns out to be a transaction. Each of those steps exists to obtain something the real product does not need, and the thing being obtained is access to your balance.

The distinction is not about how professional the interface looks. A drain can be better designed than a legitimate service, because design is cheap and the payoff is asymmetric. The distinction is entirely about whether your key is asked to do anything, and in the legitimate case the answer is no.

One caveat worth stating plainly: this rule protects you from malicious flows, not from unreliable providers. A provider can follow the correct pattern and still fail to delegate after you have paid. That risk is commercial rather than technical, and the only controls are counterparty selection, small first orders, and verifying delivery on chain before sending a large batch.

Separate the treasury from the spender

The highest-leverage structural change for most teams that rent TRX energy costs nothing and prevents the worst outcome.

Whenever you rent TRX energy, it must land on the address that signs transfers, which is a hot wallet with a key in memory. Your treasury is a cold address that should never sign anything automatically. If those are the same address, every compromise of the payout system is a compromise of the whole balance.

The correct shape is three layers:

Energy belongs on the hot wallet, and only on the hot wallet. It is a consumable, not an asset worth protecting in cold storage. The tempting mistake is to delegate energy to the treasury address “because that is where the funds are” — which pulls your cold address into the signing path for no benefit.

For anything above a few batches of working balance, put the hot wallet behind a multisig or a policy-controlled signer. This also changes the failure calculus on approvals: a compromised signing key in a single-key setup drains the wallet, while in a 2-of-3 it drains nothing.

Approval hygiene, if you have ever approved anything

Nothing about renting TRX energy creates an allowance, but if you have used DeFi on the same addresses you already have some outstanding. They are independent of any rental service and they outlive it.

Two habits close this off. First, review and revoke allowances periodically on any address that holds a balance — most wallets and several public tools list outstanding approvals per token and per spender. Second, never grant an unlimited allowance. A specific amount is nearly always sufficient, and it caps the damage at that amount.

On the spender side, treat any address that once held an approval as tainted even after revocation, and prefer a fresh address for new high-value flows. Address history is a record of who has tried what.

If you think you have been drained

Order of operations matters, and the wrong first move wastes the window.

1. Revoke approvals first, before anything else. An active allowance is a live faucet. Revoking stops ongoing loss even if the attacker still has other access.
2. Move remaining funds to a new address you generate yourself — not an address someone sent you, and not one copy-pasted from history.
3. Do not “recover” via any service that asks you to sign or to enter your seed phrase. Recovery scams target exactly this moment, and they arrive within minutes of a public incident.
4. Check whether an energy delegation was the vector by reviewing approvals and recent delegations. If it was not, look at what you signed in the preceding days rather than the preceding minutes.

Nothing in that list requires a provider’s cooperation, which is the point. If your recovery plan depends on a vendor responding, it is not a plan.

A short checklist before you rent TRX energy

• The provider delegates to an address you name, with no signature from you.
• You have confirmed the recipient address by reading it in full, not by matching first and last characters.
• Delegation is verified by reading account resources, not by the order page.
• Energy is delegated to the hot wallet, never to the treasury.
• You know the expiry, and it covers your batch window.
• No approval of any kind was granted during the process.
• Outstanding approvals on the sending address have been reviewed in the last 90 days.

None of this is sophisticated. The security posture of renting TRX energy is mostly a matter of refusing to do things you never needed to do — which is harder than it sounds, because interfaces are built to make extra steps feel like diligence. The provider that asks for one more confirmation is not being careful. It is asking you to lower your defences to match the appearance of theirs.

Why you need a checklist before you rent TRX energy

Almost every way people lose money renting TRX energy is a process failure, not a knowledge failure. The person who sized for the wrong recipient state knew that recipient state mattered. They just skipped the check at the moment it counted.

That is the case for a checklist. It is not for people who do not understand energy rental — it is for people who understand it well enough to be doing it repeatedly, under time pressure, with a batch waiting. Twelve checks, most of them under thirty seconds, that stand between an order and the four failure modes that cost real money.

The reference figures throughout: 64,285 energy to a recipient that already holds USDT, 130,285 to one that does not, 100 sun per unit if you burn TRX, and roughly 26 to 74 sun if you rent.

Before you rent TRX energy: checks 1 to 6

1. Confirm you control the sending address. Delegation only helps an address whose keys you hold. Exchange deposit addresses, custodial accounts and venue-managed wallets cannot consume delegated energy — the venue settles from its own ledger. If your flow routes through one of those, this whole exercise does not apply to you.

2. Classify every recipient as funded or empty. This is the highest-value check on the list. A recipient that already holds a USDT balance needs about 64,285 energy; one with no balance needs about 130,285, because the contract must create a new balance slot. Get this wrong and the transfer fails mid-execution regardless of how much you paid.

3. Compute energy from the classification, not from an average. Sum 64,285 per funded recipient and 130,285 per empty one. An average across a mixed batch will be wrong for both halves.

4. Add a 15–25% buffer. Contract state shifts and the dynamic energy factor is a network parameter, not a constant. Below 15% you will see intermittent failures; above 25% you are prepaying for energy that expires unused and returns nothing.

5. Set the duration from your refill cycle or batch window, plus half again. Delegated energy refills over roughly 24 hours, so a monthly term sized for one transfer a day covers a month of daily transfers. For a single batch, measure how long the batch actually takes and add 50% — the tail burning TRX after expiry costs two to three times the planned rate.

6. Check your TRX balance covers bandwidth. Renting energy does not cover bandwidth. Every account gets 600 free bytes per day, enough for exactly one transfer; past that you burn about 0.35 TRX per transfer at 1,000 sun per byte. A few TRX of headroom prevents a failure that has nothing to do with the energy you just bought.

At order time: checks 7 to 9

7. Write down the expected delivery deadline before you pay. Delegation usually confirms within a minute and sometimes takes several during congestion. Having a number in advance is what lets you distinguish “slow” from “not coming” without guessing.

8. Note the expiry timestamp at the moment of confirmation, not the moment of ordering. These differ, and the gap is time you paid for but cannot use. If a provider times duration from order placement, that is worth raising — on short rentals it is a material share of what you bought.

9. Do not queue any transfer until check 10 passes. This one sentence prevents the most common automated failure: a pipeline that orders energy and submits transactions in the same breath, so the head of every batch burns TRX.

After delegation: checks 10 to 12

10. Verify the energy in your wallet’s resource panel. Not the provider’s order page. That page reflects a database; the chain reflects reality, and they are not always the same. If the panel shows zero, ask for the delegation transaction hash and verify it on a block explorer yourself.

11. Confirm the expiry lands after your batch finishes. Compare the expiry timestamp from check 8 against your measured batch duration. If the margin is under 30 minutes, either extend or split the batch — the cost of a second order is trivial against a tail burning at 100 sun.

12. Log what you ordered against what you used. This is the check everyone skips and the only one that improves the next order. If you consistently use 78% of what you buy, your buffer is too large and you are paying for expired energy. If you consistently use 98%, it is too small and you are one variance event away from failures.

The rent TRX energy checklist on one page

Twelve rows. In practice, checks 2, 4, 5 and 10 are the four that prevent almost all of the money loss; the remainder are hygiene.

How each failure presents after you rent TRX energy

Knowing the symptom is what lets you find the failed check quickly, rather than re-reading your whole setup.

Where the numbers come from

Worth stating plainly, because the widely published figures are wrong. Energy is priced at 100 sun per unit by on-chain committee proposal #104, effective 29 August 2025, down from 210 sun. A USDT transfer consumes about 64,285 energy to a funded recipient and 130,285 to an empty one — not the 31,895 and 64,895 that most guides still quote, which predate TRON’s dynamic energy model. The USDT contract currently carries an energy factor of 34,000, the network maximum, roughly 3.4× base cost.

If your checklist is built on the old numbers, checks 3 and 4 will pass and the transfer will still fail. That is the one input worth re-verifying periodically rather than assuming.

Running this checklist when you rent TRX energy through an API

If you rent TRX energy through an API rather than an interface, most of these checks become code — and two of them change character entirely.

Check 9 becomes a state machine. A pipeline must be able to exist in the state “order placed, delegation unconfirmed” and refuse to advance. The common bug is ordering and submitting in the same function, with the confirmation check reduced to a sleep. Sleeps fail under congestion, which is precisely when you need the check.

Check 12 becomes telemetry. Log energy ordered, energy consumed, transfers attempted and transfers failed, per batch. Three ratios fall out of that: utilisation, failure rate, and effective cost per transfer. If utilisation sits above 95% you are under-buffered and about to see failures; below 75% you are prepaying for expired energy. Neither number is visible without logging, and both are worth more than any price negotiation.

Check 10 needs a timeout that fails loudly. Polling the resource balance is right, but polling forever is not. Pick a deadline, and when it passes, fail the batch and alert. A pipeline that waits indefinitely looks healthier than one that errors, and is more expensive.

Two implementation details worth stating because they are easy to get wrong. First, make order placement idempotent — a retried API call must not create a second delegation. Second, distinguish a timeout from a rejection in your error handling; treating them identically either double-orders or silently drops an order.

Walked through end to end on a 200-transfer batch, the twelve checks take about ninety seconds of human attention and a few hundred milliseconds of code. That is the entire cost of avoiding four of the five failure modes in this market.

Frequently asked questions

What should I check before I rent TRX energy?

Four things matter most: that you control the sending address, that each recipient is classified as holding USDT or not, that your energy order includes a 15–25% buffer, and that you verify the delegation on-chain before sending anything.

How much energy should one USDT transfer need?

64,285 to a recipient that already holds USDT, 130,285 to one with no balance. Add 15–25% buffer. Figures near 31,895 or 64,895 are outdated and will cause failures if used for sizing.

How do I verify that rented energy arrived?

Open your wallet’s resource panel and confirm the energy balance is non-zero. If it is not, request the delegation transaction hash from the provider and check it on a block explorer. An order status page is not evidence of delivery.

How long should I rent TRX energy for a single batch?

Measure how long the batch actually takes and add 50%. A batch that runs 40 minutes should have a two-hour window rather than a one-hour one — the extra cost is small, and the tail burning TRX after expiry is not.

Why does my transfer cost TRX even after I rent TRX energy?

Bandwidth. Renting covers contract execution only; transaction data is charged at 1,000 sun per byte, about 345 bytes per transfer, with 600 free bytes per account per day. Anything past that burns roughly 0.35 TRX per transfer.

Should I rent TRX energy in excess of what I need?

Slightly, yes — 15–25% over the computed requirement. Unused energy at expiry is lost, so this is a real cost, but it is a certain small one against a failure that costs a retry plus the wasted energy at the full burn rate.

How to use this

If you rent TRX energy on any kind of schedule, copy the twelve-row table into whatever your team already uses for operational runbooks. The point is not to follow it perfectly; the point is that when a transfer fails, you can point at a row instead of guessing.

If you run this checklist consistently for a month, one thing will happen: check 12 will tell you your real buffer requirement, and you will find you have been overbuying by a fifth. That is the cheapest saving on the list, and it only comes from logging.

For the underlying mechanics rather than the procedure — what energy is, why refills work the way they do, and the thirty questions that come up most often — the full set of answers on renting TRX energy is the place to start.

Rent TRX energy: why this page exists

Renting TRX energy sounds like a single action — pay, receive energy, send USDT — but almost every question people actually ask turns out to be about one of three things: what the real cost is, whether the arrangement is safe, and what to do when the timing goes wrong.

This page answers thirty of the questions people ask before they rent TRX energy for the first time, in the order they come up. The numbers are current as of late 2026 and each one is stated with its basis, so you can recheck it rather than trust it. Where the widely published figure is wrong, the answer says so.

Part 1: the basics

1. What does it actually mean to rent TRX energy?

It means another party delegates Energy to your wallet for a limited time. Energy on TRON is a network resource produced by staking TRX, and Stake 2.0 allows a staker to delegate it to any address. A rental platform aggregates delegated Energy from large stakers and resells it in small slices — typically 15 minutes, 1 hour, 1 day, 3 days or 30 days. You never hold TRX, never stake, and never touch the staking interface. The Energy simply appears in your wallet’s resource panel.

2. Why is it called TRX energy when I’m sending USDT?

Because Energy is a property of the TRON network, not of the token you are moving. TRX is the network’s native asset and the thing you stake; USDT is a TRC-20 contract that runs on top of it. Executing that contract consumes Energy, and the network prices Energy in TRX. So the resource is “TRX energy” even when the transfer is denominated in USDT.

3. Do I need TRX in my wallet to rent energy?

You need a small amount, but far less than for burning. Energy covers contract execution; it does not cover bandwidth, which is charged at 1,000 sun per byte. Every account gets 600 free bandwidth bytes per day — enough for exactly one transfer, since two need 690. Keep a few TRX in the wallet for bandwidth and for any energy shortfall, and you will avoid the most common avoidable failures.

4. Can I rent energy to an exchange deposit address?

No, and this trips people up constantly. You can technically delegate to any address, but a deposit address is controlled by the exchange, and the exchange settles withdrawals from its own internal ledger — it does not consume delegated energy on your behalf. If your flow routes through an exchange, you are limited to whatever energy product that exchange offers.

5. Is it different to rent TRX energy or buy it?

Yes, and the distinction matters. Buying energy usually means letting the network burn TRX at the protocol rate — currently 100 sun per unit, set by committee proposal #104, effective 29 August 2025. Renting means paying a third party for delegated energy, which typically clears between 26 and 74 sun per unit. Burning is the ceiling; renting is the market price below it.

6. Is renting energy allowed?

Yes. Delegation is a documented feature of Stake 2.0, not a workaround or a grey-market trick. What can go wrong is not the mechanism but the counterparty — a provider that takes payment and never delegates, or one that asks for your private key. No legitimate energy rental service needs custody of your keys.

Part 2: cost and pricing

7. How much does it cost to rent TRX energy?

Indicative pricing through late 2026 has run from about 26 sun per unit on large monthly orders up to 74 sun on small short-duration orders. Against the 100-sun burn rate, that is a discount of roughly 26% to 74%. Per transfer, renting usually lands somewhere between a quarter and two thirds of the burn cost. Treat any specific number — including these — as a snapshot, not a rate.

8. Why is renting cheaper than burning TRX?

Because stakers hold Energy they cannot otherwise monetise. A staker with surplus capacity has idle inventory; delegation lets them sell it. Competition between providers pushes the price toward their marginal cost rather than the protocol’s burn rate, and the gap between the two is the rental market’s entire reason for existing.

9. How much energy does one USDT transfer need?

Approximately 64,285 Energy if the recipient already holds a USDT balance, and approximately 130,285 Energy if they do not — roughly double, because the token contract has to create a new balance slot for that address. These are measured from confirmed on-chain receipts in 2026, not the older published estimates.

10. Why do so many guides say 31,895 energy?

Because they are repeating a figure that is roughly two years stale. That number, and the 64,895 that goes with it, predates TRON’s dynamic energy model, which adds a surcharge to heavily used contracts. The USDT contract currently carries an energy factor of 34,000 — the network maximum, about 3.4× base cost. If you budget off 31,895, your estimate is wrong by more than half.

11. Is it cheaper to rent TRX energy for longer?

Cheaper per unit, yes. Cheaper in total, only if you use it. A 30-day rental costs less per energy unit than a 1-hour rental because the provider’s revenue is more certain, but delegated Energy refills over roughly 24 hours — so a monthly plan sized for one transfer a day genuinely covers 30 transfers. A monthly plan bought for a single transfer wastes money.

12. How many transfers will one rental cover?

It depends on duration and sizing. Energy regenerates, so a 30-day rental sized at 64,285 Energy covers one transfer per day for the month — 30 transfers, not one. A 1-hour rental covers one transfer. The governing rule is that your energy balance refills over about a day, so size for your daily volume rather than your total volume.

13. How do I calculate how much TRX energy to rent?

Multiply transfers per day by the energy per transfer, using the correct figure for each recipient — 64,285 or 130,285, not an average. Add a 15–25% buffer for variance, then match the duration to your refill cycle. Example: 20 transfers a day to funded recipients is 1,285,700 Energy, so order about 1.54 million on a monthly term with a 20% buffer.

Part 3: mechanics and timing

14. How long after I rent TRX energy does delegation arrive?

Usually under a minute, because delegation is a single on-chain transaction. During network congestion it can take longer. Always confirm the energy balance in your wallet’s resource panel before sending — an order status page saying “completed” is not proof that the delegation landed.

15. What happens when the rental expires?

Delegation is withdrawn and the Energy returns to the provider. Any transfer after that point reverts to burning TRX at 100 sun per unit. There is no grace period and no automatic renewal, so if a batch is scheduled near the expiry time, renew first.

16. Can I extend a rental before it expires?

Usually yes — most platforms let you place a new order that stacks on top of the existing delegation. What you generally cannot do is modify an existing order. Check whether the platform extends or replaces, because replacing can briefly leave you with no energy between delegations.

17. Does unused energy carry over or get refunded?

No. Energy is delegated for a fixed window; whatever you do not consume at expiry goes back to the provider. There is no refund and no carry-forward. This is why sizing matters more than buying a comfortable margin “just in case” — overbuying is a certain loss, whereas underbuying is a possible one.

18. Can I rent TRX energy for someone else’s address?

Yes, if they control the keys to that address. This is common for businesses funding an employee wallet or a partner’s operations. It does not work for custodial addresses, where the venue controls the keys and manages its own resources.

19. If I rent TRX energy, is bandwidth covered too?

No, and this is the omission that makes many “90% savings” claims wrong. Renting covers Energy only. Bandwidth is charged separately at 1,000 sun per byte, about 345 bytes per TRC-20 transfer, with 600 free bytes per account per day. At high volume, bandwidth is a real line item that survives your energy savings untouched.

Part 4: safety and scams

20. Is renting TRX energy safe?

The mechanism is safe; the counterparty risk is real. Delegation is a standard network feature and the transaction is visible on-chain. The risks are operational: paying for delegation that never arrives, sizing a rental that expires mid-batch, or dealing with a provider who disappears. Our guide to the two ways people lose money renting energy covers these in detail.

21. What do the common scams look like?

Three patterns dominate. A provider that collects payment and never delegates, leaving you with no recourse. A “support agent” who offers to fix a failed order in exchange for your private key or seed phrase. And a platform that requires you to import your wallet into its interface, which is simply key theft with extra steps. If any of these appear, stop.

22. Do I have to give my private key to rent energy?

No. Never. Renting requires one thing from you: the address you want energy delegated to. That is a public address, not a secret. Any service asking for a private key, seed phrase or wallet import to receive energy is either compromised or fraudulent.

23. What if I pay and the energy never arrives?

Check the on-chain delegation first — it may simply be delayed. If there is genuinely no delegation after a reasonable wait, you have a support dispute, not a technical one, and your leverage depends entirely on how you paid. This is the practical argument for using established platforms with visible delegation transaction hashes rather than the cheapest quote on a marketplace you have not heard of.

24. Can a provider revoke TRX energy before the rental ends?

Technically the delegator can undelegate at any time, but doing so would be self-defeating for a business that sells time-based rentals. What you should confirm is the platform’s stated policy, and prefer providers where the order terms specify a fixed window. Treat a very cheap quote from an unknown provider as a signal to check that term.

25. Is it risky to rent TRX energy from a small provider?

Smaller providers are not inherently unsafe, but they carry more of two specific risks: inventory risk, meaning they may not have the energy available exactly when you need it, and continuity risk, meaning they may not be around for your next order. For a one-off transfer these are minor. For an operation that depends on daily settlement, use a provider with provable inventory and an API.

Part 5: troubleshooting

26. I rented energy but still got OUT_OF_ENERGY. Why?

The most likely cause is a recipient with no USDT balance. If you sized for 64,285 Energy and the transfer needed 130,285, it fails regardless of the rental. Second most likely: the delegation had not confirmed when you submitted. Third: the rental expired between ordering and sending. Our guide to avoiding OUT_OF_ENERGY errors walks through the diagnosis.

27. My transfer failed — did I lose the energy anyway?

Often yes, at least partially. A transaction that runs out of energy mid-execution may still consume what it used before failing, and you must buy more to retry. This is why underbuying is more expensive than buffering: the buffer costs a little for certain, while a failure costs unpredictably.

28. Energy is showing, but the transfer still burned TRX. Why?

Almost always bandwidth. Energy and bandwidth are separate resources and a transfer consumes both. If your daily 600 free bytes are used up, the overflow burns TRX at 1,000 sun per byte — roughly 0.35 TRX per transfer — even with a full energy balance.

29. The order says complete but my wallet shows zero energy.

Check the wallet’s resource panel rather than its main balance, and confirm you are looking at the same network and address you ordered for. If the panel still shows zero, look for the delegation transaction hash — a legitimate platform can show you one. No hash and no energy means you have not received anything, whatever the order page says.

30. Should I rent TRX energy or stake for long-term use?

Rent, unless you already hold a large TRX position. Staking looks free because no fee leaves your wallet, but covering one 64,285-Energy transfer per day requires roughly 6,700 TRX staked — around $2,200 — locked for 14 days of unbonding if you want out. If you already hold TRX as inventory, staking captures the yield yourself and beats renting. If you would have to buy TRX to do it, you are taking a directional position to save a fee, which is a different decision.

The five answers that matter most

If you remember nothing else from these thirty questions about renting TRX energy, remember these.

A USDT transfer needs 64,285 Energy, or 130,285 to a new recipient. Not 31,895. The dynamic energy model changed this and most guides have not caught up.

Rental clears below the 100-sun burn rate, typically 26 to 74 sun. The discount is structural, not promotional, and it varies enough that how you buy matters as much as whether you buy.

Energy refills, so size by duration. A monthly rental covers a month of daily transfers, not one transfer. Buying per transfer is the most expensive habit in this market.

Bandwidth is not included. 600 free bytes a day covers one transfer; beyond that you burn TRX regardless of how much energy you rented.

Verify the delegation on-chain before sending. An order status is not proof. This single habit prevents the most expensive class of mistake in energy rental.

If you want the operational walkthrough rather than the questions, start with how to rent TRON energy step by step, and if you would rather compare staking properly, this staking walkthrough including the 14-day unbonding covers what that commitment actually costs.

Most people meet wallet import for the first time assuming it only matters when a wallet has broken. It is useful in a much wider set of situations. That includes a new phone, a factory reset, an app reinstalled and opened to an empty wallet, or simply wanting to manage the same TRON address from a second wallet.

Put simply, the wallet itself stays on-chain the whole time. What disappears is the record inside the app on your phone. An import does not create a new wallet. It hands the key you already hold to another wallet app, and that app takes over access to it.

Before you start, have your backup ready: a recovery phrase, a private key, or a keystore file plus the password you set for it. Any one of the three will do. There is nothing else to arrange. You do not need TRX, the import itself needs no network connection, and nobody has to approve it.

The whole process is short: find your backup, paste it into the wallet app, and check the address before you send anything. This guide covers TronLink first, then Trust Wallet. If the import succeeds but the balance looks wrong, the last section lists the usual things to check.

An import moves nothing on-chain

Your TRX and your USDT do not move during an import. They sit on the TRON chain and belong to one wallet address. The only thing that changes is which app on your phone holds the signing permission for that address.

So the same set of keys, imported into two wallet apps, always produces the same address. No transfer runs, no fee is charged, and there is no block confirmation to wait for.

This also means an import can be repeated as many times as you like. It does not copy your assets, and there is no such thing as one copy spending the money first.

Why the same 12 words give you a T address, not a 0x address

This is the point that explains a situation many people run into: the import reports success, and the wallet page shows nothing.

A recovery phrase is not a single private key. It works as a seed that grows a whole tree of keys. Each chain reads a different branch of that tree. TRON uses coin type 195, so the standard derivation path to your first TRON address is m/44’/195’/0’/0/0. Ethereum uses coin type 60.

The same phrase on a different branch gives a completely different private key and address. That is why one set of words produces a 0x address in an EVM wallet and a T address in a TRON wallet. The two addresses have no link between them.

If you restore the phrase into a wallet without TRON support, the balance appears to vanish. The assets are still there. That wallet simply never reads the 195 branch. Import the same phrase into TronLink or Trust Wallet and the T address and its assets come back as normal.

The number at the end of the derivation path is a counter. TronLink can derive several wallet addresses from one phrase, and they sit at paths like /0/1 and /0/2. Trust Wallet reads /0/0 by default. Remember this line, because it is where most balance mismatches start.

Check which backup you hold

Three kinds exist, and each behaves differently after the import.

TronLink takes all three. Trust Wallet takes the phrase and the private key, and its own help centre documents only those two — there is no keystore import.

If the wallet was created in TronLink, the phrase and the keystore both sit behind your wallet password, on the wallet’s backup page. If it was created in Trust Wallet, the phrase is behind your PIN, under the wallet name in the three-dot menu.

Copy the backup onto paper now. Both apps ask you to type it in full, and a screenshot on the same phone is not a backup. We suggest two copies, kept in separate places.

Step 1 — Import into TronLink

In the app:

1. Open TronLink. On a fresh install, tap Import Wallet at the bottom of the welcome screen.
2. If you already have a wallet, open the wallet list from the name at the top, tap Add Wallet, then Import Wallet.
3. Paste the phrase, private key or keystore into the single input box. The page reads the format for you.
4. Tap Next, scroll down, and fill in a wallet name and a password.
5. Tap the button at the bottom of the page and wait for the wallet to open.

In the browser extension:

1. Click the TronLink icon. On the welcome screen choose Import Wallet. If an account already exists, unlock first, then open Add Wallet → Import Wallet.
2. Paste the private key. It must be a 64-character hexadecimal string.
3. Tap Next. Give the account a name of 2 to 14 characters.
4. Set the password if this is your first account here. It needs at least 8 characters, with upper case, lower case and a digit.
5. In the Select Network window, choose TRON, then confirm the import.
6. Check that the name and the address on the home screen match the wallet you meant to bring in.

When an import fails, we check the string length first: 64 characters, no spaces.

That password only unlocks the copy on this device. Forgetting it does not lose funds — import the backup again and set a new one.

Step 2 — Import into Trust Wallet

Trust Wallet is a multi-coin app, so the phrase route brings the whole wallet. The private key route brings one chain only, and it works on mobile only. The browser extension does not accept private keys.

With the phrase:

1. Open Trust Wallet and go to Settings (the gear icon).
2. Tap Wallets, then the + icon in the top right.
3. Choose Add existing wallet, then Secret phrase.
4. Choose Multi-coin Wallet if you want every chain, or single coin if you want TRON alone.
5. Type the 12 or 24 words in the exact order you wrote them down, then tap Import.
6. Open TRON in the coin list and confirm the address.

With the private key:

1. Go to Settings → Wallets → + → Add existing wallet.
2. Pick TRON from the network list. Pick the wrong network and you import a different wallet.
3. Tap Private key, paste the 64-character string, and name the wallet.
4. Tap Restore wallet.

On a fresh install the entry point is Get started → Add existing wallet, and steps 2 to 4 are the same.

Check the address after the import

A TRON address starts with the letter T and runs 34 characters. Before you send anything, compare the first four and the last four characters of the new address against the address in the old wallet.

Two wallet apps sharing one set of keys is normal, and neither one can change what the other sees on-chain. The trap sits deeper: if you imported a different backup, the empty address on screen is one you have never used.

I do it this way myself: send a small test amount from the new wallet, confirm it arrives, then touch the larger balance in the old one. The test usually costs less than 1 TRX and settles the question in a minute. If you have not sent from this app before, the steps in how to send USDT on TRON are the ones the real transfer will follow.

Four cases where a successful import still looks wrong

Four causes cover almost every case.

You landed on a different derived address. One phrase can derive several independent keys. If your assets sit at /0/1 in TronLink while Trust Wallet loads /0/0 by default, the balance will be empty. Do not conclude that the assets are gone; check the address index first.

The token is not switched on. Trust Wallet hides some tokens until you add them manually. A normal TRX balance with no TRC-20 tokens in sight is common. To add USDT, use this contract address: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. A different contract address is a different token.

You imported an address you had already emptied. If the backup belongs to an old test wallet, an empty result is the correct one.

The USDT is visible but cannot be sent. Seeing a balance and spending it are two different things. Sending USDT consumes energy, and a wallet holding USDT without TRX has no energy to spend. When the receiving address already holds USDT, one transfer costs about 65,000 energy; when it holds none, about 130,000. Energy is burned at 100 SUN per unit, and 1 TRX equals 1,000,000 SUN, which works out to roughly 6.5 TRX and 13.0 TRX. The arithmetic behind those two figures is set out in the energy cost of a USDT transfer.

That last one is the only case of the four that costs you money. Renting TRON energy costs less than burning TRX, and a rental needs nothing but your public T address — no phrase, no key, no wallet connection. That is what we do at Tronsell.io.

Can one wallet live in two apps at once?

Yes. Both apps keep their own copy of the same keys, and both can sign. A transfer sent from either app reaches the chain within seconds, and the other app shows it after the next refresh.

We would keep the old app installed until the new one has signed at least one transaction, then decide whether to remove it. Uninstalling an app does not delete the wallet. The backup is what keeps the wallet alive, and that backup is yours alone.

One warning worth stating plainly, because it is where this goes wrong: these two apps only ask for your recovery phrase or private key inside their own import screen. Any website, bot or support agent that asks for them in private is stealing your assets.

FAQ

Do I need TRX to import a wallet? 

No. Importing is a local action, and the network never sees it. You only need TRX, or delegated energy, when you send.

Is importing the same as creating a new wallet? 

No. A new wallet gets a new key and a new address. An import reuses an old key, so the address is the one you already had.

Can I import by private key into Trust Wallet on a computer? 

No. Trust Wallet supports private key import in the mobile app only, and only for one chain at a time.

The app says my phrase is invalid. What now? 

Check word order and spelling first, then the count. TronLink expects 12 or 24 English words. One wrong word gives a different address or an error, and neither is recoverable by trying again.

I lost the phrase and the key. Can support restore it? 

No. There is no reset on a self-custody wallet. A service that offers to recover it is a scam, and so is one that asks for the phrase to “verify” it.

Sources

1. TronLink Help Center, “How to import a wallet” (entry points on the welcome screen and on the Add Wallet page; a single input box reads a phrase, a private key or a keystore automatically), checked October 2026.
2. TronLink Help Center, “How to import an account in the TronLink browser extension” (private key is 64 hexadecimal characters; account name 2 to 14 characters; password at least 8 characters mixing upper case, lower case and a digit; TRON selected in the Select Network window; phrase is 12 or 24 English words).
3. Trust Wallet Support, “How to Import a Wallet Using a Secret Phrase on Trust Wallet” (Settings → Wallets → + → Add existing wallet → Secret phrase → Multi-coin Wallet → Import), checked October 2026.
4. Trust Wallet Support, “How to Import a Wallet via Private Key on Trust Wallet” (mobile app only, not the browser extension; single-chain wallets only; Settings → Wallets → + → Add existing wallet → select network → Private key → Restore wallet).
5. Trust Wallet Support, “The Lifecycle of a Seed Phrase in Trust Wallet” (some tokens need manual addition through the token search feature before they appear).
6. ChainGateway, “What Is a TRC20 Address?” (TRON coin type 195 and the standard first-address path m/44’/195’/0’/0/0; Ethereum coin type 60; a T address is 34 characters).
7. TRON Developer Documentation, “Wallet management” (default derivation path m/44’/195’/0’/0/0; linked accounts at /0/1 and /0/2).
8. TRON chain parameters, checked with /wallet/getchainparameters, October 2026 (energy price 100 SUN, the figure the TRX conversions above rest on).
9. Tronsell.io on-chain measurements plus the prevailing industry figures, 2026 (USDT TRC-20 transfer at 65,000 / 130,000 energy; 1 TRX is 1,000,000 SUN, so 100 SUN per unit gives 6.5 / 13.0 TRX).
10. TRONSCAN token page, checked October 2026 (USDT TRC-20 contract address TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t).

Disclaimer

This guide describes wallet software that changes often. Menu labels may differ between versions and platforms. Nothing here is financial advice. Keep your recovery phrase and private key offline, and test any migration with a small amount before you move the rest.