The three routes
| Burn TRX | Stake TRX | Rent | |
|---|---|---|---|
| Capital required | None | High, and locked | None |
| Lock-up | None | 14 days to unstake | None |
| Cost per transfer | Highest | Lowest at scale | Low, pay per use |
| Setup | None | Stake, then delegate | Order and receive |
| Good for | One-off transfers | Constant high volume | Everything in between |
Burning TRX
Do nothing, and the network converts TRX into the Energy your transaction needs and burns it. The rate is a governance parameter, getEnergyFee, currently 100 sun per Energy — about 0.0001 TRX.
That puts a routine USDT transfer at roughly 6.4 TRX and a transfer to a first-time recipient at roughly 13 TRX. It requires no preparation whatsoever, which is exactly why it is the default and exactly why it is the most expensive option per transfer.
Governance can and does change that rate. It has been lowered by vote more than once and has stood several times higher than it is today, so treat any figure — including this one — as something to verify rather than assume.
Staking TRX
Stake TRX and the network grants Energy in proportion to your stake and to total network staking. The Energy regenerates roughly every 24 hours, so a stake large enough for your daily volume produces that volume every day at no marginal cost.
Two things make it a heavier commitment than it first appears:
- The capital is substantial. Covering a few USDT transfers a day takes a meaningful TRX position, and that TRX is exposed to price movement the entire time.
- Unstaking takes 14 days. The capital is not merely allocated, it is unavailable, and if you need it during those two weeks you cannot have it.
- Your Energy yield moves with total network staking. Stake more elsewhere in the network and your share falls, without you doing anything.
Staking wins clearly at constant high volume — an exchange, a payment processor, a busy payout system. Below that, you are buying a fixed asset to solve a variable problem.
Renting
Renting borrows someone else's staked Energy. They hold the TRX and carry the lock-up; you pay for a delegation to your address for a fixed period, and it is withdrawn automatically when the period ends.
- No capital position and no 14-day lock-up. You pay for what you use, when you use it.
- It is a delegation, not a transfer: the delegated resource gives the provider no rights over your funds, and your keys never leave your wallet.
- It is priced well below the network's burn rate, because the provider is reselling regenerating Energy from staked TRX rather than destroying it.
The trade-off is timing. A rental runs for a fixed window, so if you rent and then sign an hour later, the delegation may already be gone. Broadcast promptly, or check the delegation before you sign.
What a delegation actually is
Renting sounds like it should involve trusting someone with your wallet. It does not, and the reason is worth understanding, because it is the difference between a resource service and a custodian.
Under TRON's Stake 2.0 mechanism, an address that has staked TRX can delegate the resulting Energy or Bandwidth to another address. The stake stays with the owner. What moves is the right to consume the resource, and only that.
- The provider never receives your keys, and delegation grants no authority over your balances.
- You continue to sign and broadcast your own transactions; the provider is not a party to them.
- The delegation is a public on-chain record. Open your address in TronScan and you can see exactly what was delegated, by whom and when.
- When the term ends, the delegation is withdrawn automatically. Nothing of yours is touched.
This is why the safety question has a concrete answer rather than a reassurance: the protocol makes it structurally impossible for delegated resources to move your funds. Verify it yourself in the explorer rather than taking anyone's word for it.
Running the numbers
Take a routine USDT transfer at roughly 64,285 Energy and work three volumes through each route. Rental pricing varies by provider, so treat the rental column as an illustration of shape, not a quote.
| Volume | Burning TRX | What staking would demand |
|---|---|---|
| 1 transfer a week | ~28 TRX a month | A stake sized for daily peak, idle six days out of seven |
| 1 transfer a day | ~193 TRX a month | A stake that is finally busy, plus a 14-day exit |
| 10 transfers a day | ~1,930 TRX a month | Staking clearly wins; the capital is fully used |
The pattern is the point. At one transfer a week the absolute saving is too small to justify locking capital. At ten a day the burn cost is large enough that owning the stake pays for itself and renting is the fallback for spikes. The interesting range is the middle, and there renting wins on flexibility rather than on headline price.
Where the answer flips
Volume decides it, and the boundaries are less blurry than they look.
| Your usage | What makes sense | Why |
|---|---|---|
| A few transfers a month | Burn TRX | The saving is a few TRX and not worth any setup |
| Several transfers a week | Rent | Saving per transfer is already large; still no reason to lock capital |
| Daily transfers, variable volume | Rent | Cost tracks usage instead of a stake sized for the peak |
| High constant volume | Stake, and rent the peaks | Stake covers the predictable base; rent absorbs the spikes |
The hybrid at the bottom is what most operators at scale converge on. Staking a position sized for your quiet baseline is efficient; staking for your busiest day means most of that capital sits idle most of the time.
The question to ask first
Before comparing prices, ask what you are willing to immobilise. Renting and burning cost you nothing but the fee. Staking costs you the use of capital for a fortnight beyond the moment you change your mind.
If your transfer volume is steady and large enough to keep a stake busy, stake. If it moves around, rent, and keep the capital.