Tron energy and bandwidth: the fee that is not a fee

What are Tron bandwidth and energy?

The documentation names three resources, and two matter at a cashier. Bandwidth pays for the size of a transaction: every transaction other than a read-only query uses as many units as it has bytes. Energy pays for computation, and only a call to a smart contract needs it. The third, TRON Power, is about voting and plays no part in a deposit.

Both bandwidth and energy refill continuously over a rolling twenty-four hours, so what you use now comes back gradually and not at midnight. Neither is a balance you hold the way you hold coins; each is a share of the network’s capacity.

Bandwidth vs. energy: which one does a casino deposit use?

It depends on what you send. TRX is the network’s native coin, and moving it is an ordinary transaction that uses bandwidth only. USDT on Tron is a TRC-20 token. TRC-20 is Tron’s counterpart of the Ethereum ERC-20 standard, and a token transfer is a call to the token’s contract, so it needs bandwidth for its size and energy for its work.

That single difference is why this site keeps TRX and USDT apart on every page, and why “a Tron deposit” is not one thing. One operator’s cashier can offer the coin and not the token, or the token and not the coin, and the cost to you differs between them.

What is free, and what is not

Each activated address has a free allowance of bandwidth, which the documentation currently gives as 600 units per rolling day. Energy has no free allowance at all. The documentation also notes that bandwidth is all-or-nothing within a single transaction: the network tries staked or delegated bandwidth first, then the free allowance, then a burn of TRX, and each option has to cover the whole transaction. They are not combined. An address whose free allowance has fewer units left than the transaction needs gets no help from it; the burn pays for the full size.

What happens when the address has no energy: the TRX burn

When stake and free allowance fall short, the network burns TRX from the sender’s own balance, at rates fixed by chain parameters that the network can change by proposal. The documentation prices a plain transfer of a few hundred bytes by multiplying its size by the bandwidth rate, and a contract call by multiplying its energy by the energy rate. The wallet’s fee limit caps how much may burn.

Two consequences for a player. First, by the documentation’s description an address that holds USDT and no TRX has nothing to burn, so unless it has energy through staking or delegation the token transfer cannot be paid for. Second, the fee limit is a ceiling and not a quote: if the call needs more energy than the limit allows, the transaction fails with an out-of-energy error, and the energy it used before failing is still charged.

How to get Tron energy

Three routes are described. You can stake TRX for energy or for bandwidth and receive a share of the network’s total in proportion to your stake; unstaking begins a waiting period before the TRX is yours again. Another account can delegate energy or bandwidth to you, and the documentation says exchanges and application operators commonly use delegation to cover costs for their users from a single staking pool. Or you can do nothing and let the burn pay.

Markets that sell or rent energy exist too, but they are third-party services outside the documentation, and we describe none of them. One note on words: staking here is the network’s own mechanism and has nothing to do with the operator called Stake, which has its own page.

Is a Tron transfer really cheap?

Often, but not by rule. Three things move the cost. The first is coin against token: energy on top of bandwidth. The second is contract load: the documentation describes a dynamic energy mechanism that raises the effective energy cost of heavily used contracts, stablecoin contracts among them, with a ceiling that it currently gives as 4.4 times the base cost, a value set on chain and open to change. The third is the price of the burn itself, which is a parameter and not a constant.

None of these depends on the amount you send. A transfer of twenty and a transfer of twenty thousand of the same token need the same energy. That is the reverse of the intuition built on percentage fees, and it is the reason a cashier line reading “fee 0%” and a wallet’s actual burn can both be honest at once.

Who pays at the cashier: you or the operator?

Direction decides. A deposit is a transaction from your wallet, so your address’s resources, or its TRX, pay. A withdrawal is a transaction from the operator’s wallet, so the operator’s resources pay, and the operator may pass the cost to you as a fee, absorb it or fold it into a flat figure.

Cloudbet’s page shows the clearest case. Its table prints a withdrawal fee for USDT on TRON about ten times the one for TRX on the same network, which is the shape the mechanics predict, though the column states no unit and we compare only the two numbers with each other. Rollbit says it charges no withdrawal fee beyond on-chain gas, previewed before you send. BitStarz prints a fee of 0% for Tron. These are different promises, not entries in a league table.

Is TRC-20 the same as USDT?

No. TRC-20 is a token standard. USDT is one token that exists in that standard on Tron and in other forms on other networks. When a cashier says “TRC20” it almost always means Tether on Tron; when it says “TRX” or “Tron” it means the native coin. Stake’s table shows both usages, and shows the awkward one too: its row for TRX itself is labelled “TRC20 network”, which we read as its name for the Tron network.

Operators differ in how clearly they separate the two. Stake and Vave list USDT on TRC20 by name. Cloudbet gives it its own route. BitStarz names the protocol in its page source. Duelbits and Rollbit name the coin or the family and leave the token route out. Roobet points USDT to an Ethereum explorer.

What the operators’ own pages say about timing and fees

Four statements are worth quoting, each tied to its stage. Roobet counts confirmations for BTC and XRP (1) and for ETH, LTC, USDT and USDC (3), none for TRX, all for deposits. Duelbits says deposits usually arrive within five minutes and may take longer in congestion, and that it cannot speed up confirmations. BetFury says a deposit is credited automatically and only rarely takes 24 to 72 hours, and, on another page, that withdrawals can take that long after a manual audit. BitStarz says “Instantly” on every row.

On Tron the network’s part of a deposit is short: a block roughly every three seconds, with the 27 elected producers taking turns. The documentation separates a transaction that has been included in a block from one that has become final, and an operator’s crediting rule may wait for the second. What it waits for is not something any of the pages above say.