TRON Address

Overview

A TRON account address is based on a 21-byte network-prefixed value and is commonly shown as a Base58Check string beginning with T. APIs may also expose an equivalent hexadecimal representation.

Externally controlled accounts derive from public keys, while smart contracts receive addresses through deployment rules. Token balances belong to addresses but are tracked by protocol or contract state, so sending TRX and calling a TRC-20 contract are different transaction types. Wallets must validate checksum, network prefix, representation, and destination contract before signing. Developers should convert between Base58Check and hexadecimal using tested libraries rather than manual string edits. Address similarity does not prove recipient identity, and private keys or seed phrases must never be entered where only a public address is requested. Systems storing TRON Address should preserve the exact value together with chain identifiers and type metadata. Normalization, case conversion, truncation, and alias resolution need protocol-aware rules, because a visually similar value can represent a different destination or fail checksum validation.

Higher-value transfers benefit from an independent destination check rather than reliance on shortened display text. Testing for TRON Address should include valid and invalid examples, wrong-network values, boundary encodings, contract destinations, and any memo or tag requirements. TRON Address must be interpreted with its network, address or account type, encoding rules, and any required routing fields. A string that passes a format check can still belong to the wrong chain, unsupported asset, contract type, or destination that requires a memo or tag. Risk-control point: A TRON address identifies an account or contract, while checksum, representation, token type, and recipient identity require separate validation.