Ethereum uses EVM account addresses and ETH for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. SOL uses SOL contract token on the source; HYPE uses HYPE contract token on Solana.
Base58-encoded Solana account address 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. A compatible wallet may create or use an associated token account, and SOL—not HYPE unless it is SOL—pays later Solana fees.
ETH is the native gas asset for Ethereum. SOL is contract-tracked and can require an allowance before transfer. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.
Route-specific mistakes include sending on a network other than Ethereum; using a destination that is not valid for Solana; running out of ETH before the source transaction is submitted; assuming evm and solana addresses are interchangeable. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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 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.
Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Ethereum. The recorded Ethereum representation uses 9 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 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.
Ethereum wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this SOL on Ethereum to HYPE on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana account address; it does not hide either chain's public records.
No. The destination must be a Solana-compatible address. Base58-encoded Solana account address
An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.
SOL is a contract representation on Ethereum with 9 decimals at 0xD31a59c85aE9D8edEFeC411D448f90841571b89c. ETH, not SOL, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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 a contract representation on Solana with 9 decimals at 98sMhvDwXj1RQi5c5Mndm3vPe9cBqPrbLaufMXFNMh5g. SOL, not HYPE, pays gas unless both symbols are the same. 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.
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. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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.
Requirements are checked for the live SOL Ethereum to HYPE Solana 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.
