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

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

Manage Multi-chain Assets and Connect to Web3 with Clarity

Use one clear hub to understand multi-chain assets, network selection, receiving and sending, DApp connections, signatures, approvals, blockchain concepts and wallet security. Every on-chain action should begin with a review of the address, network, permissions and request details.

Multi-chain assetsNetwork selectionSend & receiveDAppsApprovalsWallet security
imtoken mobile wallet product preview
01

Create a Wallet

Understand wallets, addresses and recovery information before creating one.

Learn more →
02

Back Up a Wallet

Keep your seed phrase offline and never send recovery information to anyone.

Learn more →
03

Receive Assets

Verify the receiving address, network and asset before sharing an address.

Learn more →
04

Send Assets

Review the address, network, amount, gas and token before confirming.

Learn more →
05

Connect to a DApp

Check the domain, account request, signature and approval scope.

Learn more →
Wallet capabilities

Understand the wallet through real tasks, from assets to Web3

Multi-chain assets

Asset display depends on the active network, address and token contract. Recheck assets, gas assets and transaction status when switching networks.

Multi-chain network overview

Send & receive

Verify address and network when receiving, then review amount, gas, token details and transaction hash when sending.

imtoken APP

View assets, networks and transaction history on mobile, and review each DApp request individually.

imtoken App interface

imtoken Web

Browser connections should make the account, network and permission scope clear. Disconnect unused connections and review any permissions that remain.

Wallet security

Keep seed phrases and private keys under your control, prefer offline backups, and never send recovery information to another person.

Offline backup and private key security
Blockchain networks

Choose the network first, then interpret fees and confirmations

Multi-chain

See how one wallet can connect to different networks and why parameters must be rechecked when switching.

Explore network knowledge →
Multi-chain overview illustration

Public Chains

Understand the role of nodes, blocks, transactions and confirmations.

Explore network knowledge →
Public Chains overview illustration

EVM

Learn addresses, gas, contracts, tokens and approvals on EVM-compatible networks.

Explore network knowledge →
EVM overview illustration

Layer 2

Understand relationships with base networks, bridges, cross-layer transfers and arrival checks.

Explore network knowledge →
Layer 2 overview illustration

Gas & Confirmations

See how fee estimates, block inclusion, confirmation depth and congestion affect transactions.

Explore network knowledge →
Gas & Confirmations overview illustration
Wallet journey

Turn wallet use into six repeatable review steps

01Get imtoken

Enter the official download flow after an intentional click; the site does not auto-download.

02Create or import a wallet

Before creating or importing, understand what recovery information controls and how it should be protected.

03Back up the wallet offline

Keep the seed phrase offline. Do not screenshot it, send it to another person or give it to someone claiming to be support.

04Select and verify the network

Confirm the network, address and asset match; similar address formats do not mean two networks are the same.

05Receive or send assets

Review the address, network, amount and gas. For higher-value actions, consider validating the workflow with a smaller scope first.

06Review transactions and approvals

Use the transaction hash to review on-chain status, and periodically remove DApp approvals you no longer need.

Web3 & DApp

A connection is only the beginning—review every signature and approval

A DApp may request account access, a network switch, a message signature, a transaction signature or a token approval. Do not treat an existing connection as automatic consent to later requests.

Connecting a wallet does not mean every signature request should be accepted. Review each signature and approval separately.

Explore the Web3 guide →

01 · Visit the DApp

Review the source, network, account and permissions at each step; a connection is not blanket consent for later requests.

02 · Verify the domain

Review the source, network, account and permissions at each step; a connection is not blanket consent for later requests.

03 · Start the connection

Review the source, network, account and permissions at each step; a connection is not blanket consent for later requests.

04 · Review the account request

Review the source, network, account and permissions at each step; a connection is not blanket consent for later requests.

05 · Check the signature or approval

Review the source, network, account and permissions at each step; a connection is not blanket consent for later requests.

06 · Complete the action

Review the source, network, account and permissions at each step; a connection is not blanket consent for later requests.

07 · Disconnect unused connections

Review the source, network, account and permissions at each step; a connection is not blanket consent for later requests.

Security

Put security habits before every on-chain confirmation

Wallet security goes beyond a single warning about private keys. It requires ongoing checks of seed phrase storage, DApp spenders, signature origins, device conditions, networks and recipient addresses. On-chain transactions generally cannot be reversed by a wallet alone, so preventive verification is more reliable than recovery after a mistake. Use public devices and networks cautiously, and treat any request for a seed phrase, private key or verification code as high risk.

Open the Security Center →
Wallet security checklist illustration

Security checklist

  • Back up the seed phrase offline
  • Never disclose the private key
  • Verify network and address
  • Review signature requests
  • Manage DApp approvals
Academy

What Should You Understand Before Using a Digital Wallet?

Start with addresses, then learn seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals. The sequence matters: understand who controls the account, where a transaction is executed and what confirmation creates before moving into more complex contract interactions.

Read the getting-started guide →
Topic

Public Chains & Confirmations

Understand nodes, blocks, transactions and confirmation.

Topic

EVM & Smart Contracts

Learn addresses, gas, tokens and approvals.

Topic

Layer 2 Basics

Understand base-layer relationships and cross-layer transfers.

Topic

DApp Approvals

Review spenders, allowances and revocation.

Topic

Wallet Security

Build practical everyday security habits.

Topic

Blockchain Glossary

Look up common on-chain terms quickly.

Ethereum & PoS

Understand validators—and the risk boundaries before participating

Ethereum Staking Basics

Learn Ethereum PoS, validators, reward sources, network status, withdrawals and exits. Rewards are not fixed and are not guaranteed.

Read staking basics →

Before you participate

Exits may involve waiting periods, validators may face protocol penalties, smart contracts carry technical risk, and digital asset prices can fluctuate. Third-party services can add another layer of risk.

Learn PoS & validators →
Updates

Product, network, security and service notices

Product Notice

Product Notice

The site uses one download entry so the user initiates the download flow intentionally.

Network

Network

Recheck assets, addresses, gas and contract details whenever you switch networks.

Security

Security

imtoken official staff will never ask for your seed phrase, private key or verification code.

Service

Service

Before staking, understand exit waiting periods, protocol penalties, contract risk and market volatility.

View all updates →

FAQ

Frequently asked questions

A wallet address is a public identifier used to receive on-chain assets. Before sending, verify the network, asset and full address rather than relying only on a few visible characters.

Both can represent control over wallet accounts. A seed phrase commonly derives or restores accounts, while a private key usually signs for a specific account. Neither should be sent to another person.

It is safer not to. Screenshots, photo sync and cloud storage increase exposure. Prefer an offline backup that is stored securely and separately from everyday connected devices.

Many EVM-compatible networks use the same address format, but their assets and network states are separate. Always verify the network, chain parameters and token contract.

Gas measures the computational resources needed for an on-chain operation. Fees depend on network rules and congestion, so wallet estimates can change as network conditions change.

A transaction hash is a unique identifier that can be checked on a suitable block explorer to review status, block inclusion, confirmations and interaction details.

Once an on-chain transaction is confirmed, a wallet generally cannot reverse it unilaterally. Recovery options depend on the recipient, network and asset, making pre-transfer checks essential.

View the full FAQ →

imtoken

Start with understanding, then act on-chain

All download buttons use the same download entry. Before transferring, signing or approving, verify the address, network, amount and request details.

Download imtoken