Recent Update
The imtoken updates area summarizes product notes, network notices, security reminders, and service information. When no verified date is available, the site does not invent a calendar date; the content itself takes priority.
Product Notice
Product notes explain feature changes, usage paths, and interface adjustments so users can understand which actions are affected. Important changes should include practical checks rather than only promotional language.
Network Notice
Network congestion, upgrades, or third-party service changes can affect confirmation times and availability. Users should compare wallet information with on-chain status rather than relying on a single interface message.
Security Notice
Security updates focus on seed phrases, private keys, signatures, approvals, phishing, and device environments. imtoken staff will never ask for a seed phrase, private key, or verification code.
Understanding product updates and network notices
When working with Updates, it helps to separate the roles of product updates and network notices. product updates identifies the main object or action you are dealing with, while network notices often affects how that action is recognized and processed by the network. Do not rely only on token names or icons. Check the network, address format, contract address when relevant, and the source of the request. In a multi-chain environment, similar-looking addresses do not mean every network is directly interchangeable.
Checking security notices before you act
A useful review of security notices has three layers: source, content, and result. Confirm that the site, DApp, or service is the one you intentionally opened; read the amount, network, approval target, gas information, or signature summary; then verify the final state with the transaction hash, block explorer, or wallet history. If these layers do not agree, stop and investigate instead of repeating the action in the hope that it will fix itself.
How service notices fits into an on-chain flow
service notices is often an important clue when deciding whether an on-chain action behaved as expected. A typical transaction is prepared and signed by the wallet, broadcast to the selected network, validated by nodes, and eventually included in a block. A wallet status such as “sent” may only mean the request was submitted. Final completion should be judged against the on-chain transaction status and the number of confirmations required by the receiving service.