Energy and Bandwidth Marketplaces on TRON: The Deployed Infrastructure of Delegated Resources

When a TRON walletSoftware or hardware that stores private keys and uses them to sign transactions. A wallet holds keys, not coins — balances live on the ledger itself — so the same funds can be reached from any wallet loaded with the same keys, and losing the wallet loses nothing if the keys are backed up elsewhere. sends USDTA US-dollar stablecoin issued by Tether, first launched in 2014 on Bitcoin's Omni Layer and circulating on TRON as a TRC-20 token since April 2019. Tether retains privileged functions in the token contract — it can blacklist addresses and destroy blacklisted balances — so every USDT balance is ultimately conditional on the issuer's authority. Not to be confused with counterfeit tokens that copy the USDT name and symbol without any issuer or backing. TRC-20TRON's smart-contract standard for fungible tokens, derived from Ethereum's ERC-20: a compliant contract exposes transfer, approve, allowance, and transferFrom, and emits Transfer and Approval events. USDT on TRON is issued as a TRC-20 token. Because every TRC-20 transfer is a contract call, it consumes Energy (plus Bandwidth) and — unlike a TRX or TRC-10 transfer — cannot activate a not-yet-created account. without the EnergyA TRON network resource that meters the computational cost of smart-contract execution, consumed whenever a transaction calls contract code — including TRC-20 token transfers such as USDT. An account obtains Energy by staking TRX or receiving a delegation from another account; if it holds too little, the shortfall is paid by burning TRX from its balance. to pay for the call, it has two options: let the protocol burn TRXThe native coin of the TRON network. TRX settles value directly (no contract call needed), is staked to obtain Energy, Bandwidth, and voting power, and is burned to pay fees when staked resources fall short. Its smallest unit is the sun: 1 TRX = 1,000,000 sun. to cover the Energy — roughly 6.5 TRX for a transfer to an existing holder, ~13 TRX to a fresh addressA public identifier, derived from a key pair, at which an account receives funds and is looked up on-chain. Anyone can view an address's history, but only the matching private key can spend from it. TRON addresses are 34-character Base58Check strings beginning with "T". — or rent that Energy from a marketplace for a fraction of it. The math isn’t close. Anyone running USDT transfers at volume rents.

For an investigator, that produces a clean signatureA cryptographic proof, produced with a private key over a transaction's exact contents, that the key holder authorized that transaction and no other. Nodes verify the signature before accepting the transaction, so a valid signature is definitive evidence the key was used — though not of who was holding it at the time.: a wallet whose Energy is consistently supplied by a known marketplace is a fee-conscious actor — usually a USDT-transfer operator, a payment processor, or a bot. It is not an ownership signal. Who Pays the Fees? covers the attributionThe process of identifying the entity most likely to control a blockchain address by combining on-chain signals — who created and funded it, how it transacts, which keys can act for it — with known service patterns and labels. Attribution conclusions are evidence-weighted judgments, not certainties, and are strongest when several independent signals converge. side; this article covers the infrastructure — who the marketplaces are, where their contracts live, and how to spot each one in a wallet’s history.

How a rental actually moves on-chain

Every rental ends the same way: a DelegateResourceContract moves Energy from the marketplace’s own staked pool to the recipient, with the marketplace named as owner_address. The renter never makes that delegation call. Payment is the step that differs. The centralized P2P services — Feee.io, TronSave, Netts.io — take a plain TRX transfer; JustLend’s pool takes a TriggerSmartContract call. The diagram below traces the centralized pattern.

Stake 2.0 (see Stake 2.0) gave the marketplaces the two contract types they run on:

• DelegateResourceContract (type 57) — moves Energy or BandwidthA TRON network resource that covers the byte-size cost of putting a transaction on chain — one byte consumes one Bandwidth point. Every account receives a small free daily allowance (also called free bandwidth); heavier usage requires staking TRX, receiving a delegation, or burning TRX to cover the bytes. from a provider’s staked-resource pool to a recipient address.
• UnDelegateResourceContract (type 58) — reclaims previously delegated resources.

A DelegateResourceContract names the provider in owner_address and the recipient in receiver_address. So the chain fully attributes the marketplace as owner_address on every fulfillment — there’s no off-chain “rental escrow” hiding who supplied the resources. Per the TRON developer hub, only unused resources obtained through Stake 2.0 stakingLocking TRX (historically called freezing) to obtain network resources instead of paying fees per transaction — a stake earns either Energy or Bandwidth, chosen at stake time. Staking also grants TRON Power for Super Representative voting, at one vote per staked TRX, making a wallet's stake both its fee budget and its governance weight. can be delegated, and only to an activated external account, never to a smart contractA program deployed to a blockchain that runs deterministically when called, holding its own state and balance and enforcing its rules without any operator's ongoing involvement. Because a contract executes code rather than acting on anyone's initiative, its address represents logic — funds can flow through it, but the contract itself is not a person or a controlling entity..

