imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken Knowledge

Multi-chain Networks

A practical guide to multi-chain networks with clear concepts, user checks and risk boundaries before wallet actions are confirmed.

On this page
  1. What multi-chain means
  2. The same address is not the same network
  3. Moving assets across networks
  4. Everyday checks

What multi-chain means

What multi-chain means is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

What multi-chain means is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Confirm the current account and network
  • Never share a seed phrase, private key or verification code
  • Read the full transfer, signature or approval request before confirming

The same address is not the same network

The same address is not the same network is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

The same address is not the same network is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Moving assets across networks

Moving assets across networks is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Moving assets across networks is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Everyday checks

Everyday checks is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Everyday checks is an essential part of understanding Multi-chain Networks. A network label in a wallet is only the user-facing entry point. The chain rules determine gas, confirmations, contract behavior and explorer records. Similar address formats do not make two networks interchangeable, and cross-layer or cross-network transfers can add bridge and timing risks. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear