BNB Chain to Sui: object and account boundary
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 coin-object and SUI gas requirements
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.
USDT input versus SUI output representation
The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.
Converting stablecoin USDT into SUI
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 source is a stablecoin contract or recorded native representation, while SUI is classified as native-asset. Check the quoted output rather than assuming a one-dollar source unit fixes the destination amount.
Mistakes specific to USDT BNB Chain to SUI Sui
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. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.
USDT input identity and handling
Tether is classified as a stablecoin for this route. USDT uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior.
SUI output identity and receiving
Sui is classified as a native asset for this route. SUI uses a native asset on Sui. The Sui side is contract-tracked rather than a native gas balance. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.