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.

EVM Networks

Learn EVM, addresses, Gas, contracts, tokens and approvals with practical security checks and on-chain verification guidance.

Core concept

The EVM is a smart-contract execution environment used by Ethereum and many compatible networks. Similar address formats improve wallet compatibility but do not move assets between chains.

EVM Networks 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 EVM, addresses, Gas, contracts, tokens and approvals makes it easier to separate interface messages from actual on-chain state.

Operating sequence

EVM transactions consume Gas for computation and storage. Fees depend on network conditions, Gas settings and transaction complexity, and contract calls can cost more than simple transfers.

For EVM, addresses, Gas, contracts, tokens and approvals, use a deliberate sequence: verify the entry point, confirm the network, check the address or contract, review the exact request, then submit. For asset movement, also verify the amount, fee and transaction hash. For DApps, distinguish connection, message signatures, transaction signatures and token approvals because they create different permissions.

Common mistakes and verification

Tokens are commonly represented by contracts. A DApp may request permission for a contract to spend a defined token amount. An approval is not itself a transfer, but it can create ongoing permission.

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 EVM, addresses, Gas, contracts, tokens and approvals with verifiable data such as transaction hashes, block heights, address history and contract addresses instead of relying only on interface messages.

Security and risk boundary

Before confirming, check the network, contract address, requested method and approval scope. Consider revoking permissions that are no longer needed.

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.