Direction
BNB Chain → Tron
Asset
XRP
Source gas
BNB
Destination gas
TRX
Choose the XRP asset and BNB Chain network you currently hold.
Check the estimated output, fees, timing, and Tron destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
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.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. 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.
XRP is classified as a native asset for this route. XRP uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. The BNB Chain side is contract-tracked rather than a native gas balance. Native XRP exists on one recorded origin network; other network forms require representation checks. 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. The Tron side is contract-tracked rather than a native gas balance. Native XRP exists on one recorded origin network; other network forms require representation checks. XRP leaves as a network-specific contract asset. XRP arrives as a network-specific contract asset.
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. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. 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 Chain wallet, token-transfer, contract, log, and gas activity remain public, and Tron address, token-transfer, contract, and resource activity remain public. For this XRP 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.
Tron is the Tron side. Match its Tron address and exact TRC-20 contract; the other network representation is separate.
XRP is a contract representation on BNB Chain with 18 decimals at 0x1D2F0da169ceB9fC7B3144628dB156f3F6c60dBE. BNB, not XRP, 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. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network.
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.
No. This bridge keeps the asset intent while moving between a XRP contract token and a XRP contract token. Match the source and output details in the live quote.
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. The bridge output does not automatically fund every later gas need.
Tron Base58Check address, commonly beginning with T Do not substitute a BNB Chain address merely because a wallet displays both networks.
Sending on a network other than BNB Chain, selecting a representation not listed by the quote, or entering an address invalid for Tron can prevent normal detection or receipt.
Requirements are checked for the live XRP BNB Chain to 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.
