Why Token Support Differs by Network on Sui
Why the same ticker can represent different contracts and why chain selection matters.
Why this matters on Sui
The same ticker can exist as multiple contracts on multiple networks. Network-specific contract verification prevents one of the most common cross-chain mistakes.
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
- 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.
- Confirm both the source and destination network, including whether Sui is one of them.
- Compare the quote, the minimum received amount and the total fees before signing.
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