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

Learn how to review multi-chain assets, select the correct network, send and receive, connect to DApps, manage approvals, understand network concepts and build practical wallet security habits.

Multi-chain assetsNetwork checksDApp permissionsSecurity education
imtoken multi-chain wallet interface

Start with the task you need to complete

A task-based path makes it easier to notice a wrong network, incorrect recipient or unnecessary permission before you confirm.

01

Create a Wallet

Choose a trusted device and decide how recovery material will be backed up before creating an account.

Learn the basics →
02

Back Up a Wallet

Keep seed phrases offline and never send recovery secrets to anyone.

Backup principles →
03

Receive Assets

Confirm that sender and recipient are using the same intended network before sharing an address.

Receiving checks →
04

Send Assets

Verify recipient, network, amount and gas, then keep the transaction hash.

Sending workflow →
05

Connect to a DApp

Connection, signatures and approvals are separate actions that deserve separate review.

Connection guide →

Wallet capabilities organized around real use

Assets, networks, transactions, Web3 and security are connected, but each creates a different decision point.

Multi-chain assets

Confirm the network, address and on-chain status before treating a displayed balance as available on another network.

Multi-chain network relationship

Send & Receive

For receiving, match the network and address. For sending, review amount, gas and transaction hash. Confirmation speed depends on the network.

See the full workflow →

imtoken App

Review networks, assets and transaction history on mobile, and reread every request before signing.

imtoken app product view

imtoken Web

Browser connections support DApp access and account requests. A connection is not a trust decision, and an approval should never be automatic.

Explore web usage →

Wallet security

Keep seed phrases and private keys under your control, prefer offline backups and review the spender and amount before approving.

Offline wallet key safety principles

Explore blockchain networks

Use the tabs to compare concepts. All topics remain readable even when interactive switching is unavailable.

Multi-chain

Each network maintains its own balances, gas and transaction state. Confirm where the asset lives before selecting a destination.

Multi-chain concept

Public Chains

Transactions propagate through nodes, enter blocks and accumulate confirmations. Block explorers help you read the public state.

Public chain blocks and confirmations

EVM Networks

Several EVM networks may share an address format while keeping separate gas assets, token contracts and histories.

EVM-compatible network concept

Layer 2

Bridging and additional confirmation can be required between Layer 2 and mainnet. A successful source transaction does not always mean immediate destination availability.

Layer 2 and mainnet relationship

Gas & Confirmations

Gas reflects network execution cost, while confirmation time depends on network conditions. Use the transaction hash to inspect pending state.

A six-step wallet path

Each step has a verifiable goal so you do not have to rely on “just continue” behavior.

01

Get imtoken

Start from the download page and verify the product identity and source.

02

Create or import

Use a trusted device and do not enter recovery secrets into a website form.

03

Back up offline

Keep the seed phrase offline and never disclose a private key.

04

Select the network

Confirm the network name, gas asset and recipient support.

05

Receive or send

Verify address, network and amount, then keep the transaction hash.

06

Review transactions and approvals

Inspect DApp requests before signing and remove permissions you no longer need.

Web3 & DApps

After connecting, the important part is understanding each request

A wallet connection begins a session. Signatures, approvals and contract transactions remain separate decisions. “Connected” should never mean “approve everything.”

Open the Web3 guide →
Security note

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

Visit the DApp
Verify the domain
Start the connection
Review account requests
Inspect the signature or approval
Complete the action
Disconnect unused sessions

Make the security decision before the confirmation button

Seed phrases and private keys represent wallet control and should remain with the user. Legitimate support should never request them. Before sending, verify address, network and amount; before using a DApp, verify the domain, signature details, spender and permission scope.

Public computers, public Wi‑Fi, remote-control tools and clipboard replacement can increase exposure. Keep devices updated, be cautious with untrusted software and consider revoking approvals you no longer use.

Open Security →
Offline private key storage principles
Back up seed phrases offline
Never disclose private keys
Verify network and recipient
Inspect signature requests
Manage DApp approvals
Getting Started

What Should You Understand Before Using a Digital Wallet?

Start with addresses, seed phrases, private keys, networks and gas, then connect those concepts to transaction hashes, DApps and approvals. This sequence helps you identify errors such as choosing the wrong network or granting more permission than an action requires.

Read the guide →
Networks

Public chains and confirmations

Blocks, confirmation depth and explorer lookup.

Contracts

EVM and smart contracts

Addresses, gas, tokens and approvals.

Scaling

Layer 2 basics

Mainnet, bridges and destination confirmation.

Web3

DApp approvals

Connection is not approval; scope still matters.

Security

Wallet security

Keys, devices, signatures and transaction checks.

Ethereum and Proof of Stake

Understand validator duties, reward sources, exit paths and risks before deciding whether deeper participation is appropriate.

Ethereum Staking Basics

Ethereum PoS uses validators to participate in consensus. Rewards vary with network conditions and validator performance, while exits and withdrawals may involve waiting.

Learn the basics →

What to understand first

Validators can face protocol penalties. Smart-contract risk, third-party service risk and digital-asset price volatility also matter. Staking does not guarantee returns.

Understand validators →

Product and security updates

Notices use category labels without inventing dates, partnerships, funding claims or market rankings.

Recent UpdateProduct guidance continues to expandView →
NetworkReconfirm the destination chain before cross-network actionsView →
Security NoticeReview signatures and approvals one request at a timeView →
ServiceUse the site notice page for current service informationView →

Frequently asked questions

The full FAQ covers 16 topics across wallets, networks, Web3, security and validators.

Assets are recorded on the relevant blockchain. The wallet manages accounts and signing authority.

No. Seed phrases and private keys should remain under your custody.

Gas is the network fee used to submit or execute a blockchain transaction.

No. Connection, signatures and token approvals are separate actions.

A Layer 2 processes some activity outside the base chain and uses a defined settlement or data-publication mechanism.

No. Rewards can change and there may be penalties, waiting periods and market risk.

View the complete FAQ →

Get imtoken

Every download action leads to the local download page. Before any on-chain action, understand backups, networks, transactions and approval safety.

Download imtoken