The other half of the economics is what a user pays without delegated Energy. When staked Energy runs out, the network burns 100 sun (0.0001 TRX) per Energy unit. A standard USDT transfer to an existing USDT holder consumes ~65,000 Energy; to a fresh address that has never held USDT, ~130,000. That’s roughly 6.5 and 13 TRX in burn. Renting the same Energy typically runs 2–5 TRX.

The four receivers worth memorizing

Two distinctions organize the field: centralized P2P services and aggregators versus JustLend’s decentralized pool, and EOAAn account controlled by a private key held by a person or organization, as opposed to a contract account controlled by code. The term comes from Ethereum, but the distinction applies on TRON too: every externally initiated transaction begins with an EOA's signature, so tracing who acts on a chain ultimately means tracing EOAs. receivers versus smart contracts. Most of the traffic an investigator meets passes through four accounts.

Feee.io — TYukBQZ2XX…

One of the highest-volume centralized P2P Energy marketplaces on TRON. The contract TYukBQZ2XXCcRCReAUguyXncCWNY9CEiDQ carries the on-chain account name CreatedByContract, a seven-figure TRX balance, and a lifetime transactionA signed instruction ("tx" for short) that changes on-chain state — transferring value, calling a contract, or updating an account's settings. Once it is included in a block and that block reaches finality the record is permanent: later transactions can supersede its effects, but the entry itself can never be edited or deleted. Before finality, a freshly included transaction can still be reversed if its block is reorganized out. count that passed the million mark — sustained, high-volume fulfillment. The delegation capacity comes from its frozenV2 ENERGY position.

Feee.io sells via API, manual, transfer, and bulk methods, with rental terms by minute, hour, or day. Programmatic access needs an API key, so its docs don’t publish the canonical on-chain shape; the address is instead identified from public block-explorer name-tagging (TronScan surfaces the CreatedByContract account) corroborated across its transaction graph, and the balance and lifetime-transaction figures cited here are directly observable on any TRON block explorer and can be re-derived by any analyst. A wallet receiving Energy from TYukBQZ2XX… is effectively a Feee.io customer. Given the volume, that’s common across the chain and weak as a standalone attribution. Paired with high USDT-transfer frequency and bot-like timing, it reliably marks an operator renting to keep transfer costs down.

TronSave — TWZEhq5JuU…

TronSave’s flow is the textbook EOA pattern. A buyer sends TRX via a plain TransferContract (type 1) to the receiver TWZEhq5JuUVvGtutNgnRBATbF8BnHGyn4S, an externally-owned account with an active ENERGY-staked position since June 28, 2023. TronSave’s backend watches for the incoming deposit and delegates Energy to the address the buyer specified. The buyer never calls DelegateResourceContract.

The API spells the buy out: resourceAmount, unitPrice (FAST, MEDIUM, SLOW, or a numeric SUN value), durationSec (default 3 days), requester, receiver, and resourceType (ENERGY or BANDWIDTH, default ENERGY). The signature to watch is the temporal pair: a small TransferContract to TWZEhq5JuU…, then within a short window a DelegateResourceContract with owner_address = TWZEhq5JuU…. When requester and receiver differ, the buyer is funding a different address — common for payment processors feeding operational wallets, or an exchange routing Energy to a customer’s withdrawal hot walletAn online, always-connected wallet a service uses for day-to-day operations — paying withdrawals, sweeping deposits, funding fresh addresses. Because its keys live on internet-connected systems, a service keeps only working balances in it; in tracing work, a service's hot wallet often shows up as the first funder of the addresses it operates..

Netts.io — TDRrxdENQC…rent

A non-custodial aggregator that pools orders across backends it names as JustLend, Trongas, Catfee, SoHu, APITRX, and private pools. Its self-published receiver TDRrxdENQCCm8B8YEoy4uayaqeapw4rent is an EOA with a vanity …rent suffix and an active ENERGY-staked position since September 26, 2025; the controlling owner key is THLT7V3bvQBshLDtJ9iWhPA7ppXDuDaFxk.

