Sui → Polygon
Network-specific checks before a cross-chain transaction.
Sui 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
Sui: Sui uses an object-centric model that differs from the account and token conventions of EVM networks.
Polygon: Polygon provides an EVM-compatible environment with its own network balances and token representations.
On the source side, Verify the network-specific asset and object details rather than applying EVM assumptions. On the destination side, Confirm that the token is held on Polygon and verify its contract before moving or swapping it.
Consider network transaction costs and route-specific costs 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 Sui.
- 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: Review transaction effects carefully and use trusted wallet interfaces. 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