Solana Wallets and the Avalanche to Arbitrum Route

Why this matters on Solana

Avalanche and Arbitrum have different network conditions and asset representations. Compare the route, destination token, and total cost before moving small balances.

Solana uses a different account and token model from EVM networks, so EVM assumptions should not be applied directly.

Solana does not follow standard EVM conventions. Address formats, token identifiers and approval mechanics differ, so EVM-oriented checklists and tools should only be applied to Solana after confirming they are supported.

Solana and this route

Solana is neither end of the Avalanche to Arbitrum route, but a wallet that uses Solana often holds balances on those networks too. If your assets are on Solana, they would first have to be on Avalanche for this route to apply.

Leaving Avalanche

Compare Avalanche transaction costs with route and destination costs before consolidating small balances. Confirm the network and contract before interacting with unfamiliar assets.

Arriving on Arbitrum

Confirm the Arbitrum token contract rather than assuming an identical ticker represents the same asset everywhere. Compare L2 transaction costs with any bridge or liquidity costs required to reach the destination.

Solana: what to pay attention to

• Costs: Consider transaction costs and token-account mechanics when evaluating small balances.
• Security: Use trusted wallet interfaces and review transaction effects before approving them.
• Assets and tokens: Verify the mint address and relevant token-account details rather than relying on ticker symbols.

A Solana checklist for this topic

• Do not assume a route from Solana is available; check the current interface and quote.
• Send a small test amount first if the route or address is new to you.
• Confirm that the token you hold on Solana is supported for the route you are reading about.
• Verify the source network, the destination network and the destination address before signing.

Bridge from Solana

Consider transaction costs and token-account mechanics when evaluating small balances. On the zkSync side: verify the asset contract on zkSync before assuming it matches another network.

The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.

Related guides