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. BNB uses BNB contract token on the source; LINK uses LINK 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. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later. A compatible wallet may create or use an associated token account, and SOL—not LINK unless it is SOL—pays later Solana fees.
ETH is the native gas asset for Arbitrum. BNB 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. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Arbitrum. The recorded Arbitrum 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.
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Solana. The Solana side is contract-tracked rather than a native gas balance. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this BNB on Arbitrum to LINK 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.
BNB is a contract representation on Arbitrum with 18 decimals at 0x20865e63B111B2649ef829EC220536c82C58ad7B. ETH, not BNB, 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. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
LINK is a contract representation on Solana at LinkhB3afbBKb2EQQu7s7umdZceV3wcvAUJhQAfQ23L. SOL, not LINK, 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. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. On receipt, LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
BNB is the deposited native-asset input; LINK is the quoted token 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. 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. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Requirements are checked for the live BNB Arbitrum to LINK 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.
