Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.
Hyperliquid (HyperEVM) is a L1 EVM network in the Hyperliquid ecosystem. HYPE pays destination-side network gas on Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance.
Hyperliquid is classified as a native asset for this route. HYPE uses a native asset on Hyperliquid (HyperEVM). Native HYPE exists on one recorded origin network; other network forms require representation checks. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays source-side network gas on BNB Chain. EVM 0x account address 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.
BNB Chain and Hyperliquid (HyperEVM) can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Route-specific mistakes include sending on a network other than BNB Chain; using a destination that is not valid for Hyperliquid (HyperEVM); running out of BNB before the source transaction is submitted. 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 SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public. For this SOL on BNB Chain to HYPE on Hyperliquid (HyperEVM) path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; confirm the destination is HyperEVM; it does not hide either chain's public records.
SOL is a contract representation on BNB Chain with 18 decimals at 0x570A5D26f7765Ecb712C0924E4De545B89fD43dF. BNB, not SOL, 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 SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.
HYPE is listed as the native representation on Hyperliquid (HyperEVM); HYPE is used for network gas. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. On receipt, Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
SOL is the deposited native-asset input; HYPE is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead. 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 HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
BNB is the native gas asset for BNB Chain. 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. SOL is token-tracked and can need approval before transfer.
Sending SOL on a network other than BNB Chain, or using an address that is not valid for Hyperliquid (HyperEVM), can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live SOL BSC to HYPE Hyperliquid 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.
