Learn control before features
A first-time wallet user should understand the relationship between a public address, private key, and seed phrase before exploring advanced tools. Addresses are typically shareable for receiving, while private keys and seed phrases must remain secret. This foundation makes network and transaction concepts much easier to reason about. For Support, convert this principle into a repeatable check: identify the action, verify the network and counterparty, and review the important fields again before signing or submitting. This is more reliable than trusting colors, icons, or familiarity alone. If the result does not match your expectation, stop, keep the transaction hash, contract address, or network details, and verify them through a trusted source. Do not skip checks because a page creates urgency or promises a reward.
Use your first transaction to learn the network
The same asset name can exist across multiple networks. Learn to identify the current chain, the native gas asset, and the destination before sending. A small, affordable test transaction can help connect the interface to the actual on-chain record visible through a transaction hash. For Support, convert this principle into a repeatable check: identify the action, verify the network and counterparty, and review the important fields again before signing or submitting. This is more reliable than trusting colors, icons, or familiarity alone. If the result does not match your expectation, stop, keep the transaction hash, contract address, or network details, and verify them through a trusted source. Do not skip checks because a page creates urgency or promises a reward.
Wallet setup
Check whether you are creating a new wallet or importing an existing one, and confirm that backups remain private.
Network and balance
Verify the active network, token contract when relevant, and whether the balance is visible on a trusted explorer.
Transaction status
Locate the transaction hash and inspect inclusion, confirmations, recipient, amount, and fee.
DApp requests
Check the domain, requested account, signature text, approval spender, and transaction target.
Security concern
Stop signing, disconnect unneeded sessions, review approvals, and move to a trusted device if the current environment is suspicious.
Staking question
Review validator state, exit mechanics, waiting periods, service terms, and risk before taking action.
Break Web3 prompts into separate actions
Connection, message signing, transaction signing, and token approval are distinct. A trusted connection does not make every later prompt safe. Learning to inspect domains, contract addresses, allowance amounts, and transaction recipients is central to independent judgment. For Support, convert this principle into a repeatable check: identify the action, verify the network and counterparty, and review the important fields again before signing or submitting. This is more reliable than trusting colors, icons, or familiarity alone. If the result does not match your expectation, stop, keep the transaction hash, contract address, or network details, and verify them through a trusted source. Do not skip checks because a page creates urgency or promises a reward.
Security is a maintenance routine
Backup is not a one-time checkbox. Devices change, approvals accumulate, networks evolve, and phishing techniques change. Revisit the readability of your backup, stale permissions, device access, and bookmarked entry points so that your security practices remain useful over time. For Support, convert this principle into a repeatable check: identify the action, verify the network and counterparty, and review the important fields again before signing or submitting. This is more reliable than trusting colors, icons, or familiarity alone. If the result does not match your expectation, stop, keep the transaction hash, contract address, or network details, and verify them through a trusted source. Do not skip checks because a page creates urgency or promises a reward.
Turn knowledge into a repeatable checklist
The goal of learning Support is not to collect terminology but to make actions verifiable. Keep a personal checklist for trusted entry points, the active network, addresses or contracts, amounts or permission scope, and post-transaction verification. Reject requests you cannot explain. imtoken will never ask you to enter a seed phrase, private key, recovery phrase, or verification code on a webpage, and on-chain transactions generally cannot be unilaterally reversed by a wallet.