An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Ethereum and Tron use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.
TRX is the native gas asset for Tron. Tron Base58Check address, commonly beginning with T A TRC-20 token transfer is not an ERC-20 transfer even when an asset ticker exists on both sides.
Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract. Verify the exact TRC-20 contract and the Ethereum representation independently.
Route-specific mistakes include sending on a network other than Ethereum; using a destination that is not valid for Tron; running out of ETH before the source transaction is submitted; assuming evm and other addresses are interchangeable. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
TRON is classified as a native asset for this route. TRX uses a network-specific contract asset on Ethereum. The recorded Ethereum representation uses 6 decimal places. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger.
XRP is classified as a native asset for this route. XRP uses a network-specific contract asset on Tron. The recorded Tron representation uses 6 decimal places. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Tron address, token-transfer, contract, and resource activity remain public. For this TRX on Ethereum to XRP on Tron path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Tron Base58Check address, commonly beginning with T; it does not hide either chain's public records.
The Tron side must match the TRC-20 contract or native TRX label shown in the route. The Ethereum side is a separate network representation.
TRX is a contract representation on Ethereum with 6 decimals at 0x50327c6c5a14DCaDE707ABad2E27eB517df87AB5. ETH, not TRX, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger.
XRP is a contract representation on Tron with 6 decimals at TTjWeVeYWjsMpoBAuBX6pHGMFPyCgjQctz. TRX, not XRP, pays gas unless both symbols are the same. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
TRX is the deposited native-asset input; XRP is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
ETH is the native gas asset for Ethereum. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. TRX is token-tracked and can need approval before transfer.
Requirements are checked for the live TRX Ethereum to XRP Tron quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.
