← All articles

Ecosystem

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

PUBLISHED │ READ~12 min │ BYTRONORIGIN

energy bandwidth resources marketplaces

When a TRON wallet sends USDT TRC-20 without owning the Energy needed to pay the call, two things can happen. The wallet’s holder can let the protocol burn TRX to cover the Energy — costing roughly 6.5 TRX for a transfer to an existing-holder address, or ~13 TRX to a fresh one — or the holder can rent Energy from a marketplace and pay 60-80% less. The math is unambiguous enough that any operator running USDT transfers at scale uses a marketplace as a matter of course. The marketplaces are the deployed infrastructure that turns Stake 2.0’s delegation primitives into a working economy.

For an investigator, the marketplaces produce a distinctive on-chain signature: a wallet whose Energy is consistently being supplied by a known marketplace contract is operating as a fee-conscious actor — most commonly a USDT-transfer operator, a payment processor, or a bot. The marketplace relationship is not an ownership signal. /learn/fueling/ covers the attribution side; this article covers the infrastructure side — who, where, what the contracts look like, and how to recognize each marketplace’s transactions in a wallet’s history.

The protocol primitive

Stake 2.0 (covered in /learn/stake-2/) added two on-chain contract types that marketplaces use directly:

  • DelegateResourceContract (contract type 57) — transfers Energy or Bandwidth from a provider’s staked-resource pool to a recipient address.
  • UnDelegateResourceContract (contract type 58) — reclaims previously delegated resources.

A DelegateResourceContract transaction names the provider in owner_address and the recipient in receiver_address. The on-chain record fully attributes the marketplace as the owner_address for every fulfillment — there is no off-chain “rental escrow” that obscures who supplied the resources. Per the TRON developer hub, only unused resources obtained through staking in Stake 2.0 can be delegated, and only to an activated external account address (not to a smart contract).

The other half of the marketplace economics is the cost a TRON user pays when they do not have delegated Energy. The TRON network burns 100 sun (0.0001 TRX) per Energy unit when an account’s staked Energy is exhausted. A standard USDT TRC-20 transfer to an already-existing USDT holder consumes approximately 65,000 Energy. A transfer to a fresh address that has never held USDT consumes approximately 130,000 Energy. At 100 sun per unit, the burn-rate costs are roughly 6.5 TRX and 13 TRX per transfer respectively. Renting the same Energy from a marketplace typically costs in the range of 2-5 TRX. The differential is what supports the entire marketplace category.

Feee.io

Feee.io is one of the highest-volume centralized peer-to-peer Energy marketplaces on TRON. The Feee.io contract is at TYukBQZ2XXCcRCReAUguyXncCWNY9CEiDQ — a deployed contract with the on-chain account name CreatedByContract, a TronGrid balance of approximately 1.15 million TRX as of last verification, and over 1.5 million lifetime transactions reflecting sustained high-volume fulfillment. The contract has a frozenV2 ENERGY position, which is what enables it to delegate Energy via DelegateResourceContract.

Feee.io offers multiple purchase methods (API, manual, transfer, bulk) and supports rental terms by minute, hour, or day. The platform requires API-key authentication for programmatic access, so its developer documentation does not publish the canonical on-chain transaction shape — the on-chain receiver address shown above was identified via TronScan tagging and the TRONORIGIN curated catalog rather than via Feee.io self-publication.

Investigator signature. A wallet that receives Energy from TYukBQZ2XX… is, in effect, a Feee.io customer. The platform’s high transaction volume means many wallets across the chain will show this signature; it is not by itself a strong attribution signal, but combined with other operational patterns (high USDT transfer frequency, bot-like timing) it consistently identifies fee-conscious operators.

TronSave

TronSave’s user-facing flow is straightforward: a buyer sends TRX via a standard TransferContract (contract type 1) to the receiver address TWZEhq5JuUVvGtutNgnRBATbF8BnHGyn4S — an externally-owned account, not a smart contract, with an active ENERGY-staked position since June 28, 2023 — and shortly after, the platform delegates Energy to the address the buyer specified. The buyer never directly invokes DelegateResourceContract; TronSave’s backend monitors incoming TRX deposits and submits the delegation transaction on the buyer’s behalf.

