imtoken App

Capabilities and boundaries

imtoken App makes more sense when mobile wallet, network management, asset views, transaction history, DApp access are considered as parts of one on-chain workflow. A wallet interface is only the entry point; the important checks concern the network, address, contract and on-chain state.

During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to mobile wallet. Any action that changes assets, permissions or account state deserves a full review before confirmation.

Real-world use cases

During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to mobile wallet. Any action that changes assets, permissions or account state deserves a full review before confirmation.

For network management, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. When a request is unclear, stop before signing or transferring and verify the network and on-chain record from a trusted path.

Operational checks

For network management, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. When a request is unclear, stop before signing or transferring and verify the network and on-chain record from a trusted path.

When asset views is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.

Security principles

When asset views is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.

For transaction history, retain the transaction hash or other useful reference when appropriate. On-chain transactions generally cannot be reversed unilaterally by a wallet, which makes pre-broadcast checks of the address, network, amount and permissions especially important.

Continue learning

For transaction history, retain the transaction hash or other useful reference when appropriate. On-chain transactions generally cannot be reversed unilaterally by a wallet, which makes pre-broadcast checks of the address, network, amount and permissions especially important.

Finally, consider DApp access. Third-party DApps, smart contracts and network services can introduce technical, operational and market risk. Unclear signatures, unnecessarily broad approvals, or any page asking for a seed phrase or private key are reasons to stop and re-check the request.