BNB is classified as a native asset for this route. BNB uses a native asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. The destination wallet must support the exact Hyperliquid (HyperEVM) representation. The route converts a native-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Hyperliquid (HyperEVM). The Hyperliquid (HyperEVM) side is contract-tracked rather than a native gas balance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
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.
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.
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; 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 BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
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 BNB on BNB Chain to USDC 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.
BNB is listed as the native representation on BNB Chain; BNB is used for network gas. 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 BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
USDC is a contract representation on Hyperliquid (HyperEVM) at 0xb88339cb7199b77e23db6e890353e22632ba630f. HYPE, not USDC, pays gas unless both symbols are the same. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. On receipt, The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
BNB is the deposited native-asset input; USDC is the quoted stablecoin output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
USDC must match the quoted Hyperliquid (HyperEVM) representation. A ticker or target price is not enough to identify a token contract.
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. BNB is recorded as native on this source.
Requirements are checked for the live BNB BSC to USDC 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.
