The unified download entry remains the starting point
All download calls to action use /download.html. Content pages do not trigger downloads automatically or expose a final mobile download target. Verify the domain before starting the flow.
Updates
Product, Network, Security and Service Updates
This section prioritizes information that can change how an action should be reviewed. When no verifiable date is available, notices use labels such as Recent Update, Product Notice and Security Notice rather than inventing a publication date.
Recent Update
Understand the change before deciding whether to act
A useful notice explains what changed, which workflow is affected and what should be verified next. Network, approval and download notices should stay anchored to the actual request and verifiable on-chain information.
View →
Re-check assets and gas after switching networks
When moving to another public chain, EVM network or Layer 2, the fee asset, explorer, confirmation behavior and available tokens can change. Similar address formats do not make networks identical.
Be cautious with messages asking for recovery information
imtoken personnel will not ask for a seed phrase, private key or verification code. Stop and verify the source if a message requests remote access, wallet import to an unknown site or sensitive recovery material.
DApp connection and token approval are separate decisions
Connecting an account does not automatically grant spending permission. Message signatures, transaction signatures and token approvals that follow should each be reviewed for target, details and scope.
Ethereum staking rewards and exit timing can change
Reward sources, validator state, network queues and protocol rules can affect outcomes. Exits can involve waiting, validators can face protocol penalties and digital asset prices can fluctuate.
Inspect the transaction hash before repeating a pending action
If a status does not update, use the relevant explorer to inspect the transaction hash, block and confirmation state. Repeating an unclear action can add fees and make troubleshooting harder.
Match a notice to your own operating context
A network reminder will not affect every user in the same way. First identify the chain, asset, DApp or service you are using. If a notice concerns approval risk, inspect the spender and allowance. If it concerns congestion, use the transaction hash to verify state. If it concerns staking, consider exit waiting, validator status and contract risk together.
A notice is not a substitute for on-chain verification. Transfers, contract calls and approvals should still be checked against the transaction hash, contract address, block data and the appropriate explorer. Do not let countdowns, limited-time language or high-return claims override security checks.
Network troubleshooting path
Review network, address, gas and confirmation in a stable order.
Security center
Core principles for recovery material, approvals, phishing and devices.
Support
Gather safe-to-share on-chain information without exposing recovery material.