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
中文Download
Practical Guide

Wallet Guides

This guide connects the practical decisions behind creation, import, and backup. It focuses on verifiable on-chain information, clear user actions, and security habits that remain useful even when interfaces change.

Download imtokenSecurity guide →
Before you begin

Use a fixed sequence for the goal, network, address and expected result instead of relying on defaults.

Before you begin

Prepare a check sequence before acting

Confirm the goal, account, network and expected result before you send, sign, connect or approve.

On this page
  1. Prepare before you start
  2. Understand creation and import
  3. Work through backup and receiving carefully
  4. Verify the on-chain result
  5. Troubleshooting common mistakes
  6. Good habits after the task is complete

Prepare before you start

Before using this wallet guides guide, identify the account, network, asset, and exact outcome you want. Similar-looking addresses do not make two networks interchangeable, and a wallet interface cannot automatically correct a transfer that was sent on the wrong chain; in Wallet Guides, read this specifically alongside “Prepare before you start” and creation. A clear task definition makes every later check more meaningful; in Wallet Guides, read this specifically alongside “Prepare before you start” and creation. If “Prepare before you start” is unclear, stop before approving and return to the basics of creation and import, then verify the result with a transaction hash, contract address or block record where applicable.

Understand creation and import

Start by understanding how creation and import affect the operation. Do not rely on a default network or an autofilled address for a high-value action; in Wallet Guides, read this specifically alongside “Understand creation and import” and import. Confirm the network, destination, token contract when relevant, and the account that will sign; in Wallet Guides, read this specifically alongside “Understand creation and import” and import. For a first-time workflow, a smaller test can help you understand the sequence, but the same checks are still required; in Wallet Guides, read this specifically alongside “Understand creation and import” and import. A durable routine for Wallet Guides is to make import a first-pass check, use backup as a second check, and rely on verifiable information related to receiving rather than interface assumptions.

Pre-action checklist
  • Confirm the intended account and network.
  • Verify the address, contract or DApp independently.
  • Know what will change after the request is confirmed.

Work through backup and receiving carefully

When you reach backup and receiving, read what the wallet is actually asking you to approve. A DApp connection is not blanket consent for later signatures; in Wallet Guides, read this specifically alongside “Work through backup and receiving carefully” and backup. If a contract, permission, amount, or destination differs from what you expected, cancel the step and restart from a trusted entry point instead of trying to “fix” an unclear request in place; in Wallet Guides, read this specifically alongside “Work through backup and receiving carefully” and backup. This part of Wallet Guides should be read together with the surrounding workflow: backup affects how you interpret receiving, while sending helps confirm the state after the action.

Verify the on-chain result

After submission, verify the result with the transaction hash rather than trusting only a success toast; in Wallet Guides, read this specifically alongside “Verify the on-chain result” and receiving. The explorer should show the network, sender, recipient, fee, status, and confirmation progress; in Wallet Guides, read this specifically alongside “Verify the on-chain result” and receiving. For steps involving sending, the process may include waiting periods or multiple stages, so the first wallet notification is not always the final on-chain state. For Wallet Guides, connect receiving with sending and transaction lookup; the important part is the relationship between those concepts and the on-chain evidence you can verify afterward.

Troubleshooting common mistakes

Common mistakes include the wrong network, a copied address error, an incorrect token contract, insufficient gas, duplicate submissions, and confusing a connection request with a transaction; in Wallet Guides, read this specifically alongside “Troubleshooting common mistakes” and sending. Troubleshoot in a fixed order: network, address, transaction hash, contract, then current status; in Wallet Guides, read this specifically alongside “Troubleshooting common mistakes” and sending. If transaction lookup looks unusual, first establish whether a transaction was actually broadcast. When working through “Troubleshooting common mistakes,” check the source, network, request details and resulting state in that order, with extra attention to sending and transaction lookup.

Good habits after the task is complete

Once the task is complete, disconnect DApps you no longer need and review approvals that may remain active; in Wallet Guides, read this specifically alongside “Good habits after the task is complete” and transaction lookup. Keep seed phrases and private keys offline and never send them through screenshots, cloud notes, or support chats; in Wallet Guides, read this specifically alongside “Good habits after the task is complete” and transaction lookup. Interfaces can change over time; a repeatable verification routine is more reliable than memorizing where a button used to be; in Wallet Guides, read this specifically alongside “Good habits after the task is complete” and transaction lookup. Do not treat an interface success message as the final answer for Wallet Guides. Use transaction lookup, creation and import to confirm that the expected change occurred on the intended network.

Security and risk reminder

Seed phrases and private keys are controlled by the user. imtoken will never ask for them. Blockchain transactions are generally irreversible by a wallet provider, and third-party DApps, smart contracts, network conditions and digital-asset prices can introduce additional risk.