Account identity
Aperture derives and validates the public account under TRON rules. It does not assign a generic address from another network family.
Supported production mainnet
TRON in Aperture.
A network-aware home for TRX—with TRON addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
TRON is not just a ticker.
TRON is an account-based smart-contract network with its own address encoding and resource system. Transactions can consume bandwidth and smart-contract execution can consume energy.
Address format. A TRON account is commonly shown as a Base58Check value beginning with T.
A 0x-style hexadecimal value may represent the same underlying account bytes, but use the TRON address Aperture presents for TRON transfers.
Native asset and tokens
TRX is the native asset. TRC-20 tokens are identified by their TRON contract addresses, so an Ethereum token contract or matching ticker does not identify the TRON asset.
Fees and transaction state
TRX can cover network resource costs when available bandwidth or energy is insufficient. A broadcast transaction should be followed through inclusion and confirmation rather than treated as complete at submission.
Mainnet boundary
This catalog entry is TRON mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.
Receive safely
The network is part of the address.
In Aperture, choose TRON and the exact asset before copying an address or QR code. The sender, exchange, or bridge must use the same mainnet. A matching symbol, logo, or familiar-looking string does not prove compatibility.
- Confirm the receive screen says TRON.
- Copy or scan the complete address; do not retype it.
- Check whether the sending service requires an additional memo, tag, or network-specific field.
- For a new route or meaningful amount, consider a small test transfer first.
- Keep the receive screen available until the sender has verified the same network.
Send deliberately
Review what the signature will authorize.
Aperture keeps asset selection, recipient validation, amount, fee review, authorization, broadcast, and finality as distinct stages. Before authorizing a transaction on TRON, review the full recipient, the TRX amount, and the network fee together.
Blockchain transfers may be irreversible. Aperture cannot cancel a confirmed transaction, recover an incorrect destination, or move an asset that was sent through the wrong network.
Transaction signing happens on the device. Public account data, fee requests, transaction history, and the signed transaction may reach network infrastructure; the private signing key is not part of the broadcast payload.
Verify independently
Use the right source for the right question.
Network documentationUnderstand TRON protocol rules
Public block explorerInspect TRON public chain state
Aperture JournalHow accounts and networks stay separate
Aperture JournalReceive crypto safely in Aperture
External documentation and explorers are independent public resources. Their availability, labels, and data are not controlled by Aperture.
Aperture for iPhone and iPad
One interface. 25 mainnets. No blurred boundaries.
Use TRON alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.