Why Token Support Differs by Network on Starknet
Why the same ticker can represent different contracts and why chain selection matters.
Why this matters on Starknet
The same ticker can exist as multiple contracts on multiple networks. Network-specific contract verification prevents one of the most common cross-chain mistakes.
Starknet uses its own account and smart-contract environment, which differs from standard EVM networks.
Starknet 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 Starknet after confirming they are supported.
Starknet: what to pay attention to
- Costs: Check the current network cost and route mechanics before moving small balances.
- Security: Do not assume EVM contract and wallet conventions apply directly.
- Assets and tokens: Verify Starknet-specific asset and account details.
A Starknet checklist for this topic
- Confirm both the source and destination network, including whether Starknet is one of them.
- Compare the quote, the minimum received amount and the total fees before signing.
- Check that the token you hold on Starknet 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 Starknet
Check the current network cost and route mechanics before moving small balances. On the Zora side: verify the token contract on Zora.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Starknet → Zora BRIDGE GUIDE