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 logoimtoken
中文Download

Staking & Services

Support

A practical imtoken guide to support, including core concepts, verification steps and risk-aware usage.

01

Core concepts

When using imtoken for Support, prioritize information that can be independently verified, such as addresses, network names, contract addresses, transaction hashes and block-explorer records. Visual design, urgency messages or claims from an unknown support account are not substitutes for verifiable on-chain details.

For self-service checks, first define its role in the current task, then check whether transaction lookup and security issues are consistent. When DApp issues is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For download entry, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

  • Confirm: self-service checks
  • Cross-check: transaction lookup and security issues
  • Review carefully: DApp issues
  • Verify afterward: download entry
02

Checks before you act

From a risk perspective, DApp issues and download entry deserve an independent review. Once a transaction is confirmed on-chain, a wallet normally cannot reverse it unilaterally. DApps and smart contracts can also introduce permission and contract risks, so every signature, approval and transfer should be understood before it is accepted.

For transaction lookup, first define its role in the current task, then check whether security issues and DApp issues are consistent. When download entry is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For self-service checks, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

  • Confirm: transaction lookup
  • Cross-check: security issues and DApp issues
  • Review carefully: download entry
  • Verify afterward: self-service checks
03

How to evaluate a live request

After a Support task is completed, review self-service checks and transaction lookup to make sure the outcome matches the intent. Long-lived approvals and persistent connections should be revisited periodically. Good wallet hygiene is a repeated process of checking critical details and retaining traceable on-chain information, not a one-time setting.

For security issues, first define its role in the current task, then check whether DApp issues and download entry are consistent. When self-service checks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For transaction lookup, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

  • Confirm: security issues
  • Cross-check: DApp issues and download entry
  • Review carefully: self-service checks
  • Verify afterward: transaction lookup
04

Risks and boundaries

To understand Support, treat DApp issues and download entry as parts of the same on-chain workflow. The interface is only the entry point; the selected network, current chain state and permission scope determine what actually happens. Confirm the destination, source and network before continuing so the meaning of the request stays clear.

For DApp issues, first define its role in the current task, then check whether download entry and self-service checks are consistent. When transaction lookup is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For security issues, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

  • Confirm: DApp issues
  • Cross-check: download entry and self-service checks
  • Review carefully: transaction lookup
  • Verify afterward: security issues
05

How to verify the outcome

download entry rarely appears in isolation. It often intersects with self-service checks and transaction lookup. A useful pattern is to separate each action into four checks: identify the object, verify the network, review permissions, and confirm the result. If one of those checks cannot be completed, stop and verify rather than relying on an unfamiliar site or remote instructions.

For download entry, first define its role in the current task, then check whether self-service checks and transaction lookup are consistent. When security issues is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For DApp issues, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.

  • Confirm: download entry
  • Cross-check: self-service checks and transaction lookup
  • Review carefully: security issues
  • Verify afterward: DApp issues

Important considerations

  • Never share your seed phrase, private key or verification code.
  • Verify the address, network and amount before sending.
  • Review each DApp signature and token approval independently.
  • Use transaction hashes and block explorers to verify on-chain status.
  • Revoke approvals and disconnect sessions that are no longer needed.