Why Token Support Differs by Network on Solana
Why the same ticker can represent different contracts and why chain selection matters.
Why this matters on Solana
The same ticker can exist as multiple contracts on multiple networks. Network-specific contract verification prevents one of the most common cross-chain mistakes.
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: 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
- Confirm both the source and destination network, including whether Solana is one of them.
- Compare the quote, the minimum received amount and the total fees before signing.
- Check that the token you hold on Solana is supported for the route you are considering.
- Allow for a delay between sending and receiving; do not repeat a transfer while one is pending.
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.
Solana → zkSync BRIDGE GUIDE