TronSave’s API documents the buy flow with explicit parameters: resourceAmount, unitPrice (one of FAST, MEDIUM, SLOW, or a numeric SUN value), durationSec (default 3 days), requester, receiver, and resourceType (ENERGY or BANDWIDTH, default ENERGY).

Investigator signature. The temporal pair is the marketplace signature: a small TransferContract from a buyer to TWZEhq5JuU…, followed within a short window by a DelegateResourceContract with owner_address = TWZEhq5JuU… and receiver_address = <buyer or buyer's nominee>. If requester and receiver differ, the buyer is paying for Energy to be delivered to a different address — a common pattern for payment processors funding operational wallets, or for an exchange routing Energy to a customer’s withdrawal hot wallet.

Netts.io

Netts.io is a non-custodial aggregator: it pools orders from multiple underlying provider pools (the platform names JustLend, Trongas, Catfee, SoHu, APITRX, and private pools as backends). Its self-published receiver address is TDRrxdENQCCm8B8YEoy4uayaqeapw4rent — an EOA with a vanity suffix (“…rent”) and an active ENERGY-staked position since September 26, 2025. The owner key controlling the account is THLT7V3bvQBshLDtJ9iWhPA7ppXDuDaFxk.

Netts.io advertises pricing as low as 32 sun per Energy unit for short-duration rentals routed through its aggregator. The platform supports rental amounts from 65,000 Energy (one USDT transfer) up to 1.3 million Energy, and rental durations from 1 hour to 30 days.

Investigator signature. Like TronSave, the pattern is TRX or USDT TRC-20 transfer to TDRrxdENQC…, followed by a DelegateResourceContract with owner_address = TDRrxdENQC…. The vanity address is itself an investigator signal — operators routinely use vanity suffixes for branded receivers, so a …rent suffix on a high-volume delegation source has high confidence of being marketplace-related.

JustLend Energy Rental

JustLend’s Energy Rental is the decentralized alternative to the centralized marketplaces. It is a one-to-many protocol: lenders stake TRX into a pool, the pool delegates Energy to recipients, and a small per-day fee is paid in TRX. The entry contract is TU2MJ5Veik1LRAgjeSzEdvmDYx7mefJZvd, with the on-chain account name MarketProxy, a multi-million-TRX balance, and a substantial ENERGY-staked position.

Per JustLend’s documentation, the protocol supports renting by the hour or by the day, with a maximum single rental period of 30 days. Fees comprise an Energy Fee (time-based), a Security Deposit equivalent to one day’s Energy Fee, and a Liquidation Penalty. The platform documentation claims roughly 71% savings for a USDT-holding receiver and roughly 84% savings for a non-USDT receiver versus burning TRX directly.

Investigator signature. Unlike the centralized marketplaces, JustLend’s MarketProxy is a smart contract — a buyer invokes rentResource() via TriggerSmartContract, paying TRX, and the contract delegates Energy programmatically. The on-chain pattern: a TriggerSmartContract call to TU2MJ5Veik… followed by a DelegateResourceContract from TU2MJ5Veik… to the buyer’s chosen recipient. JustLend’s rentals can be made on behalf of any recipient address, so the same requester != receiver pattern available with TronSave applies here too.

Other notable providers

As of May 2026, Netts.io’s own competitive census ranks roughly 20 providers active on TRON. Notable ones beyond those above include:

ProviderApproximate price (sun/Energy unit)Notes
SoHu28Cheapest listed; small inventory
Tron Energy Market40Token-based marketplace (TEM token); requires pool-permission grant for sellers
JustLendDAO Energy49Decentralized via JustLend protocol
Feee.io73High volume, centralized P2P
TronSave74Centralized; documented developer API
Trongas75Centralized; uses fixed-pricing model

Per-provider sun rates fluctuate with real-time inventory and demand; treat the table as a snapshot rather than a long-term benchmark. As of May 2026 the market shape — many small providers, two or three dominant ones, and a decentralized JustLend alternative — has no consolidation events publicly documented.

Why marketplaces cannot be wallet origins

