imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken · Knowledge and practical checks

Updates

The Updates center covers product use, network conditions, security reminders and service notices. It does not invent dates, partnerships, fundraising claims or scale metrics.

Use the page as a decision guide: identify the network, account and request before signing or moving assets.
On this page
01 · Product notices stay verifiable

Product notices stay verifiable

Product notices describe observable features, navigation or usage principles without invented download counts, user numbers or media claims.

Do not rely on a button label or a familiar-looking page as the reason to continue. Compare the request with the on-chain target, network state and expected result, and stop when those pieces do not line up.

02 · Network notices focus on user impact

Network notices focus on user impact

Network congestion, fee changes or confirmation delays are explained by their practical effect on users rather than presented as marketing news.

A common mistake is to treat a normal-looking interface as proof that the underlying blockchain action is correct. Public addresses, transaction hashes, contract addresses and network parameters provide independent ways to verify what is happening.

03 · Security notices provide checks

Security notices provide checks

Security notices identify concrete checks for domains, approvals, signatures, addresses and networks without flashing red effects, countdowns or fear-based copy.

A repeatable order of checks is more reliable than memory. Review source, network, account, target and expected outcome each time so the same safety logic carries across wallets and DApps.

04 · Service notices avoid yield promises

Service notices avoid yield promises

Staking and validator notices disclose variable rewards, exit waits, penalties, contract risk and market risk instead of fixed-yield or “risk-free” claims.

When a task involves a third-party contract, bridge, validator or web service, separate that external risk from the wallet itself. A wallet can display and sign a request, but it cannot guarantee the safety of outside code or services.

Practical checklist

  • Confirm that “Product notices stay verifiable” matches the task you intend to perform
  • Confirm that “Network notices focus on user impact” matches the task you intend to perform
  • Confirm that “Security notices provide checks” matches the task you intend to perform
  • Confirm that “Service notices avoid yield promises” matches the task you intend to perform

Risk reminder

Seed phrases and private keys remain under the user’s control. Legitimate support should not ask for a seed phrase, private key or verification code. Review address, network and amount before transferring; blockchain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review spender and permission scope and consider revoking unused approvals.