StepsIdentify the networkUnderstand feesUse an explorerLayer 2 & compatible networks
  1. 01

    Identify the network

    Identify the network is a practical part of understanding Network Guides. Build a cross-network decision framework around network identity, gas, explorers, EVM environments and Layer 2. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    Identify the network within Network Guides is not an isolated feature. In practice it is shaped by network state, account permissions, transaction parameters and user decisions. Understanding those relationships first makes similar-looking screens and labels much less confusing.

    For Identify the network, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with identify the network
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  2. 02

    Understand fees

    Understand fees is a practical part of understanding Network Guides. Build a cross-network decision framework around network identity, gas, explorers, EVM environments and Layer 2. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    A useful way to think about Understand fees within Network Guides is to separate what the interface displays from what the blockchain records. The wallet organizes information and submits requests, while the target network records the resulting state. Addresses, networks, contracts and transaction hashes are therefore important verification points.

    For Understand fees, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with understand fees
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  3. 03

    Use an explorer

    Use an explorer is a practical part of understanding Network Guides. Build a cross-network decision framework around network identity, gas, explorers, EVM environments and Layer 2. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    The risky part of Use an explorer within Network Guides is often the surrounding context rather than the button itself: which network is active, which site initiated the request, what permission is being granted, and whether the amount and fee make sense. Turning those checks into a routine is more reliable than reacting to prompts one by one.

    For Use an explorer, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with use an explorer
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  4. 04

    Layer 2 & compatible networks

    Layer 2 & compatible networks is a practical part of understanding Network Guides. Build a cross-network decision framework around network identity, gas, explorers, EVM environments and Layer 2. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    imtoken guidance focuses on information you can verify. When something is unclear, do not rely on a single line in a pop-up. Check the address, network, contract, transaction history and explorer data where relevant, then decide whether the action matches your intent.

    For Layer 2 & compatible networks, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with layer 2 & compatible networks
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone

Related reading

Getting StartedNetwork GuidesSecurity