On this page
first launch and local wallet setupnetwork and asset managementreceiving and sendingtransaction history checksDApps and approvalsUsing the imtoken App: A practical guide to creating or importing a wallet, managing networks, viewing assets, reviewing transactions and using DApps on mobile. imtoken brings together multi-chain asset management, network selection, sending and receiving, transaction history and Web3 connections. Product use is most reliable when each feature is paired with a clear verification habit.
first launch and local wallet setup
When working with first launch and local wallet setup, place the concept back into a real transaction flow. Information on screen may come from on-chain state, local wallet records or a third-party page, so verify public details such as the network, address, transaction hash or contract before deciding what to do next.
In Using the imtoken App, the section on first launch and local wallet setup connects directly to the page’s main task. The asset list in a wallet is an organized view of on-chain information rather than a separate ledger. When a balance changes, check the active network, token contract and transaction history together so that same-named assets or network switches do not create confusion.
Within Using the imtoken App, for first launch and local wallet setup, keep the decision reversible for as long as possible: verify information first, then authorize only the minimum action needed. If the request changes the network, transfers an asset, grants spending permission or interacts with a contract, review the exact target and expected result before confirming.
In Using the imtoken App, a good outcome for first launch and local wallet setup is not simply that an interface reports success. The useful evidence is whether the expected on-chain state appears on the correct network, under the correct address or contract, and with a transaction or permission record that matches the intended action.
network and asset management
A common mistake with network and asset management is drawing a conclusion from a single field. A stronger check compares the active network, destination, asset identity and on-chain record together, especially for same-named tokens, cross-network activity or DApp interactions.
In Using the imtoken App, the section on network and asset management connects directly to the page’s main task. The asset list in a wallet is an organized view of on-chain information rather than a separate ledger. When a balance changes, check the active network, token contract and transaction history together so that same-named assets or network switches do not create confusion.
Within Using the imtoken App, for network and asset management, keep the decision reversible for as long as possible: verify information first, then authorize only the minimum action needed. If the request changes the network, transfers an asset, grants spending permission or interacts with a contract, review the exact target and expected result before confirming.
In Using the imtoken App, a good outcome for network and asset management is not simply that an interface reports success. The useful evidence is whether the expected on-chain state appears on the correct network, under the correct address or contract, and with a transaction or permission record that matches the intended action.
receiving and sending
For receiving and sending, a useful review pattern is source, scope and result. Source explains where the request came from; scope shows what the action can affect; result is then checked through transaction records, block confirmations or approval state.
In Using the imtoken App, the section on receiving and sending connects directly to the page’s main task. The asset list in a wallet is an organized view of on-chain information rather than a separate ledger. When a balance changes, check the active network, token contract and transaction history together so that same-named assets or network switches do not create confusion.
Within Using the imtoken App, for receiving and sending, keep the decision reversible for as long as possible: verify information first, then authorize only the minimum action needed. If the request changes the network, transfers an asset, grants spending permission or interacts with a contract, review the exact target and expected result before confirming.
In Using the imtoken App, a good outcome for receiving and sending is not simply that an interface reports success. The useful evidence is whether the expected on-chain state appears on the correct network, under the correct address or contract, and with a transaction or permission record that matches the intended action.
transaction history checks
transaction history checks is not only a feature label; it also has a specific risk boundary. If a page conflicts with the wallet display or the request cannot be explained clearly, stop before signing, approving or transferring and verify through trusted public information.
In Using the imtoken App, the section on transaction history checks connects directly to the page’s main task. The asset list in a wallet is an organized view of on-chain information rather than a separate ledger. When a balance changes, check the active network, token contract and transaction history together so that same-named assets or network switches do not create confusion.
Within Using the imtoken App, for transaction history checks, keep the decision reversible for as long as possible: verify information first, then authorize only the minimum action needed. If the request changes the network, transfers an asset, grants spending permission or interacts with a contract, review the exact target and expected result before confirming.
In Using the imtoken App, a good outcome for transaction history checks is not simply that an interface reports success. The useful evidence is whether the expected on-chain state appears on the correct network, under the correct address or contract, and with a transaction or permission record that matches the intended action.
DApps and approvals
After completing an action involving DApps and approvals, review the outcome again. Transaction status, approval targets, network confirmations and balance changes are stronger evidence than a page-level success message alone.
In Using the imtoken App, the section on DApps and approvals connects directly to the page’s main task. The asset list in a wallet is an organized view of on-chain information rather than a separate ledger. When a balance changes, check the active network, token contract and transaction history together so that same-named assets or network switches do not create confusion.
Within Using the imtoken App, for DApps and approvals, keep the decision reversible for as long as possible: verify information first, then authorize only the minimum action needed. If the request changes the network, transfers an asset, grants spending permission or interacts with a contract, review the exact target and expected result before confirming.
In Using the imtoken App, a good outcome for DApps and approvals is not simply that an interface reports success. The useful evidence is whether the expected on-chain state appears on the correct network, under the correct address or contract, and with a transaction or permission record that matches the intended action.
Important risk reminder
For Using the imtoken App, Remember: the user is responsible for safeguarding the seed phrase and private keys, and official staff will not ask for a seed phrase, private key or verification code. On-chain transactions generally cannot be reversed by a wallet alone, and third-party DApps or smart contracts may involve technical or fraud risks. Review the address, network, amount, approval target and permission scope before acting.