Stake 2.0: TRON's Resource Model Explained

Most blockchainsA shared ledger maintained by many independent computers, in which transactions are grouped into blocks and each block cryptographically references the one before it. Because rewriting any past entry would break every link after it, the record is effectively append-only — new entries can be added, but history cannot be quietly altered. charge one native-token fee per 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.. TRON doesn’t. It meters two separate resources — 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. and 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. — and you get them one of two ways: stake 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 earn a daily allowance, or burn TRX on the spot when your allowance runs dry. The model looks odd until the economics click into place. The 2023 Stake 2.0 upgrade rewired how delegation, unstaking, and lock periods work, and the last section here connects all of it to what you can read off the chain.

Bandwidth and Energy: TRON’s two resources

What a transaction costs, and in which resource, depends on what it does.

Bandwidth pays for size. One byte of serialized transaction data costs one unit of Bandwidth, and every transaction on the network consumes some: TRX transfers, contract calls, 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. operations, account activationOn TRON, a newly derived address does not exist on-chain until an existing account activates it — by transferring TRX or TRC-10 tokens to it, by creating it explicitly with an account-creation transaction, or by a smart contract transferring value to it. Until activation the address is just a valid key pair with no state, and the activating account (which pays a small creation cost) is the new wallet's first on-chain relationship.. A bare TRX transfer is small and cheap; a contract call stuffed with parameters is larger and costs more.

Energy pays for computation. The moment a transaction runs code in the TRON Virtual Machine — a 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. transfer, a DeFiDecentralized finance — financial services (trading, lending, borrowing, earning yield) delivered by smart contracts that hold funds and enforce terms directly on-chain, with no bank or broker as intermediary. Anyone with a wallet can interact with a DeFi protocol, and every position and movement is publicly recorded. swap, any contract interaction — it burns Energy in proportion to how much work the code does. It’s TRON’s analogue to Ethereum gas, but scoped strictly to smart-contract execution. A plain TRX transfer touches no code, so it spends zero Energy.

Why two resources instead of one fungible “gas”? Because they behave differently. Bandwidth is cheap and predictable; Energy is variable, tied to computational load, and dominates total transaction cost because contract calls consume it in bulk — tens of thousands of units per call — even though its per-unit price is lower: Energy burns at 0.0001 TRX per unit, Bandwidth at 0.001. Splitting them lets a high-volume contract user stake purely for Energy without subsidizing byte-heavy traffic, and vice versa.

One baseline to keep in your head: every activated account gets 600 free Bandwidth units a day, no staking required — enough to cover the occasional simple transfer. Energy gets no such free allocation, so contract calls cost from the first unit.

Why stake TRX at all

Staking buys Bandwidth and Energy in bulk, by proportion: your share of the total network stake equals your share of the daily resource pool.

• Bandwidth pool: 43,200,000,000 units a day, split across everyone who staked for Bandwidth.
• Energy pool: 180,000,000,000 units a day, split across everyone who staked for Energy.

Both pools refill continuously over the 24 hours after you spend them, block by block rather than in one midnight reset.

Run out mid-transaction and TRON covers the shortfall by burning TRX automatically. For someone sending the odd transfer, the free 600 Bandwidth and a trivial burn handle everything. For an 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". pushing dozens or hundreds of USDT transfers a day, that burn adds up until staking stops being optional and becomes the cheaper way to operate. That cost structure is what makes delegation worth watching: an address that keeps another address’s operations funded is absorbing a real, recurring expense.

Stake 1.0 vs Stake 2.0

The original mechanism — call it Stake 1.0, built on FreezeBalanceContract — had a design knot: staking and resource type were welded together. Freezing TRX meant declaring up front whether you wanted Bandwidth or Energy. Switching meant unfreezing (a 3-day lock), then re-freezing for the other type. And delegation was all-or-nothing: you could hand a stake’s resources to one recipient, in full, with no partial amounts.

Stake 2.0 — FreezeBalanceV2Contract and UnfreezeBalanceV2Contract from TIP-467 — pulled those threads apart:

