Sui to Solana: object and account boundary
A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Sui and Solana 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 HYPE 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. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
Converting stablecoin USDT into HYPE
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 HYPE 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 Sui to HYPE Solana
Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Solana; running out of SUI before the source transaction is submitted; assuming other and solana addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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 Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
USDT input identity and handling
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. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior.
HYPE output identity and receiving
Hyperliquid is classified as a native asset for this route. HYPE uses a network-specific contract asset on Solana. The recorded Solana representation uses 9 decimal places. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.