About imtoken

Connect wallet tasks, network knowledge, and security decisions

imtoken brings together multi-chain wallet use, blockchain networks, Web3 and DApps, wallet security, Ethereum proof of stake, and validator knowledge.

Product scope

Wallet and asset-management knowledge

imtoken organizes content around practical multi-chain wallet tasks: creating or importing a wallet, offline backup, asset viewing, network selection, sending and receiving, gas, and transaction history. The goal is not to replace user judgment with a single interface but to make the relationship between address, network, asset, and on-chain result easier to verify.

Mobile and Web use cases separately cover account access, network management, DApp connection, signing, and approvals. Regardless of the entry point, seed phrases and private keys remain under the user's control and should not be handed to a website, support contact, or third party.

Network knowledge

Public chains, EVM, and Layer 2

The network section explains nodes, blocks, transaction confirmation, block explorers, EVM, gas, smart contracts, and Layer 2. A useful starting question is where an asset exists, followed by which network processes the transaction, which asset pays the fee, and where confirmation status can be checked.

For cross-network or cross-layer activity, the guides distinguish the source network, destination network, bridge, destination confirmation, and possible exit waiting periods. Similar address formats do not remove network differences; the intended asset and route still have to match the selected network.

Web3 knowledge

Connections, signatures, approvals, and contract interaction

DApp connections, message signatures, transaction signatures, token approvals, NFTs, and smart-contract interactions are explained as separate topics. A connection is not a reason to accept every later request; each signature or approval deserves a fresh check of the domain, account, network, and permission scope.

Third-party DApps and smart contracts can carry technical or business risks. The knowledge center focuses on understanding requests, limiting permissions, and managing connections or approvals that are no longer needed rather than making a promise that all risk is eliminated claims about third-party services.

Security principles

Secret material, devices, and transaction checks

imtoken will never ask for a seed phrase, private key, or verification code. Security guidance covers offline backup, screenshot and cloud-storage exposure, phishing sites, fake support, public devices, public Wi-Fi, remote-control software, clipboard address replacement, and malicious signing requests.

On-chain transactions generally cannot be reversed by a wallet provider alone, so verification before action matters. Check the address, network, and amount before sending; inspect the spender and scope before approving; and consider revoking permissions that are no longer required.

Information boundaries

State only product and knowledge facts that can be supported

The site does not invent partnerships, investors, regulators, licenses, office addresses, phone numbers, email addresses, user counts, download figures, assets under management, trading volume, market rankings, media coverage, testimonials, or partner logos simply to make a page look more complete.

Ethereum proof-of-stake and validator content also avoids promotional return claims. Staking does not assure returns; rewards can change, exit can involve waiting, validators can face network penalties, smart contracts and third-party services can carry risk, and digital-asset prices can fluctuate.