imtoken Knowledge Center
Layer 2 Basics
Layer 2 systems reduce execution cost in different ways, while bridging, cross-layer transfers and confirmations still require the correct path.
Why networks remain separate
Network selection determines where a transaction is submitted. Even when address formats look alike, chain state, gas, chain IDs and application ecosystems remain separate. In the context of Layer 2 Basics, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
Confirmations and on-chain verification
A block explorer can help verify transaction hashes, block heights, confirmation counts and contract addresses, making it a key tool for checking on-chain facts. In the context of Layer 2 Basics, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
Practical verification points
Gas, contracts and network parameters
Cross-chain and cross-layer transfers introduce bridges, contracts and additional waiting steps, so ordinary same-chain transfer assumptions do not always apply. In the context of Layer 2 Basics, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result. Movement between Layer 2 and the base layer commonly relies on bridge contracts or protocols. Timing may depend on sequencers, proof submission, withdrawal windows or third-party bridge design, so “successful on L2” does not always mean “available on mainnet.”
Additional risks in cross-chain and cross-layer flows
Network selection determines where a transaction is submitted. Even when address formats look alike, chain state, gas, chain IDs and application ecosystems remain separate. In the context of Layer 2 Basics, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
- Verify the active network and destination before confirming.
- Treat seed phrases and private keys as secret credentials.
- Review DApp, signature and approval requests independently.