imtoken Product Guide

Wallet & Assets

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

Core concepts

After a Wallet & Assets task is completed, review transaction history and safety checks 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 multi-chain assets, first define its role in the current task, then check whether addresses and networks and sending and receiving are consistent. When transaction history is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For safety checks, 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: multi-chain assets
Cross-check: addresses and networks and sending and receiving
Review carefully: transaction history
Verify afterward: safety checks

Checks before you act

To understand Wallet & Assets, treat addresses and networks and sending and receiving 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 addresses and networks, first define its role in the current task, then check whether sending and receiving and transaction history are consistent. When safety checks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For multi-chain assets, 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: addresses and networks
Cross-check: sending and receiving and transaction history
Review carefully: safety checks
Verify afterward: multi-chain assets

How to evaluate a live request

sending and receiving rarely appears in isolation. It often intersects with transaction history and safety checks. 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 sending and receiving, first define its role in the current task, then check whether transaction history and safety checks are consistent. When multi-chain assets is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For addresses and networks, 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: sending and receiving
Cross-check: transaction history and safety checks
Review carefully: multi-chain assets
Verify afterward: addresses and networks

Risks and boundaries

When using imtoken for Wallet & Assets, 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 transaction history, first define its role in the current task, then check whether safety checks and multi-chain assets are consistent. When addresses and networks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For sending and receiving, 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: transaction history
Cross-check: safety checks and multi-chain assets
Review carefully: addresses and networks
Verify afterward: sending and receiving

How to verify the outcome

From a risk perspective, addresses and networks and sending and receiving 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 safety checks, first define its role in the current task, then check whether multi-chain assets and addresses and networks are consistent. When sending and receiving is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For transaction history, 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: safety checks
Cross-check: multi-chain assets and addresses and networks
Review carefully: sending and receiving
Verify afterward: transaction history

Before you continue

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.