Netts advertises short-rental pricing well below the protocol’s 100-sun-per-unit burn rate, amounts from 65,000 Energy (one USDT transfer) up to 1.3 million, and durations from 1 hour to 30 days. The pattern matches TronSave — TRX or USDT transfer to TDRrxdENQC…, then a DelegateResourceContract with owner_address = TDRrxdENQC…. The vanity suffix is itself a tell: operators routinely brand receivers this way, so a …rent ending on a high-volume delegation source is almost certainly marketplace-related.

JustLend Energy Rental — TU2MJ5Veik…

The decentralized alternative. It’s one-to-many: lenders stake TRX into a pool, the pool delegates Energy to recipients, and renters pay a small per-day fee in TRX. The entry contract TU2MJ5Veik1LRAgjeSzEdvmDYx7mefJZvd carries the on-chain name MarketProxy, a multi-million-TRX balance, and a substantial ENERGY-staked position.

Per JustLend’s docs, you rent by the hour or day, up to a 30-day maximum per rental. Fees comprise an Energy Fee (time-based), a Security Deposit equal to one day’s Energy Fee, and a Liquidation Penalty. The docs claim ~71% savings for a USDT-holding receiver and ~84% for a non-USDT receiver versus burning TRX directly. Because MarketProxy is a contract, the buyer calls rentResource() via TriggerSmartContract and the contract delegates programmatically — so the chain shows a TriggerSmartContract to TU2MJ5Veik… followed by a DelegateResourceContract from it. Rentals can target any recipient, so the same requester != receiver split as TronSave applies.

The rest of the field

In its May 2026 competitive census, Netts.io ranked roughly 20 providers active on TRON. Beyond the four above, the census listed (cheapest first):

Provider	Notes
SoHu	Cheapest in the census; small inventory
Tron Energy Market	Token-based (TEM tokenA unit of value recorded inside a smart contract rather than in the chain's native ledger — the contract keeps the balance table, and moving tokens means asking the contract to update it. Not to be confused with a coin, which is the chain's built-in asset (TRX on TRON) used to pay for the network itself.); sellers need a pool-permission grant
JustLendDAO Energy	Decentralized via JustLend
Feee.io	High volume, centralized P2P
TronSave	Centralized; documented developer API
Trongas	Centralized; fixed-pricing model

Per-provider rates swing with real-time inventory and demand, so any published rate sheet is a snapshot of one moment. The census showed a market of many small providers, two or three dominant ones, and a decentralized JustLend alternative, with no publicly documented consolidation events.

Why a marketplace can never be a wallet’s origin

A TRON smart contract is never credited as an account’s origin. A contract’s internal TRX or TRC-10 transfer can trigger activation (at a 25,000 Energy surcharge), but the activation record names the external account that signed the call, never the contract — see Account Activation. That protocol rule puts marketplace contracts in the same category as DEXAn exchange implemented as smart contracts: traders swap tokens directly from their own wallets against on-chain liquidity, so no operator ever takes custody of funds. On TRON the principal DEX is SunSwap — formerly JustSwap, rebranded in 2021 when Sun.io absorbed it, so older on-chain activity against JustSwap contracts belongs to the same protocol. routers (see Decentralized Exchanges on TRON) and bridgesA protocol that moves value between blockchains, most commonly by locking the asset in a contract on the source chain and minting a wrapped equivalent on the destination chain (lock-mint), redeemed later by burning the wrapped token to release the original (burn-release). For tracing, a bridge's contract addresses are shared plumbing: a flow into a bridge marks a chain boundary to carry the investigation across, and the bridge itself is never the origin of the funds. A bridged, wrapped stand-in is also not the same asset as a native issuance on the destination chain — see native vs bridged. (see Cross-Chain Bridges on TRON): none of them can be a wallet’s credited origin.

Feee.io’s marketplace runs on a contract; JustLend’s MarketProxy is a contract. Neither can be an account’s credited activator at the protocol level. TronSave’s and Netts.io’s receivers are EOAs, so they technically could activate a fresh address via a TRX transfer — but they don’t in normal operation. Their business is delegating Energy to already-active addresses; seeding new wallets with TRX plays no part in it. A wallet whose first activator is a marketplace EOA is a genuine edge case, and worth flagging when it turns up.

Delegation from an ordinary counterparty is one of the stronger on-chain hints of a shared owner — someone is spending their own staked resources to fuel another address. Delegation from a known Energy marketplace is the opposite: a paid service with no ownership claim attached. The practical rule for any analyst is to keep a list of known marketplace addresses and read delegations from them as commercial overhead rather than evidence of control. The attribution side is developed in the fuelingAny arrangement in which an outside party keeps a wallet transacting without its holder paying the network costs — by delegating staked resources, topping up small amounts of the native coin for fees, or sponsoring transactions through a fee-payment service; also called fee sponsorship. Not to be confused with funding lineage: fueling explains who pays a wallet's running costs, not where its balance came from. article linked above, and the investigator rule is the same either way.