• Staking and delegation are independent. Freeze once, then delegate to as many recipients as you like, in any amounts, no re-staking.
• Partial unstaking works: unfreeze a specific amount and leave the rest staked.
• Delegation changes without unstaking — re-point resources to a different recipient with no unfreeze cycle.
• Voting power still comes from the stake. A FreezeBalanceV2Contract stake grants TRON PowerTRON's voting weight: staking TRX grants TRON Power at one unit per TRX staked, spendable as votes for Super Representative candidates. It is non-transferable — it cannot be sent or sold, only earned by staking — and unstaking revokes it along with the votes it was backing. TRON Power is how holdings translate into governance influence under delegated proof-of-stake: block-producer elections are decided by staked, revocable votes rather than by one account, one vote. exactly as Stake 1.0 did — one TP per staked TRX — and casting those votes for an SROne of the 27 elected block producers on the TRON network, chosen every six hours from a wider candidate pool by TRON Power voting (one vote per staked TRX); candidates ranked 28th–127th, called SR partners, earn voting rewards without producing blocks. SRs collect block and vote rewards and pass a share to their voters after deducting a self-set commission. TRON's protocol code also calls these producers "witnesses" — a term other DPoS chains such as Steem and Hive use for the same role. stays a separate VoteWitnessContract step. Stake 2.0 reworked delegation, not the staking-to-voting-power link. The mechanics live in the field-book chapter Voting on TRON.
• Unstaking now waits. After UnfreezeBalanceV2Contract, the TRX sits in a 14-day window before a separate WithdrawExpireUnfreezeContract releases it.
• Up to 32 unstaking operations can run at once — flexibility Stake 1.0 never had.

A compatibility note for old walletsSoftware 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.: the upgrade didn’t invalidate Stake 1.0 positions — resources and votes earned under 1.0 stayed valid past April 7, 2023. But the old delegation model, the one that needed re-staking to change recipients, couldn’t carry forward. Only Stake-2.0 TRX can be delegated under the new rules.

The four TIPs behind it

Stake 2.0 didn’t land in a single commit. It arrived as a sequence of proposals over eight months, each one adding a piece, and knowing which is which helps you date what you find on-chain.

TIP-467 — Stake 2.0 design (proposed September 28, 2022; Final). The core spec: the split between staking and delegation, partial unstaking, multi-recipient delegation, and the N-day unstaking window (N being a governance parameter). It also defined six new TVM opcodes — FREEZEBALANCEV2, UNFREEZEBALANCEV2, DELEGATERESOURCE, UNDELEGATERESOURCE, CANCELALLUNFREEZEV2, WITHDRAWEXPIREUNFREEZE — plus their HTTP APIs, letting smart contractsA 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. touch the staking system directly for the first time.

TIP-519 — Enable Stake 2.0 (Final). The on-chain governance proposal that flipped the switch on mainnet. It set two parameters at once: No. 59 (ALLOW_TVM_VOTE, to 1) enabling contract-level voting, and No. 70 (UNFREEZE_DELAY_DAYS, to 14) establishing the 14-day window. Created April 4, 2023; effective April 7, 2023 — the live date for Stake 2.0.

TIP-541 — Cancel unstaking (created May 5, 2023; Final). Added the wallet/cancelallunfreezev2 API, which cancels all in-progress unstaking during the 14-day wait. Before it, hitting unstake was a one-way door — change your mind and you waited out the full 14 days. Cancelling puts the TRX back to staked and resumes resource and vote accrual. It’s purely additive and touches nothing already in flight.

TIP-542 — Customizable delegation lock period (created May 12, 2023; Final). Added a lock_period parameter (in blocks) to wallet/delegateresource. Stake 2.0 had shipped with a boolean lock flag — set it and the delegation couldn’t be undelegated for a fixed 3 days; TIP-542 swapped that fixed term for a count the delegator sets at delegation time — which lets two parties write a resource-leasing agreement straight into the chain. Leave lock true and lock_period at 0 and you get the old 86,400-block (3-day) default.

Delegation: when A funds B’s resources

When A stakes TRX and delegates Energy or Bandwidth to B, B transacts as if it had staked itself — the consumption draws on A’s allowance, and the cost lands on A. B pays nothing and never needs to hold staked TRX. The mechanics are that simple, and they are where the model earns its keep for an investigator. A few constraints frame it:

• Only Stake-2.0 resources can be delegated; Stake 1.0 positions are ineligible.
• Only unused resources can be delegated — not the slice A is already spending on its own transactions.
• A can delegate to multiple recipients, in different amounts, independently.
• It shows up on-chain as DelegateResourceContract; undelegation as UnDelegateResourceContract. Both are attributable to the delegating address.

Now consider who actually does this. Exchanges serve millions of users out of shared custodyAn arrangement in which one party — the custodian — holds the private keys or reserves controlling assets that belong to others. On a blockchain, whoever holds the keys is the on-chain owner: custodied funds sit under the custodian's addresses, so the entity an analyst sees acting on-chain is the custodian, not the customer. wallets, so per-user delegation is economically absurd at that scale — they don’t delegate Energy or Bandwidth to individual accounts. The addresses that do delegate have a specific reason to fund one particular wallet: a controller subsidizing a receiving address, a business covering a counterparty, an operator keeping a field wallet alive.

