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

Layer 2 Basics

A practical guide to layer 2 basics with clear concepts, user checks and risk boundaries before wallet actions are confirmed.

On this page
  1. Layer 2 and mainnet
  2. Moving between layers
  3. Bridges and arrival states
  4. Choosing a network

Layer 2 and mainnet

Layer 2 and mainnet is an essential part of understanding Layer 2 Basics. 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.

Layer 2 and mainnet is an essential part of understanding Layer 2 Basics. 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

Moving between layers

Moving between layers is an essential part of understanding Layer 2 Basics. 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.

Moving between layers is an essential part of understanding Layer 2 Basics. 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

Bridges and arrival states

Bridges and arrival states is an essential part of understanding Layer 2 Basics. 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.

Bridges and arrival states is an essential part of understanding Layer 2 Basics. 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

Choosing a network

Choosing a network is an essential part of understanding Layer 2 Basics. 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.

Choosing a network is an essential part of understanding Layer 2 Basics. 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