Privacy for the Tron to Sui direction
Where offered, Private Route is intended to reduce an obvious direct association between the Tron sending wallet and Sui receiving wallet; it does not hide either blockchain. TRX is the native gas asset for Tron. Tron Base58Check address, commonly beginning with T SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Similar amounts, timing, address reuse, and later consolidation can still add association signals. Identity requirements must be checked separately.
Tron source-side visibility
Tron can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses the TVM account model with bandwidth and energy resource accounting. TRC-20 contracts and Tron addresses are not ERC-20 contracts or EVM 0x destinations, and TRX covers resource or fee requirements. The source deposit, gas funding, asset representation, confirmations, and sending-address history remain outside any promise of invisibility.
Sui destination-side visibility
Sui can expose addresses or accounts, transfers, amounts, fees, and timing according to its other transaction model. It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. The destination delivery and later activity can remain observable even when the provider path reduces a direct association.
Tron deposit role versus Sui receipt role
A Tron source uses a T-address plus bandwidth and energy accounting; TRX covers resource or fee needs for native or TRC-20 transfer execution. Those deposit-side events remain public. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. The receipt and later activity remain public.
TRC-20 or TRX records remain visible
The Tron side can expose T-address activity, TRC-20 events, resource use, amount, and timing. The Sui side maintains a separate ledger record and token representation.
Cross-chain linkability limits
Private routing can reduce direct association across the Tron and other-network accounts. T-address activity, TRC-20 events, resource use, the other ledger receipt, amounts, and timing remain observable. A Tron source uses a T-address plus bandwidth and energy accounting; TRX covers resource or fee needs for native or TRC-20 transfer execution. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance.
Verification status is separate from privacy status
The provider must support the exact native or TRC-20 side plus the other network representation. Amount, region, risk controls, and current policy can trigger verification even when a privacy route is offered. A Tron source uses a T-address plus bandwidth and energy accounting; TRX covers resource or fee needs for native or TRC-20 transfer execution. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance.
