Bridge Aggregators Explained on Sui
Learn how bridge aggregators compare routes and why quotes, liquidity, fees, and execution details matter.
Why this matters on Sui
Bridge aggregators compare routes rather than making every route identical. A good comparison still requires checking the provider, route, fees, liquidity, execution details and final amount.
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
- Compare the quote, the minimum received amount and the total fees before signing.
- 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.
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