Reading the patterns

How a marketplace relationship shows up depends on which side of it the wallet sits.

Energy supplied by a marketplace. A fee-conscious actor, most often a USDT-transfer operator, bot, or service. Corroborate with high USDT TRC-20 outbound volume, low TRX-staking activity, and recurring small TRX payments to the marketplace receiver. The delegation is operational infrastructure with no ownership meaning.

Repeated payments to a marketplace. A sustained TRC-20 transfer business. Candidates: OTC desk, USDT-denominated payment processor, exchange-deposit aggregator, scam payout system (chain hops usually need USDT transfers), arbitrage bot, or remittance service. Repeat marketplace payments plus high USDT-outbound diversity is the strongest tell of a USDT-payments operation.

A wallet delegating Energy out to many unrelated recipients. Marketplace-operator behavior. If it’s on a known allowlist (Feee.io, TronSave, Netts.io, JustLend MarketProxy, or the providers in Netts’s census), it’s a known commercial marketplace. If it’s not on a known marketplace list but shows the one-to-many pattern with high recipient diversity, it’s a candidate for a new or private marketplace — precisely the kind of address worth flagging for closer inspection.

One pattern deserves individual inspection rather than a rule: a wallet whose first activator is a marketplace EOA. The marketplace’s business model doesn’t include activating accounts, so this usually means a one-off operational quirk — a fresh wallet funded via TronSave because it had no TRX — and it shouldn’t be read as a routine attribution signal.

What to carry forward

When Feee.io or TronSave delegates Energy to a wallet, it has no claim on the wallet’s funds, no control of its keys, and no ownership interest. Treat marketplace delegations as commercial overhead. Non-marketplace delegations, per the fueling article, remain ownership signals.

Keep the four receivers in muscle memory: TYukBQZ2XX… (Feee.io), TWZEhq5JuU… (TronSave), TDRrxdENQC… (Netts.io), and TU2MJ5Veik… (JustLend MarketProxy). The …rent vanity suffix is the easiest to clock.

The category itself is what makes Stake 2.0 work at scale. The free 600 Bandwidth per day covers no meaningful TRC-20 activity, and few retail users freeze enough TRX to generate the Energy a daily-active USDT wallet burns through. The marketplaces are the layer that lets a clever resource model carry the bulk of global stablecoinA token designed to hold a steady value against a reference asset, most commonly one US dollar. The target is maintained either by an issuer holding reserves that back and redeem the token, or algorithmically through mint-and-burn incentives — two very different risk models behind the same face value. transfer volume.

Sources

• TRON Developer Hub — Staking on TRON Network — primary; delegation rules, EOA-only restriction, Stake 2.0 source attribution.
• TRON Developer Hub — Resource Model — primary; 100 sun per Energy unit, 180B daily network Energy pool, 600 free Bandwidth per account.
• tronprotocol/protocol Tron.proto — primary; DelegateResourceContract (type 57) and UnDelegateResourceContract (type 58) enum definitions.
• tronprotocol/protocol balance_contract.proto — primary; DelegateResourceContract message field layout.
• Feee.io — primary, operator’s homepage; documents business model and rental-term flexibility.
• TronSave Developer Docs — Buy with Private Key — primary; mainnet receiver address TWZEhq5JuU… and TransferContract flow.
• TronSave Developer Docs — Estimate TRX — primary; API parameters and default 3-day duration.
• Netts.io homepage — primary, operator’s site; self-published receiver address TDRrxdENQC…rent, aggregator backend list, pricing tiers.
• Netts.io Market Comparison — operator-published competitive census; per-provider sun rates as of research.
• JustLend Energy Rental Documentation — primary, JustLend docs; MarketProxy address TU2MJ5Veik…, fee components, savings figures.
• Netts.io TRON USDT Energy Handbook 2025 — operator-published; 65,000-Energy USDT transfer cost figures.
• TronSave — How Much Does It Cost to Send USDT TRC-20 — operator-published; corroborates burn-vs-rental cost differential.
• TRONORIGIN attribution methodology (proprietary) — the project’s own approach to distinguishing commercial infrastructure (marketplaces, routers, bridges) from ownership relationships, and its curated registries of known infrastructure addresses.