TRON (TRX) Price

TRX (TRONIX) is the native token of the TRON network, not a token such as TRC-20 that is built on TRON. It can serve as a transfer asset and is also used to pay network resource costs, stake for resources and voting power, and act as a fee-denomination, collateral, or liquidity-related asset in TRON decentralized applications. Its “native” status means that the protocol itself uses TRX for resources, staking, and rewards; TRC-series standards are interface specifications developers use to create other assets on that network. Both can coexist on the same network, but they have different roles at the protocol layer.

TRX's core uses are paying resource costs, staking to obtain bandwidth or energy and TRON Power (TP), and using TP to vote for Super Representatives. When resources are insufficient, an account can burn TRX to complete a transaction; resources obtained through staking or delegation can first be used to cover the relevant consumption. In DeFi or other applications, TRX may also be used as collateral, liquidity, or a fee-denomination unit under each application's rules. These are application-layer uses and do not mean the protocol guarantees any return; whether a user actually pays TRX, consumes resources, or receives rewards depends on the transaction executed, staking status, and rules of the chosen application.

After staking TRX, users obtain TRON Power and resources such as bandwidth or energy. Each 1 TRX staked produces 1 TP; TP is voting weight that can be used to vote for Super Representatives (SRs). The direct purpose of resources is to cover consumption for transaction data storage or smart-contract execution, reducing the need to burn TRX when resources are insufficient. Staking does not permanently give up TRX. The lifecycle described officially is Stake → Unstake → Withdraw: first stake to obtain resources and TP; initiate unstaking when funds need to be retrieved; and withdraw TRX back to a freely transferable state after the network-specified waiting period ends. The number of waiting days is determined by the on-chain parameter getUnfreezeDelayDays, so the current network parameter should be used.

Bandwidth measures the size of transaction data written to the blockchain database, while energy measures the computation required for the TRON Virtual Machine to execute specific operations. Therefore, ordinary transfers primarily involve bandwidth, while smart-contract calls usually also involve energy; these two resources should not simply be viewed as the same type of fee. The fallback methods differ when resources are insufficient. If staked or delegated bandwidth for an ordinary transaction cannot cover the full byte cost, the network attempts to use free bandwidth; if that is still insufficient, TRX is burned for the full bandwidth cost. For contract execution, existing energy can cover part of the caller's cost and TRX is burned for the remainder. Current unit prices and direct fees are on-chain parameters that can be adjusted through proposals.

TRX is the native base asset of the TRON protocol; TRC-10, TRC-20, TRC-721, and TRC-1155 are standards used to create other tokens or digital assets on TRON. TRC-20 in particular is a fungible-token standard that runs on the TRON Virtual Machine, not another name for TRX. In practical use, the difference is that TRX is used for protocol-layer resources, staking, and voting, while the issuance rules, supply, contract functions, and value of TRC-20 assets are determined by their respective contracts. Before sending or interacting, both the asset contract, network, and recipient support must be checked; they should not be treated as interchangeable merely because both are on the TRON network.

New TRX is created by the underlying protocol when Super Representatives produce blocks; ordinary users cannot mint it themselves. Each new block has two reward streams: a block-production reward paid to the SR that actually produces the block, and a voting reward allocated to the SR system that qualifies by voting weight, then distributed to voters under the relevant rules. Official documentation lists current per-block parameters of an 8 TRX block-production reward and a 128 TRX voting reward, but both can be adjusted through committee proposals. Voting rewards apply to the top 127 SRs (27 active SRs plus 100 SR Partners) and are allocated according to votes received; SRs first retain a share according to their brokerage rate, and voters then claim their accumulated portion.

When the bandwidth or energy required by a transaction cannot be covered by available resources, the protocol burns TRX to pay the corresponding cost; burned TRX is permanently removed from circulation. This mechanism both gives network operations a real cost to deter abuse and creates a supply-contraction force opposite to block rewards. The amount burned is not a fixed constant. It is affected by transaction and contract activity, resources available to or delegated to users, on-chain resource unit prices, and certain direct fees. Therefore, whether net deflation occurs on a given day requires comparing that day's burned amount with new block-reward issuance; total supply cannot be assumed to decline merely because a transaction or burn occurred.

TRON uses delegated proof of stake (DPoS). Users first stake TRX to obtain TP, then vote with TP; in each maintenance cycle, the 27 active Super Representatives for the next cycle are determined by votes, and active SRs then take turns producing blocks and validating transactions. Voting is therefore the link between token-holder staking and the selection of block producers. Whether voters receive rewards and the proportion received depend not only on the amount held or staked, but also on whether they vote for an SR with the relevant eligibility, that SR's vote count, and its set brokerage rate. Rewards received by SRs or their partners and their distribution rules may also change with on-chain parameters and SR policies, so voting rewards should not be considered a fixed-return commitment.

The smallest unit of TRX is lowercase sun: 1 TRX = 1,000,000 sun. Smart contracts, APIs, and underlying transaction fields often count in sun, so converting a human-readable TRX amount to the smallest unit requires multiplying by 1,000,000. For example, 10 TRX is represented as 10,000,000 sun in an interface; when displaying a balance in reverse, it should be divided by 1,000,000. Lowercase sun should be carefully distinguished from uppercase SUN: the latter is another TRC-20 governance token and has no asset relationship with TRX's smallest unit.

A TRX transfer requires first creating a TransferContract transaction, then signing it with the sending account's private key and broadcasting it to the network; the signature proves that the account authorizes the transfer from its own balance to the recipient address. Creating an unsigned transaction does not mean the transfer is complete; only on-chain processing after signing and broadcasting enters the execution process. When operating, check the recipient address, network, amount unit, and available resources or balance. Amounts are often represented in sun at the underlying layer, and insufficient resources may also cause TRX to be burned; once a private key or signing authority is used for a valid on-chain transaction sent to the wrong address, the network generally has no automatic reversal step.

Under application rules, TRX can serve as collateral, liquidity, and a fee-denomination asset in TRON DeFi; these application activities can also consume bandwidth, energy, or burn TRX through transfers and contract calls. Therefore, they may connect to network resource use and fee mechanisms, but this does not mean that all application use automatically creates the same level of TRX demand. For example, lending, decentralized trading, and stablecoin-related operations each rely on different contracts, collateral rules, and liquidity conditions. The smart-contract, liquidation, impermanent-loss, or asset-price risks users actually bear when participating are determined by application design; the safety or return of any specific application cannot be inferred directly from “TRX is the ecosystem's base asset.”

TRX supply is not a fixed-cap model; it is shaped by two tracks: increases from block-reward issuance and reductions from fee burning. New blocks continuously generate block-production and voting rewards; network operations burn TRX when resources are insufficient or direct fees are triggered. The net change for a period can be summarized as: Net supply change = newly minted TRX − burned TRX. When the amount burned exceeds the amount minted, TRX in circulation decreases on a net basis; otherwise, it increases on a net basis. Higher network activity may increase resource consumption and burns, but greater staking may also allow more accounts to cover transactions with resources and reduce burns; meanwhile, reward amounts and resource unit prices can be adjusted through governance. Therefore, this formula provides a framework for determining supply direction, not a guarantee of future deflation or price.