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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. BNB Chain and Sui use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.
SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Coin objects and Move types are not EVM token contracts.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
USDT is issued through ERC-20, TRC-20, SPL, and other network-specific contracts. The ticker does not determine the token standard, contract, issuer controls, or destination address model. The destination wallet must support the exact Sui representation. The route converts a native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
Route-specific mistakes include sending on a network other than BNB Chain; using a destination that is not valid for Sui; running out of BNB before the source transaction is submitted; assuming evm and other addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
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. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network.
Tether is classified as a stablecoin for this route. USDT uses a network-specific contract asset on Sui. The recorded Sui representation uses 6 decimal places. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this XRP on BNB Chain to USDT on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Sui hexadecimal account address with an object-based asset model; it does not hide either chain's public records.
Sui uses Move coin types and objects with SUI gas. The other side follows EVM execution, so addresses and token identifiers are not interchangeable.
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.
USDT is a contract representation on Sui with 6 decimals at 0xc060006111016b8a020ad5b33834984a437aaa7d3c74c18e09a95d48aceab08c::coin::COIN. SUI, not USDT, pays gas unless both symbols are the same. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. On receipt, Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
XRP is the deposited native-asset input; USDT is the quoted stablecoin 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 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Confirm whether the output is ERC-20, TRC-20, SPL, or another USDT standard; a wallet supporting one standard may not credit another.
USDT must match the quoted Sui representation. A ticker or target price is not enough to identify a token contract.
Requirements are checked for the live XRP BSC to USDT Sui 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.
