What to Check Before Using a Crypto Bridge on Sui
Questions to ask about the route, token, destination chain, fees, and transaction details.
Why this matters on Sui
The most important bridge question is not 'does it work?' but 'what exactly will happen if I sign?' Read the route, source and destination assets, fees and recipient before approving.
Sui uses an object-centric model that differs from the account and token conventions of EVM networks.
Sui 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 Sui after confirming they are supported.
Sui: what to pay attention to
- Costs: Consider network transaction costs and route-specific costs when evaluating small balances.
- Security: Review transaction effects carefully and use trusted wallet interfaces.
- Assets and tokens: Verify the network-specific asset and object details rather than applying EVM assumptions.
A Sui checklist for this topic
- Check that the token you hold on Sui 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.
- Keep enough native balance on Sui to pay for the transaction that starts the transfer.
- Review the final recipient address and network before confirming a cross-chain transfer.
Bridge from Sui
Consider network transaction costs and route-specific costs when evaluating small balances. On the Aptos side: verify the network-specific asset representation and account details.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Sui → Aptos BRIDGE GUIDE