Blog
Notes from the desk that routes energy for USDT payouts. Where the guides explain how TRON prices a transfer, these posts are about running payouts with that knowledge: what to hand the API, what comes back when something goes wrong, and which failures are worth catching before money moves.
What JustLend energy rental really costs
A JustLend DAO position is billed twice: per second for occupying the stake, and again for the energy actually spent. The second charge turned out to be almost the whole bill — here is one order of ours, rented, spent and returned on mainnet and priced from its own event records, with twenty-six more from the public feed of the same day.
How to compare TRON energy providers
Seventeen vendors' rates stood on the table our watch read on one September day, and scarcely any two of them described the same good. What a headline price hides — the unit, the term, the order limits, the stock, whether it was published or derived, and how old it is — with a checklist short enough to run in ten minutes.
How to rent TRON energy safely
A legitimate rental needs one thing from you: the address the energy should land on. How to read the delegation on the receiving account rather than take delivery on trust, what each red flag is actually after — a connect-wallet prompt, a USDT approval, a bot asking for a seed phrase — and the difference between delivering energy and delivering your transfer.
Energy vs bandwidth on TRON
TRON meters bytes and computation separately, and a USDT transfer spends both — tens of thousands of units of energy against a few hundred points of bandwidth. What each meter pays for, the free daily allowance one of them has and the other never will, and why the market rents energy and not bandwidth.
How long rented TRON energy actually lasts
Three clocks run over a rented delegation, and the term in the price list is only the first of them: the term a seller sold, the on-chain lock that is the only thing stopping an early reclaim, and the daily recovery of energy already spent. Which one answers the question, and what expired means on an order that ended unused.
How energy delegation works on TRON
A staker keeps its TRX and its votes and lends out the energy that stake earns, in one transaction the receiving wallet never signs. What both accounts show afterwards, the lock counted in blocks of three seconds, the four things the network refuses, and how a five-minute rental is built on all of it.
How much TRX do you need to stake for energy?
The stake that covers a day of transfers is one division: the network's daily energy pool over everybody's stake, read live and worked through. A table of stake sizes from one transfer a day to five hundred, the costs staking carries beyond the capital, and the three conditions that all have to hold before it beats renting.
TRON account not activated: what it blocks and how to clear it
An address is a key pair until the network creates an account for it. What an unactivated wallet does to an order, how that refusal differs from a malformed address, why an unactivated recipient is a price rather than a refusal, and the one transaction that clears it.
OUT_OF_ENERGY: the TRON error that spends the fee and sends nothing
A transaction in a block, a fee taken, and no tokens moved. What the result means mechanically, the three ways a payout run walks into it — a limit sized for the wrong recipient, energy already spent, a limit of zero — and the fixes, from the quickest to the one that actually costs least.
When TRON energy is cheapest
Our selling tariff runs in time-of-day zones, and thirty days of hourly history say where the cheap hours actually fell. Which UTC hours were cheapest and which dearest, how off-peak compared with peak, what the boundaries are drawn by, and what a payout desk can schedule against them.
What a TRON energy API actually does
An energy API sells a delegation: another account's energy, lent to the address that will sign your transfer, for a few minutes. The minimum working flow — authenticate, estimate, order in mode A, read send_before — with the idempotency key, the rate-limit headers, and the two modes where you hand over a signed transaction or name no recipient at all.
How a wallet sends USDT without holding TRX
The burn beside a USDT transfer is not a fee anybody set — it is the network charging for energy the account does not have. Rented energy, the few-minute window it arrives in, and three ways to arrange it: send it yourself, hand us a signed transaction, or charge the wallet ahead of time.
Why USDT transfers fail
Four failures a payout desk meets over and over: no energy on the sender, a recipient that has never held USDT, a frozen recipient, and a sending wallet that was never activated. How to see each of them before the money moves, and what our statuses and refund rules say when delivery does fail.
Batch USDT payouts, up to 500 at a time
One order can carry up to 500 transfers. The estimate-first workflow, the per-recipient warnings that come back with it, what partially_completed means for the invoice, and the pair — webhooks and an idempotency key — that makes a payout pipeline safe to retry.