A steady delegation relationship — A delegating to B again and again, with B’s transactions spending that resource — is a durable economic tie. A carries B’s cost, and the act is attributable to A. Every re-delegation puts a fresh event on the record.

The 14-day unstaking window

Network parameter No. 70, UNFREEZE_DELAY_DAYS, sets the wait. It’s a governance value — Super Representatives could change it by proposal — but it has held at 14 since launch.

On-chain it starts when the staker broadcasts UnfreezeBalanceV2Contract with the amount and resource type; the TRX leaves the staked balance the moment that lands. Then it sits in limbo for 14 days, neither staked nor liquid, and that window is the only stretch where TIP-541’s cancel can reverse the whole thing. When the window closes, WithdrawExpireUnfreezeContract pulls the TRX back to the liquid balance — the on-chain proof the unstake finished.

The April 7, 2023 boundary matters when reading history. Before it, unstaking used UnfreezeBalanceContract (Stake 1.0) with a 3-day lock and no separate intermediate transaction; after it, the two-step pattern is standard. Across the upgrade, the contract types tell you which era you’re in. One Stake 1.0 quirk has no modern equivalent: unstaking under the old model revoked all of an account’s votes at once, whatever resource you pulled. Stake 2.0 removes only the votes backed by the specific TRX unstaked — keep that in mind when vote weight jumps in a wallet that lived through the transition.

What this means for investigators

Pull all of this back to the work of tracing a wallet and a few signals stand out.

Delegation is an ownership signal. A DelegateResourceContract is a deliberate act — the sender chose to fund a specific recipient’s transactions. A recurring delegation from the same source to the same target, especially Energy covering USDT calls, is among the strongest candidate-ownership indicators on TRON.

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. rounds out the picture. Some wallets skip delegation and fund others with small TRX transfers sized to cover the fallback burn. Spot the address that tops up a wallet just before its high-value USDT moves and you’re looking at the same thing — operational control. The dedicated treatment lives at Who Pays the Fees?.

Contract types also date the activity, and the completed ones say the most. FreezeBalanceContract puts activity before April 2023; FreezeBalanceV2Contract puts it after — which matters when you read delegation events and vote-weight changes across the boundary. A WithdrawExpireUnfreezeContract carries its own tell: someone kicked off an unstake and came back 14 days later to claim it, where a wallet abandoned or handed off mid-window rarely finishes the sequence cleanly. And a large unstake right before a big outbound transfer can mark deliberate liquidity staging — the unstake is the setup, and the 14-day gap sits right there in the record.

How to weigh these patterns together when judging who funded and likely owns a wallet is covered alongside the fueling write-up linked above.

Sources

Primary documentation and data sources used for the facts in this article:

• GitHub: tronprotocol/tips. “TIP-467: Stake 2.0 — A new TRON stake model” (tip-467.md) — Core Stake 2.0 specification: new contract types, TVM opcodes, delegation mechanics, N-day unstaking parameter. Proposed September 28, 2022; status: Final.
• GitHub: tronprotocol/tips. “TIP-467 issue thread” — Community discussion and clarifications on the Stake 2.0 design.
• GitHub: tronprotocol/tips. “TIP-519: Proposal to enable Stake 2.0” — On-chain activation proposal; sets network parameters No. 59 (ALLOW_TVM_VOTE = 1) and No. 70 (UNFREEZE_DELAY_DAYS = 14). Created April 4, 2023; effective April 7, 2023.
• GitHub: tronprotocol/tips. “TIP-541: Support canceling unstaking in Stake 2.0” (tip-541.md) — wallet/cancelallunfreezev2 API; created May 5, 2023; status: Final.
• GitHub: tronprotocol/tips. “TIP-542: Resource delegating supports customizable lock period” (tip-542.md) — lock_period parameter for wallet/delegateresource; replaces fixed 3-day lock; created May 12, 2023; status: Final.
• GitHub: tronprotocol/tips. “TIP-541 issue thread” — Cancel-unstaking discussion.
• GitHub: tronprotocol/tips. “TIP-542 issue thread” — Customizable lock period discussion.
• TRON Developer Hub. “Resource Model” — Bandwidth (1 byte = 1 unit; 600 free/day per account; 43.2 billion daily pool), Energy (180 billion daily pool), fallback TRX burn rates (0.001 TRX/Bandwidth unit; 0.0001 TRX/Energy unit), 24-hour regeneration.
• TRON Developer Hub. “Staking on the TRON Network” — FreezeBalanceV2Contract / UnfreezeBalanceV2Contract contract names, Stake 1.0 vs Stake 2.0 comparison, 32 concurrent unstaking operations limit, backward compatibility note.
• TRON DAO Forum. “TRON Stake 2.0 Proposal” — Community discussion thread on Stake 2.0 design rationale.