Like DEX routers (see /learn/dex-and-amm/) and bridges (see /learn/bridges/), Energy marketplace contracts cannot be wallet origins for a protocol-level reason. TRON smart contracts cannot create new accounts — see /learn/account-activation/ for the activation mechanics. Account activation requires an externally-owned account to submit a TRX or TRC-10 transfer to the uninitialized address.

Feee.io’s marketplace runs on a contract. JustLend’s MarketProxy is a contract. Both are smart contracts and cannot, at the protocol level, activate accounts. TronSave’s and Netts.io’s receivers are EOAs, which means they technically could activate accounts via a TRX transfer to a fresh address — but they don’t in normal operation. Their business model is to delegate Energy to addresses that are already active, not to seed new wallets with TRX. A wallet whose first activator is a marketplace EOA is an edge case worth flagging, not a routine pattern.

The TRONORIGIN heuristic encodes the marketplace category via a curated allowlist. When a delegation from an allowlisted marketplace address is detected, the system intentionally reduces the resource-delegation scoring weight that would otherwise apply (delegation normally signals ownership at +50; marketplace delegations are downweighted because the relationship is commercial, not custodial). /learn/fueling/ handles the heuristic side of this; for the investigator-facing logic, the rule is: marketplace delegation = commercial service, not control signal.

Investigative interpretation patterns

A wallet whose Energy is supplied by Feee.io / TronSave / Netts.io / JustLend. Fee-conscious actor; most commonly a USDT-transfer operator, a bot, or a service. The marketplace relationship is commercial. Look for: high USDT TRC-20 outbound volume, low TRX-staking activity, recurring small TRX payments to the marketplace receiver. These wallets are operators running TRC-20 transfer businesses at scale; the marketplace delegation is operational infrastructure, not an ownership signal.

A wallet that pays a marketplace contract repeatedly. Sustained TRC-20 transfer business. Possible identities include OTC desk, payment processor (USDT-denominated invoicing), exchange-deposit aggregator, scam payout system (chain hops typically requiring USDT transfers), arbitrage bot, or telecom-style remittance service. Repeat marketplace payments combined with high USDT outbound diversity is the strongest indicator of a USDT-payments business.

A wallet that itself delegates Energy outward to many unrelated recipients. Marketplace-operator behavior. If the wallet is on a known marketplace allowlist (Feee.io, TronSave, Netts.io, JustLend MarketProxy, the providers in Netts’s competitive census), the wallet is a known commercial marketplace. If it is not on any allowlist but exhibits the one-to-many delegation pattern with high recipient diversity, it is a candidate for a new or private marketplace — TRONORIGIN’s behavioral-detection module exists for exactly this case.

A wallet whose first activator is a marketplace EOA receiver. Edge case; warrants individual inspection. The marketplace’s stated business model does not include activating accounts. A first-activator-marketplace pattern most likely indicates either a one-off operational quirk (someone funded a fresh wallet via TronSave because the wallet had no TRX), or a marketplace operator using a customer-funded wallet for an unusual purpose. Not a routine attribution signal.

Investigative takeaways

Three things to carry forward.

First, marketplace delegation is commercial infrastructure, not custody. When Feee.io or TronSave delegates Energy to a wallet, the marketplace has no claim on the wallet’s funds, no operational control of the wallet’s keys, and no ownership interest. The relationship is the same as a power utility delivering electricity to a customer’s house — the utility is not a co-owner of the house. Treat marketplace delegations as commercial overhead; treat non-marketplace delegations (per /learn/fueling/) as ownership signals.

Second, the addresses to memorize are the centralized receivers. TYukBQZ2XX… (Feee.io), TWZEhq5JuU… (TronSave), TDRrxdENQC… (Netts.io), and TU2MJ5Veik… (JustLend MarketProxy) are the four most common marketplace counterparties an investigator will encounter. The Netts.io vanity suffix …rent is the easiest tell.

Third, the marketplace category is the deployed economy that makes Stake 2.0 work. TRON’s resource model would not be functional at its current transfer-volume scale without the marketplaces — the protocol’s free 600 Bandwidth per day per account does not cover any meaningful TRC-20 activity, and few retail users freeze enough TRX to generate the Energy a daily-active USDT user requires. The marketplaces are not a peripheral curiosity; they are the layer that turns a clever protocol into a chain that can carry the bulk of global stablecoin transfer volume.

Sources