A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Sui and BNB Chain 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 ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for BNB Chain; running out of SUI before the source transaction is submitted; assuming other and evm addresses are interchangeable. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Ethereum is classified as a native asset for this route. ETH uses a network-specific contract asset on Sui. The recorded Sui representation uses 8 decimal places. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.
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 Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Sui account, object, transaction-effect, and fee activity remain public, and BNB Chain wallet, token-transfer, contract, log, and gas activity remain public. For this ETH on Sui to XRP on BNB Chain path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Sui hexadecimal account address with an object-based asset model and destination-side EVM 0x account address; 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.
ETH is a contract representation on Sui with 8 decimals at 0xd0e89b2af5e4910726fbcd8b8dd37bb79b29e5f83f7491bca830e94f7f226d29::eth::ETH. SUI, not ETH, pays gas unless both symbols are the same. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.
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 receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. On receipt, 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 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 ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
SUI is the native gas asset for Sui. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. ETH is token-tracked and can need approval before transfer.
Requirements are checked for the live ETH Sui to XRP BSC 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.
