A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. 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. BNB Chain 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.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. 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 BNB Chain representation independently.
Route-specific mistakes include sending on a network other than BNB Chain; using a destination that is not valid for Tron; running out of BNB before the source transaction is submitted; assuming evm and other addresses are interchangeable. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. 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.
Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
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.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and Tron address, token-transfer, contract, and resource activity remain public. For this AVAX on BNB Chain 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 BNB Chain side is a separate network representation.
AVAX is a contract representation on BNB Chain with 18 decimals at 0x1CE0c2827e2eF14D5C4f29a091d735A204794041. BNB, not AVAX, pays gas unless both symbols are the same. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
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.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
AVAX 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.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. 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.
BNB is the native gas asset for BNB Chain. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. AVAX is token-tracked and can need approval before transfer.
Requirements are checked for the live AVAX BSC 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.
