Solana → Polygon
Network-specific checks before a cross-chain transaction.
Solana and Polygon have separate network contexts. A cross-chain route must account for the source environment, destination environment and the mechanism used to transfer or represent the asset.
Route Intelligence
Solana: Solana uses a different account and token model from EVM networks, so EVM assumptions should not be applied directly.
Polygon: Polygon provides an EVM-compatible environment with its own network balances and token representations.
On the source side, Verify the mint address and relevant token-account details rather than relying on ticker symbols. On the destination side, Confirm that the token is held on Polygon and verify its contract before moving or swapping it.
Consider transaction costs and token-account mechanics when evaluating small balances. On Polygon, Compare Polygon transaction costs with bridge and liquidity costs when consolidating small balances.
Before You Bridge
- Source: confirm the asset is actually held on Solana.
- Destination: confirm the wallet and destination network.
- Token: verify the exact asset representation rather than relying on ticker or logo.
- Costs: compare gas, bridge fees, liquidity, price impact and the final received amount.
- Security: Use trusted wallet interfaces and review transaction effects before approving them. At the destination, Check network selection and contract addresses before signing, especially when an asset also exists on Ethereum.
Use the Live Bridge Tool
When a live route is available, open Dust Sweeper and review the current quote immediately before signing. Route availability, liquidity and network conditions can change.
OPEN BRIDGE TOOL