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 Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. Tron and Base 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 XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees. Verify the exact TRC-20 contract and the Base representation independently.
Route-specific mistakes include sending on a network other than Tron; using a destination that is not valid for Base; running out of TRX before the source transaction is submitted; assuming other and evm addresses are interchangeable. 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. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
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 sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network.
Ethereum is classified as a native asset for this route. ETH uses a native asset on Base. The recorded Base representation uses 18 decimal places. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Tron address, token-transfer, contract, and resource activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this XRP on Tron to ETH on Base path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Tron Base58Check address, commonly beginning with T and destination-side EVM 0x account address; 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 Base side is a separate network representation.
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 source uses a T-address plus bandwidth and energy accounting; TRX covers resource or fee needs for native or TRC-20 transfer execution. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network.
ETH is listed as the native representation on Base; ETH is used for network gas. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. On receipt, Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
XRP is the deposited native-asset input; ETH is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. 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 Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
TRX is the native gas asset for Tron. 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. XRP is token-tracked and can need approval before transfer.
Requirements are checked for the live XRP Tron to ETH Base 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.
