imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken

Manage Multi-chain Assets and Connect to Web3 with Clarity

A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken

Explore multi-chain assets, choose the right network, send and receive with clearer checks, connect to DApps, review approvals and build a stronger understanding of wallet security. imtoken brings product guidance and blockchain knowledge into one structured learning path.

Multi-chain assetsEVMLayer 2DAppApproval checks
imtoken mobile wallet product view

Start with the task in front of you

Five common wallet actions organized as practical entry points, with the next check made clear at each step.

01

Create a Wallet

Understand accounts, recovery and what you control before creating or importing a wallet.

Open guide →
02

Back Up a Wallet

Keep recovery information offline and verify that your backup can be used without exposing it.

Open guide →
03

Receive Assets

Confirm the receiving address and the exact network the sender will use before funds are sent.

Open guide →
04

Send Assets

Re-check destination, network, amount and gas before signing a transaction.

Open guide →
05

Connect to a DApp

Verify the domain, connect the intended account, and inspect every signature or approval separately.

Open guide →

One wallet, several layers of understanding

Assets, networks, transactions, browser connections and recovery security should be understood together.

Multi-chain Assets

Compare networks, verify addresses and read confirmation state before assuming assets move automatically between chains.

Learn more → Multi-chain Assets

imtoken App

Use the mobile wallet to view assets, switch networks, review transaction history and access DApps while keeping device security in mind.

Learn more → imtoken App

Send & Receive

Receiving requires the right address and network; sending adds amount, gas and transaction-hash checks.

Learn more →

imtoken Web

Browser connections make DApp access convenient, but every signature and approval remains a separate decision.

Learn more →

Wallet Security

Protect seed phrases and private keys offline, review approvals, and check transaction details before signing.

Learn more → Wallet Security

Explore blockchain networks with context

Switch topics without hiding the underlying content from users who browse without scripting.

Multi-chain

Different chains maintain separate states. Always verify the asset's network before receiving, sending or bridging.

Read the guide →
Multi-chain

A six-step wallet path

Each step adds context before the next action can affect assets or permissions.

01

Get imtoken

Use the official download entry and keep the installation source clear.

02

Create or import

Understand whether you are creating a new recovery set or importing an existing one.

03

Back up offline

Record recovery information offline and never send it to another person.

04

Choose the network

Match the asset, recipient and active network before continuing.

05

Receive or send

Check address, amount, gas and the exact action before signing.

06

Review transactions & approvals

Save transaction hashes and review permissions you no longer need.

Web3 & DApp

Treat every request as a separate decision

Connecting a wallet does not mean you should approve every later signature. Verify the site, account, requested action and permission scope each time.

A connection can be legitimate while a later request is unnecessary or risky. Read the request, not just the site name.
Open Web3 guide →
Visit the DApp
Verify the domain
Start the connection
Review the account request
Inspect signature or approval details
Complete the intended action
Disconnect when the connection is no longer needed
Security

Protect recovery secrets, permissions and every transaction

Wallet security is not a single setting. It is a chain of decisions: keeping recovery secrets offline, resisting phishing and fake support, reviewing DApp requests, controlling device exposure, and checking every transfer. imtoken will never ask for your seed phrase, private key or verification code. A wallet cannot unilaterally reverse an on-chain transaction, so prevention and verification matter more than promises of recovery.

Open Security Center →
Offline recovery-secret security concept
✓ Back up the seed phrase offline
✓ Never disclose a private key
✓ Verify network and address
✓ Inspect each signature request
✓ Review DApp approvals

Academy: build the mental model before the habit

Editorial guides connect addresses, recovery, networks, gas, transaction hashes, DApps and approvals.

Getting Started

What Should You Understand Before Using a Digital Wallet?

A wallet is an interface to blockchain accounts, not a bank account. Learn how addresses identify destinations, how seed phrases and private keys control recovery and signing, how networks separate asset state, why gas exists, how a transaction hash helps verification, and why DApp signatures and approvals deserve separate checks.

Read the full guide →
NetworkPublic chains and transaction confirmations EVMEVM and smart contracts Layer 2Layer 2 basics Web3DApp approvals SecurityWallet security GlossaryBlockchain glossary

Ethereum & Proof of Stake

Learn the protocol concepts before considering any staking action.

Ethereum Staking Basics

Ethereum PoS uses validators to participate in consensus. Rewards depend on protocol and network conditions, while withdrawals and exits follow network-defined mechanisms and may involve waiting periods.

Learn staking concepts →

Before you participate

Validator penalties, smart contract risk, service fees, waiting periods, third-party service risk and digital-asset price volatility can all affect outcomes.

Understand validators →

Product & Security Updates

Product explanations, network reminders, security guidance and service information are presented with the action context users need.

Product
Wallet navigation and learning paths

Product explanations are organized around user tasks rather than feature claims.

Details →
Network
Verify the active network before a transfer

Similar address formats can exist on different networks; always verify the network context.

Details →
Security
Recovery secrets stay private

Never send seed phrases, private keys or verification codes to any person or website.

Details →
Service
Read risk information before staking

Rewards, waiting periods, penalties and price movements can all vary.

Details →

Frequently asked questions

Clear answers about wallets, networks, DApps and security.

A digital wallet manages blockchain accounts, addresses and signing authority. Assets are recorded on their respective networks; the wallet helps you view state and prepare signatures or transactions.

A seed phrase can restore a wallet's account structure, while a private key controls signing for a specific account. Both are highly sensitive and should remain offline and private.

If you have no other valid backup, a wallet generally cannot recreate your seed phrase or private key for you. A tested offline backup should be created when the wallet is set up.

Similar address formats can exist across multiple networks, but the asset network and the recipient's supported network must match. A network mismatch can make recovery difficult or impossible.

Gas is the network fee mechanism used to execute transactions and smart contract operations. Cost varies with network rules, transaction complexity and congestion.

A transaction hash is an identifier that can be used in a blockchain explorer to inspect status, block inclusion, sender, recipient and related contract information.

Check the active network, save the transaction hash and inspect the explorer status before submitting the same action again. Handling differs by network and by the current on-chain state.

View all FAQ →

Continue with imtoken

Use the unified download entry. Never share recovery secrets during installation or setup.

Download imtoken