Product updates
Updates is organized around practical information rather than promotional claims. imtoken does not invent user counts, partnerships, licenses, rankings, or performance figures to fill a page.
Network notices
When a question involves a blockchain transaction, begin with non-sensitive facts such as network, public address, transaction hash, token contract, and the exact action that was attempted.
Security notices
Support and notices will never require a seed phrase, private key, or verification code. Requests for remote control, transfer to a “safe address,” or secret-key disclosure should be treated as suspicious.
Service notices
For topics involving third-party DApps, smart contracts, staking providers, or bridges, users should review the relevant technical and market risks before acting.
Risk context
Staking, validators, bridges, and other third-party services can involve protocol rules, fees, waiting periods, smart contracts, operators, and asset-price volatility. Rewards can change and exits can take time; fixed-return or risk-free language is inappropriate.
User judgment
The site explains mechanisms and operational checks rather than making decisions for the user. For higher-value activity, smaller verifiable steps and independent network or explorer checks can reduce avoidable mistakes.
Practical verification for Updates
A practical way to work with Updates is to separate preparation, review, execution, verification, and maintenance. Start by identifying the active network and account, then use Product updates, Network notices, and Security notices as checkpoints for the address, asset, contract, fee, or permission involved. After an action is broadcast, keep the transaction hash and verify it on the correct network. When a DApp or smart contract is involved, also review persistent approvals after the session ends. Public addresses and transaction hashes are appropriate troubleshooting references; seed phrases, private keys, and verification codes are not. Any workflow that asks for those secrets should be stopped and independently rechecked.
On-chain transactions generally cannot be reversed by a wallet provider. Review the address, network, amount, contract, and requested permissions before signing.