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 Product

imtoken App

Learn how the mobile wallet experience handles assets, networks, history and DApp interactions.

Download imtokenRead the getting-started guide
Web3Browser connection with request-by-request review
01

What the mobile app is for

Real usage context

A useful way to approach this topic is to separate what the interface displays from what the blockchain actually records. imtoken App is best understood through the specific decisions a user makes, not just through interface labels. Learn how the mobile wallet experience handles assets, networks, history and DApp interactions.

For practical review, split the request into five layers: network, address or contract, asset or permission, network fee, and resulting transaction state. The network tells you where execution occurs; the address or contract identifies the target; the asset or permission defines the scope; gas reflects network execution cost; and the transaction hash provides a durable reference for verification. If an application shows only vague language such as “continue”, “verify” or “claim”, use the wallet confirmation screen to inspect what is actually being requested.

Keep seed phrases and private keys under your own control. imtoken personnel will not request a seed phrase, private key or verification code. Before transferring, signing or approving, check the network, destination or contract and the exact action. Confirmed blockchain transactions are generally not reversible by a wallet provider, and third-party DApps and smart contracts can introduce independent risks.

The goal is to be able to explain which network is involved, who or what the request targets, what permission is being granted and what on-chain outcome may follow.

02

Managing networks and assets

Real usage context

Most mistakes in this area come from missing context rather than from a single button press. A practical check for this topic is: what the mobile app is for; then consider managing networks and assets before moving to the next action.

For practical review, split the request into five layers: network, address or contract, asset or permission, network fee, and resulting transaction state. The network tells you where execution occurs; the address or contract identifies the target; the asset or permission defines the scope; gas reflects network execution cost; and the transaction hash provides a durable reference for verification. If an application shows only vague language such as “continue”, “verify” or “claim”, use the wallet confirmation screen to inspect what is actually being requested.

Keep seed phrases and private keys under your own control. imtoken personnel will not request a seed phrase, private key or verification code. Before transferring, signing or approving, check the network, destination or contract and the exact action. Confirmed blockchain transactions are generally not reversible by a wallet provider, and third-party DApps and smart contracts can introduce independent risks.

That habit makes it easier to reason from verifiable on-chain evidence even when an interface changes.

03

Reviewing transaction history

Real usage context

Start with the user decision: identify the network, counterparty or contract, requested permission and expected result before confirming. On-chain activity is contextual. Network, address, contract, amount, permissions and transaction status can each change the meaning of what the wallet is showing.

For practical review, split the request into five layers: network, address or contract, asset or permission, network fee, and resulting transaction state. The network tells you where execution occurs; the address or contract identifies the target; the asset or permission defines the scope; gas reflects network execution cost; and the transaction hash provides a durable reference for verification. If an application shows only vague language such as “continue”, “verify” or “claim”, use the wallet confirmation screen to inspect what is actually being requested.

Keep seed phrases and private keys under your own control. imtoken personnel will not request a seed phrase, private key or verification code. Before transferring, signing or approving, check the network, destination or contract and the exact action. Confirmed blockchain transactions are generally not reversible by a wallet provider, and third-party DApps and smart contracts can introduce independent risks.

If a critical field cannot be verified, stopping and checking independently is safer than completing the action under time pressure.

04

Protecting the mobile device

Real usage context

A repeatable verification habit is more durable than memorizing one interface because networks and applications can change over time. For safety, keep seed phrases and private keys offline and private, verify requests independently, and remember that confirmed blockchain transactions are generally not reversible by a wallet provider.

For practical review, split the request into five layers: network, address or contract, asset or permission, network fee, and resulting transaction state. The network tells you where execution occurs; the address or contract identifies the target; the asset or permission defines the scope; gas reflects network execution cost; and the transaction hash provides a durable reference for verification. If an application shows only vague language such as “continue”, “verify” or “claim”, use the wallet confirmation screen to inspect what is actually being requested.

Keep seed phrases and private keys under your own control. imtoken personnel will not request a seed phrase, private key or verification code. Before transferring, signing or approving, check the network, destination or contract and the exact action. Confirmed blockchain transactions are generally not reversible by a wallet provider, and third-party DApps and smart contracts can introduce independent risks.

There is no benefit in rushing an unfamiliar signing request; understanding the request should come before confirmation.

Product safety principles

The wallet interface helps present network and transaction information, but users remain responsible for protecting seed phrases and private keys and for reviewing third-party DApp requests before signing.

imtoken

Ready to continue?

Download access always goes through the dedicated download page.

Download imtoken