TRON (TRX)

Overview

TRON (TRX) is the native Coin of the TRON network. Accounts can hold and transfer TRX, stake it to obtain network resources and voting rights, and use it in smart-contract interactions. The smallest common denomination is the sun, with one TRX equal to one million sun.

TRON uses an account-based state model. An externally controlled account signs a transaction, which is broadcast, validated, executed, and included by block-producing Super Representatives. TRX transfers use a native transaction type, while token and smart-contract operations use different contract types.

Network resource consumption is expressed through Bandwidth and Energy. Accounts can obtain resources through staking or limited allowances. When resources are insufficient, TRX can be burned to pay the corresponding cost, so a transaction can require native TRX even when the user is moving a TRC-20 token.

Native TRX should be distinguished from contract-managed Token Transfer activity. A TRC-20 payment can emit event logs and consume Energy, while a simple TRX transfer uses the network’s native balance mechanism. Address representation can also appear as Base58Check or hexadecimal depending on the API.

Payment systems should verify network, address encoding, amount in sun, transaction type, execution result, and confirmed status. A successful transaction creation response is not a broadcast or final confirmation. Current OxaPay asset and network support should be retrieved dynamically before presenting TRX payment instructions.

TRON operations should also account for account activation and resource delegation. A destination that has not previously existed can create additional cost or behavior, and sponsored or delegated resources can make the fee payer differ from the economic sender. These details belong in support and reconciliation records.