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.

Network Guides

Learn network selection, Gas, block confirmations, EVM and Layer 2 with practical security checks and on-chain verification guidance.

Before you start

Network Guides should be understood in the broader wallet and on-chain context. Identify the asset, network and controlling address, then determine whether the next step creates a connection, signature, approval or transaction. A clear model of network selection, Gas, block confirmations, EVM and Layer 2 makes it easier to separate interface messages from actual on-chain state.

Step-by-step workflow

Confirm the entry point

Use a trusted page or saved entry point and check the domain.

Confirm network and account

Make sure the active network and selected account match the task.

Review address, contract or request

Check the destination, contract and permission scope before signing.

Submit and verify

After submission, use the transaction hash or session state to verify the result.

Common mistakes

Common mistakes include using the wrong network, copying a bad address, ignoring token contracts, treating pending transactions as failures, or accepting an unclear approval. Troubleshoot network selection, Gas, block confirmations, EVM and Layer 2 with verifiable data such as transaction hashes, block heights, address history and contract addresses instead of relying only on interface messages.

Common mistakes include using the wrong network, copying a bad address, ignoring token contracts, treating pending transactions as failures, or accepting an unclear approval. Troubleshoot network selection, Gas, block confirmations, EVM and Layer 2 with verifiable data such as transaction hashes, block heights, address history and contract addresses instead of relying only on interface messages.

Security checklist

Seed phrases and private keys should remain under the user’s control. Official support should not request them, and verification codes should never be shared. Third-party DApps, smart contracts and network services can introduce risk. Because confirmed transactions are usually not reversible by the wallet alone, pre-signing checks are essential.

  • Keep recovery material offline
  • Verify network and destination
  • Read each signature independently
  • Check token approval scope
  • Verify the final state on-chain