StepsBefore you startCreate or importOffline backupRecovery practice
  1. 01

    Before you start

    Before you start is a practical part of understanding Create & Backup. After creating or importing a wallet, the priority is to verify your backup method and protect critical credentials. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    imtoken guidance focuses on information you can verify. When something is unclear, do not rely on a single line in a pop-up. Check the address, network, contract, transaction history and explorer data where relevant, then decide whether the action matches your intent.

    For Before you start, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with before you start
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  2. 02

    Create or import

    Create or import is a practical part of understanding Create & Backup. After creating or importing a wallet, the priority is to verify your backup method and protect critical credentials. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    Create or import within Create & Backup is not an isolated feature. In practice it is shaped by network state, account permissions, transaction parameters and user decisions. Understanding those relationships first makes similar-looking screens and labels much less confusing.

    For Create or import, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with create or import
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  3. 03

    Offline backup

    Offline backup is a practical part of understanding Create & Backup. After creating or importing a wallet, the priority is to verify your backup method and protect critical credentials. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    A useful way to think about Offline backup within Create & Backup is to separate what the interface displays from what the blockchain records. The wallet organizes information and submits requests, while the target network records the resulting state. Addresses, networks, contracts and transaction hashes are therefore important verification points.

    For Offline backup, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with offline backup
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  4. 04

    Recovery practice

    Recovery practice is a practical part of understanding Create & Backup. After creating or importing a wallet, the priority is to verify your backup method and protect critical credentials. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    The risky part of Recovery practice within Create & Backup is often the surrounding context rather than the button itself: which network is active, which site initiated the request, what permission is being granted, and whether the amount and fee make sense. Turning those checks into a routine is more reliable than reacting to prompts one by one.

    For Recovery practice, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with recovery practice
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone

Related reading

Getting StartedNetwork GuidesSecurity