Why Token Support Differs by Network on Gnosis
Why the same ticker can represent different contracts and why chain selection matters.
Why this matters on Gnosis
The same ticker can exist as multiple contracts on multiple networks. Network-specific contract verification prevents one of the most common cross-chain mistakes.
Gnosis provides an EVM-compatible environment with its own network balances and application ecosystem.
Gnosis uses EVM-style addresses and token contracts, which means the same address can hold balances on several EVM networks at once. A balance that is missing on Gnosis may simply be sitting on a different network.
Gnosis: what to pay attention to
- Costs: Compare transaction costs with bridge and destination costs.
- Security: Review approvals and transaction details before signing.
- Assets and tokens: Verify the token contract on Gnosis.
A Gnosis checklist for this topic
- Confirm both the source and destination network, including whether Gnosis is one of them.
- Compare the quote, the minimum received amount and the total fees before signing.
- Check that the token you hold on Gnosis 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 Gnosis
Compare transaction costs with bridge and destination costs. On the Metis side: verify the token contract on Metis.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Gnosis → Metis BRIDGE GUIDE