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 and practical checks

Wallet & Assets

A wallet is not a container for assets. It manages account control and helps you read, create and verify actions on the correct blockchain network.

Use the page as a decision guide: identify the network, account and request before signing or moving assets.
01Understand wallet control
02Addresses, accounts and networks
03Transfers and transaction records
04Long-term wallet habits
Wallet & Assets
01

Understand wallet control

A wallet proves account control through keys while balances and transaction history live on blockchain networks. Separating the interface from on-chain state helps diagnose display issues correctly.

02

Addresses, accounts and networks

The same account may show a similar address on several compatible networks, yet each network has its own balances, gas asset, contracts and transaction history. Network context comes first.

03

Transfers and transaction records

When receiving, verify the network and address. When sending, also verify amount and gas. After submission, use the transaction hash to review public on-chain status instead of relying on one interface message.

Long-term wallet habits

Review old DApp connections and approvals, keep devices current, and store seed phrases and private keys offline. Good wallet management is an ongoing verification habit, not a one-time setup.

Do not rely on a button label or a familiar-looking page as the reason to continue. Compare the request with the on-chain target, network state and expected result, and stop when those pieces do not line up.

Move from interface display to on-chain evidence

An asset list is the wallet's presentation of data for the selected network; it is not the asset itself. If a token is missing, first confirm the active network, then compare the token contract, account address, and balance shown by an explorer for that chain. A familiar token name is not enough to identify a contract, and similarly named assets on different networks should not be treated as the same record.

When you use multiple accounts, confirm which account is active after every account, network, or DApp switch. Rechecking the sender, recipient, and approval target prevents context from a previous action from carrying into the next one. Use public on-chain records as a verification layer alongside the wallet interface, especially when transaction status or token display appears delayed.

Practical checklist

  • Confirm that “Understand wallet control” matches the task you intend to perform
  • Confirm that “Addresses, accounts and networks” matches the task you intend to perform
  • Confirm that “Transfers and transaction records” matches the task you intend to perform
  • Confirm that “Long-term wallet habits” matches the task you intend to perform

Risk reminder

Seed phrases and private keys remain under the user’s control. Legitimate support should not ask for a seed phrase, private key or verification code. Review address, network and amount before transferring; blockchain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review spender and permission scope and consider revoking unused approvals.

Continue with imtoken

Use the unified download entry and review every network and permission request.

Download imtoken