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

Product & Security Updates

A practical guide to product & security updates with clear concepts, user checks and risk boundaries before wallet actions are confirmed.

On this page
  1. Product notices
  2. Network notices
  3. Security notices
  4. Service notices

Product notices

Product notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Product notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Confirm the current account and network
  • Never share a seed phrase, private key or verification code
  • Read the full transfer, signature or approval request before confirming

Network notices

Network notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Network notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Security notices

Security notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Security notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. imtoken does not ask users to enter seed phrases, private keys or recovery phrases into content pages. On-chain transactions generally cannot be reversed by a wallet provider, so confirmation should always follow the user’s own review.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear

Service notices

Service notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Service notices is an essential part of understanding Product & Security Updates. Treat every wallet request as a decision with consequences. Check the source, understand the requested permission, and confirm that the action is actually necessary. A site, support account or promotion that asks for a seed phrase, private key or verification code should be treated as a serious warning sign. When something is unclear, stop and re-check through a trusted entry point rather than following an unfamiliar link, screenshot instruction or remote-control request. A small test transaction can be useful before a high-value transfer.

Practical checks

  • Keep the transaction hash for later checks
  • Use the relevant block explorer to verify on-chain status
  • Stop and re-check when the source or request is unclear