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.

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

Manage Multi-chain Assets and Connect to Web3 with Clarity

Bring multi-chain assets, network selection, sending and receiving, DApp connections, token approvals, blockchain knowledge and wallet security into one practical flow. imtoken pairs product capabilities with the checks that matter before you act.

Multi-chain AssetsNetwork ChecksDApps & ApprovalsSecurity Education
imtoken mobile wallet interface

Quick Tasks

Start with what you need to do now

You do not need to browse every feature first. Enter through the task, then verify the result against on-chain information.

01

Create a Wallet

Understand self-custody and create a wallet in a trusted environment.

Open guide →
02

Back Up a Wallet

Record the seed phrase offline and verify it without uploading or sharing it.

Open guide →
03

Receive Assets

Confirm the network first, then use the address for that network.

Open guide →
04

Send Assets

Review recipient, network, asset and amount before gas and confirmation.

Open guide →
05

Connect to a DApp

Verify the domain and review connection, signature and approval requests separately.

Open guide →

Wallet Capabilities

Organized around real asset, network and Web3 decisions

Multi-chain Assets

Understand network differences before switching

A multi-chain interface can simplify access, but gas assets, token contracts and transaction histories remain network-specific. When a balance looks wrong, verify network and contract first.

Explore multi-chain networks →
Multi-chain network relationships
imtoken App

Review assets and transactions on mobile

Manage networks, portfolio information and transaction history while keeping device security and signing context in view.

imtoken App product interface
Send & Receive

Address, network, amount, gas and transaction hash

Confirm the receiving network first, review transfer details before signing, and use the transaction hash to verify status afterward.

Send & receive guide →
imtoken Web

Browser connections and approval review

Connecting a DApp does not mean every later request is safe. Treat messages, transactions and token approvals as separate decisions.

Learn about Web connections →
Wallet Security

Make key custody and permission review part of daily use

Keep seed phrases and private keys offline where possible, inspect approval scope, and review permissions that are no longer needed.

Open Security →
Offline private key and seed phrase safety

Explore Networks

Confirm the network before deciding where the transaction belongs

All panel content remains in the server-rendered page; the interaction only changes reading focus.

Different networks maintain different state

A multi-chain wallet brings several networks into one interface without merging their ledgers. Confirm the destination network before every transfer or token action.

Multi-chain guide →
Multi-chain network knowledge

Nodes, blocks and confirmations

Public chains use nodes and consensus rules to maintain a shared ledger. Services may wait for additional confirmations after inclusion.

Public chain basics →
Public chain nodes and blocks

Compatibility does not merge assets

EVM networks can share a similar execution model and address format while keeping separate gas assets, token contracts and chain state.

EVM networks →
EVM compatible network knowledge

Mainnet, scaling layers and cross-layer flows

Layer 2 systems have a defined relationship with mainnet. Deposits and withdrawals can involve bridges and different waiting stages.

Layer 2 basics →
Layer 2 and mainnet relationship

Gas and confirmations describe execution state

Gas reflects execution resources and fee mechanics; confirmations show how a transaction becomes embedded in later blocks. Failed transactions can still consume gas.

Gas & confirmations →

Wallet Journey

Put the important checks before each action

01

Get imtoken

Use a trusted entry point for the download flow rather than unfamiliar ads or chat links.

02

Create or Import

Create a wallet or import an existing one only inside a trusted wallet environment.

03

Back Up Offline

Store the seed phrase offline and verify its order without screenshots, cloud uploads or chat transfers.

04

Choose the Network

Confirm what the receiving service or DApp supports, including the gas asset and contract context.

05

Receive or Send

Check network, recipient, asset, amount and fee before signing; use a small test where appropriate.

06

Review Transactions & Approvals

Use the transaction hash to verify on-chain status and clean up connections or approvals you no longer need.

Web3 & DApps

A connection is only the beginning

A wallet connection establishes context between an account and a DApp. It does not make every later signature, approval or transaction acceptable. The meaningful review happens request by request.

Read the Web3 guide →
  1. 01Visit the DApp
  2. 02Verify the domain
  3. 03Start the connection
  4. 04Review account requests
  5. 05Check the signature or approval
  6. 06Complete the action
  7. 07Disconnect unused sessions

Security

Security comes from repeatable checks, not absolute promises

Seed phrases and private keys determine account control and should remain under the user’s custody, preferably with offline backup. DApp use requires domain verification, signature review and approval management. Transfers require checks on recipient, network, amount and asset. Shared devices, remote-control sessions and untrusted networks add uncertainty. Confirmed on-chain transactions usually cannot be reversed by the wallet provider, so the decisive review belongs before broadcast.

Open Security →
Offline seed phrase and private key safety
  • Back up the seed phrase offline
  • Never disclose private keys
  • Verify network and recipient
  • Review signature requests
  • Manage DApp approvals

Academy

Understand the concepts before acting on-chain

View all learning content →
Featured Starter

What Should You Understand Before Using a Digital Wallet?

Addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals shape what a wallet request actually means. The goal is not memorizing vocabulary; it is building a reliable decision sequence.

Start learning →
NetworksPublic Chains & ConfirmationsNodes, blocks and confirmation depth.ContractsEVM & Smart ContractsAddresses, gas, tokens and execution.ScalingLayer 2 BasicsMainnet relationships, bridges and arrival checks.Web3DApp ApprovalsSpender, allowance and revocation.SecurityWallet SecurityKeys, devices, phishing and transfer checks.GlossaryBlockchain GlossaryPut common terms back into practical context.

Ethereum & PoS

Ethereum Staking Basics

PoS validators propose and attest to blocks as part of network consensus. Reward levels depend on network conditions, validator performance and protocol rules, while exits and withdrawals may involve waiting.

Explore Ethereum staking →
Understand before participating
  • Validators can face protocol penalties
  • Rewards can change
  • Exits and withdrawals may take time
  • Smart contracts have technical risk
  • Digital asset prices are volatile
  • Third-party services add their own risk
PoS & validators →

Product & Security Updates

Focus on changes that affect real decisions

Updates →
Recent Update · Product Notice

Wallet journey and multi-chain guidance reorganized

Creation, backup, transfers, on-chain verification and DApp approvals are grouped around real user tasks.

Network Notice

Confirm the destination chain before cross-network movement

A normal transfer does not automatically perform cross-chain or cross-layer conversion.

Security Notice

Reject requests for seed phrases, private keys or verification codes

Those credentials do not belong in support forms, websites or chat conversations.

Service Notice

Staking content is presented with risks first

Rewards are not fixed; exits can involve waiting and validators or contracts can introduce additional risk.

FAQ

Resolve the most common decision questions first

No. Keep seed phrases and private keys under your own control and never submit them to support forms, chats or unfamiliar websites.

Some compatible networks use the same address format, but each network has separate state, gas assets, contracts and transaction history.

Usually not by the wallet provider. Review the address, network, asset and amount before broadcasting.

Gas is generally a blockchain network fee related to execution resources and congestion, not a universal fixed wallet charge.

A connection usually exposes a public address. Signatures, approvals and transactions are separate requests and should be reviewed individually.

Not necessarily. Disconnecting ends the session; on-chain approvals remain until they are separately changed or revoked.

No. Rewards can change with network conditions, validator performance and protocol rules, and exits or penalties may apply.

View the full FAQ →

imtoken

Start with the right network and stronger security habits

Every download button goes through the download page. Before any on-chain action, understand the network, address, gas, signature and approval.

Download imtoken