Arbitrum 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. ARB uses ARB 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 Arbitrum. ARB is contract-tracked and can require an allowance before transfer. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval.
Route-specific mistakes include sending on a network other than Arbitrum; 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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. 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.
Arbitrum is classified as a governance or utility token for this route. ARB uses a network-specific contract asset on Arbitrum. The Arbitrum side is contract-tracked rather than a native gas balance. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
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.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this ARB on Arbitrum 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.
ARB is a contract representation on Arbitrum at 0x912ce59144191c1204e64559fe8253a0e49e6548. ETH, not ARB, pays gas unless both symbols are the same. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
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.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. On receipt, Confirm receipt in HyperEVM rather than HyperCore or another Hyperliquid environment; the destination context determines whether HYPE is spendable gas.
ARB is the deposited token input; HYPE is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. 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 ARB Arbitrum 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.
