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 Knowledge Center

Getting Started

For first-time wallet users, understanding wallets, addresses, seed phrases, networks and gas matters more than rushing into a transfer.

Before you start

  • Use a trusted device and network environment.
  • Prepare an offline way to record necessary backup information.
  • Never send a seed phrase, private key or verification code to anyone.

Steps

01

Confirm the objective

Know whether you are creating, importing, receiving, sending or connecting to a DApp before you start confirming actions.

02

Check network and address

Verify the active network, destination and asset chain; use a block explorer when you need independent confirmation.

03

Review fees and permissions

For transfers, inspect gas and amount; for Web3, inspect signature details, contract and approval scope.

04

Verify after submission

Keep the transaction hash or operation record and verify status on the correct network rather than relying only on a pop-up message.

Common mistakes and checks

Start with foundational concepts

Learning is easier when you understand addresses, networks, gas and transaction hashes before moving into DApps and approvals. Each later action then has clearer context. In the context of Getting Started, 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.

Learn along the real user journey

The goal is not to memorize button positions, but to build transferable judgment: which chain am I on, who is asking for permission, and what will the transaction do? In the context of Getting Started, 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 outcomes with on-chain data

When something looks wrong, preserve the transaction hash, contract address and network details, then check a block explorer before deciding whether the issue is display-only or on-chain. In the context of Getting Started, 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.

Integrate security into every step

Learning is easier when you understand addresses, networks, gas and transaction hashes before moving into DApps and approvals. Each later action then has clearer context. In the context of Getting Started, 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.