Knowledge and support pages do not ask users to enter seed phrases, private keys, recovery phrases, or verification codes.
About imtoken
The imtoken site organizes practical information around multi-chain wallets, blockchain networks, Web3 use, security education, and Ethereum PoS so users can understand both the action they are taking and the checks that belong around it.
What this site is designed to clarify
A wallet interface can compress a complex on-chain action into a few controls, but addresses, networks, gas, signatures, approvals, and smart contracts still have distinct roles. The content here expands those concepts so users can understand what deserves review before confirmation and what public information can be used to verify a result afterwards.
The site provides corresponding Chinese and English content. Topics align page by page while the English copy is written for natural reading rather than treated as a literal sentence-by-sentence translation.
Content principles
Security depends on key custody, device hygiene, permission review, and transaction checks; risk education is more useful than claims of perfect protection.
The site does not add unverified partners, investors, licenses, user counts, trading volume, rankings, or media endorsements simply to make pages appear more established.
DApps, smart contracts, bridges, and other third-party services can introduce their own technical and operational risks.
What the knowledge center covers
Wallet & Assets covers creation, backup, receiving, sending, and transaction history. Blockchain Networks explains public chains, EVM, Layer 2, gas, and confirmations. Web3 & DApps separates connections, signatures, approvals, NFTs, and contract interactions. Security focuses on recovery secrets, phishing, devices, permissions, and transaction checks. The Academy provides a learning path, while Staking & Services explains Ethereum PoS, validators, reward sources, exit mechanics, and material risks.
Using the information responsibly
Networks and third-party services evolve, so users should combine these principles with the current network state and the exact request visible at the time of an action. Staking does not guarantee returns; rewards can change, exits may involve waiting, validators can face protocol penalties, smart contracts carry technical risk, and digital-asset prices can move materially.
How to use this knowledge center
If the core concepts are still new, begin with Getting Started to understand accounts, addresses, seed phrases, private keys, networks, and gas. Then use the wallet guides for creation, backup, receiving, and sending. When a balance or transaction status looks wrong, move to the network guides and explorer checks. Before using a DApp, read the separate guidance for connections, signatures, approvals, and contract interactions. This sequence keeps product use and risk judgment in the same learning path.
Security is not a separate feature that can be completed once and ignored. Backup decisions affect recovery-secret exposure; transfers require address and network checks; DApp access requires domain review; signatures require interpretation of the request; and approvals require understanding the spender and permission scope. Treating those actions separately produces better decisions than relying on a single “security setting.”
Each topic is intended to support a concrete decision: what must remain private, what public information can be verified, which network context applies, and what permission a request actually grants. Those questions remain useful even when interfaces and third-party services change over time.