Core security principles
Core security principles is an essential part of understanding Security Center. 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.
Core security principles is an essential part of understanding Security Center. 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
Common attack paths
Common attack paths is an essential part of understanding Security Center. 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.
Common attack paths is an essential part of understanding Security Center. 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
Transfer and approval checks
Transfer and approval checks is an essential part of understanding Security Center. 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.
Transfer and approval checks is an essential part of understanding Security Center. 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
Devices and network environments
Devices and network environments is an essential part of understanding Security Center. 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.
Devices and network environments is an essential part of understanding Security Center. 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