Wallet fundamentals and transaction verification
Explains the relationship among asset display, network selection, transaction hashes and public chain state.
Updates
No invented dates, funding, partnerships, licenses, user counts, transaction volumes or rankings. Each notice focuses on information users can understand and verify.
Explains the relationship among asset display, network selection, transaction hashes and public chain state.
Switching networks does not move assets; bridge actions require verification on both source and destination chains.
imtoken will not ask for seed phrases, private keys or verification codes, and support should not require remote control of a wallet.
Staking does not guarantee returns. Rewards can change, exits can take time, and validator, contract, service and price risks remain.
Connection, message signing, transaction signing and token approvals are different permissions and should be reviewed separately.
First identify whether the notice concerns a product interface, a specific network, DApp permissions or a service flow, then check whether you are affected. Never follow a notice that asks for a seed phrase, private key, verification code or remote-control “verification.”