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 logoimtoken
中文Download

Step-by-step Guide

Wallet Guides

A practical imtoken guide to wallet guides, including core concepts, verification steps and risk-aware usage.

Before you start

Confirm the account, network and intended destination. Keep seed phrases and private keys offline and never provide them to another person.

  1. 01

    Core concepts

    After a Wallet Guides task is completed, review receive and send to make sure the outcome matches the intent. Long-lived approvals and persistent connections should be revisited periodically. Good wallet hygiene is a repeated process of checking critical details and retaining traceable on-chain information, not a one-time setting.

    For create, first define its role in the current task, then check whether import and back up are consistent. When receive is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For send, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

    • Confirm: create
    • Cross-check: import and back up
    • Review carefully: receive
    • Verify afterward: send
  2. 02

    Checks before you act

    To understand Wallet Guides, treat import and back up as parts of the same on-chain workflow. The interface is only the entry point; the selected network, current chain state and permission scope determine what actually happens. Confirm the destination, source and network before continuing so the meaning of the request stays clear.

    For import, first define its role in the current task, then check whether back up and receive are consistent. When send is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For create, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

    • Confirm: import
    • Cross-check: back up and receive
    • Review carefully: send
    • Verify afterward: create
  3. 03

    How to evaluate a live request

    back up rarely appears in isolation. It often intersects with receive and send. A useful pattern is to separate each action into four checks: identify the object, verify the network, review permissions, and confirm the result. If one of those checks cannot be completed, stop and verify rather than relying on an unfamiliar site or remote instructions.

    For back up, first define its role in the current task, then check whether receive and send are consistent. When create is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For import, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

    • Confirm: back up
    • Cross-check: receive and send
    • Review carefully: create
    • Verify afterward: import
  4. 04

    Risks and boundaries

    When using imtoken for Wallet Guides, prioritize information that can be independently verified, such as addresses, network names, contract addresses, transaction hashes and block-explorer records. Visual design, urgency messages or claims from an unknown support account are not substitutes for verifiable on-chain details.

    For receive, first define its role in the current task, then check whether send and create are consistent. When import is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For back up, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

    • Confirm: receive
    • Cross-check: send and create
    • Review carefully: import
    • Verify afterward: back up
  5. 05

    How to verify the outcome

    From a risk perspective, import and back up deserve an independent review. Once a transaction is confirmed on-chain, a wallet normally cannot reverse it unilaterally. DApps and smart contracts can also introduce permission and contract risks, so every signature, approval and transfer should be understood before it is accepted.

    For send, first define its role in the current task, then check whether create and import are consistent. When back up is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For receive, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

    • Confirm: send
    • Cross-check: create and import
    • Review carefully: back up
    • Verify afterward: receive

Final checks

  • Never share your seed phrase, private key or verification code.
  • Verify the address, network and amount before sending.
  • Review each DApp signature and token approval independently.
  • Use transaction hashes and block explorers to verify on-chain status.
  • Revoke approvals and disconnect sessions that are no longer needed.