Why Token Support Differs by Network on Aptos
Why the same ticker can represent different contracts and why chain selection matters.
Why this matters on Aptos
The same ticker can exist as multiple contracts on multiple networks. Network-specific contract verification prevents one of the most common cross-chain mistakes.
Aptos uses the Move ecosystem and has asset conventions that differ from EVM networks.
Aptos 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 Aptos after confirming they are supported.
Aptos: what to pay attention to
- Costs: Compare network costs with any route or destination costs before moving small balances.
- Security: Confirm the destination and transaction effects before signing.
- Assets and tokens: Verify the network-specific asset representation and account details.
A Aptos checklist for this topic
- Confirm both the source and destination network, including whether Aptos is one of them.
- Compare the quote, the minimum received amount and the total fees before signing.
- Check that the token you hold on Aptos 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.
Bridge from Aptos
Compare network costs with any route or destination costs before moving small balances. On the Fantom side: verify the token contract on the selected Fantom network.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Aptos → Fantom BRIDGE GUIDE