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
中文Download
Practical Guide

Network Guides

This guide connects the practical decisions behind public chains, EVM, and Layer 2. It focuses on verifiable on-chain information, clear user actions, and security habits that remain useful even when interfaces change.

Download imtokenSecurity guide →
Before you begin

Use a fixed sequence for the goal, network, address and expected result instead of relying on defaults.

Before you begin

Prepare a check sequence before acting

Confirm the goal, account, network and expected result before you send, sign, connect or approve.

On this page
  1. Prepare before you start
  2. Understand public chains and EVM
  3. Work through Layer 2 and gas carefully
  4. Verify the on-chain result
  5. Troubleshooting common mistakes
  6. Good habits after the task is complete

Prepare before you start

Before using this network guides guide, identify the account, network, asset, and exact outcome you want. Similar-looking addresses do not make two networks interchangeable, and a wallet interface cannot automatically correct a transfer that was sent on the wrong chain; in Network Guides, read this specifically alongside “Prepare before you start” and public chains. A clear task definition makes every later check more meaningful; in Network Guides, read this specifically alongside “Prepare before you start” and public chains. A durable routine for Network Guides is to make public chains a first-pass check, use EVM as a second check, and rely on verifiable information related to Layer 2 rather than interface assumptions.

Understand public chains and EVM

Start by understanding how public chains and EVM affect the operation. Do not rely on a default network or an autofilled address for a high-value action; in Network Guides, read this specifically alongside “Understand public chains and EVM” and EVM. Confirm the network, destination, token contract when relevant, and the account that will sign; in Network Guides, read this specifically alongside “Understand public chains and EVM” and EVM. For a first-time workflow, a smaller test can help you understand the sequence, but the same checks are still required; in Network Guides, read this specifically alongside “Understand public chains and EVM” and EVM. This part of Network Guides should be read together with the surrounding workflow: EVM affects how you interpret Layer 2, while gas helps confirm the state after the action.

Pre-action checklist
  • Confirm the intended account and network.
  • Verify the address, contract or DApp independently.
  • Know what will change after the request is confirmed.

Work through Layer 2 and gas carefully

When you reach Layer 2 and gas, read what the wallet is actually asking you to approve. A DApp connection is not blanket consent for later signatures; in Network Guides, read this specifically alongside “Work through Layer 2 and gas carefully” and Layer 2. If a contract, permission, amount, or destination differs from what you expected, cancel the step and restart from a trusted entry point instead of trying to “fix” an unclear request in place; in Network Guides, read this specifically alongside “Work through Layer 2 and gas carefully” and Layer 2. For Network Guides, connect Layer 2 with gas and blockchain explorers; the important part is the relationship between those concepts and the on-chain evidence you can verify afterward.

Verify the on-chain result

After submission, verify the result with the transaction hash rather than trusting only a success toast; in Network Guides, read this specifically alongside “Verify the on-chain result” and gas. The explorer should show the network, sender, recipient, fee, status, and confirmation progress; in Network Guides, read this specifically alongside “Verify the on-chain result” and gas. For steps involving blockchain explorers, the process may include waiting periods or multiple stages, so the first wallet notification is not always the final on-chain state; in Network Guides, read this specifically alongside “Verify the on-chain result” and gas. When working through “Verify the on-chain result,” check the source, network, request details and resulting state in that order, with extra attention to gas and blockchain explorers.

Troubleshooting common mistakes

Common mistakes include the wrong network, a copied address error, an incorrect token contract, insufficient gas, duplicate submissions, and confusing a connection request with a transaction; in Network Guides, read this specifically alongside “Troubleshooting common mistakes” and blockchain explorers. Troubleshoot in a fixed order: network, address, transaction hash, contract, then current status; in Network Guides, read this specifically alongside “Troubleshooting common mistakes” and blockchain explorers. If network switching looks unusual, first establish whether a transaction was actually broadcast. Do not treat an interface success message as the final answer for Network Guides. Use blockchain explorers, network switching and public chains to confirm that the expected change occurred on the intended network.

Good habits after the task is complete

Once the task is complete, disconnect DApps you no longer need and review approvals that may remain active; in Network Guides, read this specifically alongside “Good habits after the task is complete” and network switching. Keep seed phrases and private keys offline and never send them through screenshots, cloud notes, or support chats; in Network Guides, read this specifically alongside “Good habits after the task is complete” and network switching. Interfaces can change over time; a repeatable verification routine is more reliable than memorizing where a button used to be; in Network Guides, read this specifically alongside “Good habits after the task is complete” and network switching. If “Good habits after the task is complete” is unclear, stop before approving and return to the basics of network switching and public chains, then verify the result with a transaction hash, contract address or block record where applicable.

Security and risk reminder

Seed phrases and private keys are controlled by the user. imtoken will never ask for them. Blockchain transactions are generally irreversible by a wallet provider, and third-party DApps, smart contracts, network conditions and digital-asset prices can introduce additional risk.