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 · Multi-chain digital wallet

Manage Multi-chain Assets and Connect to Web3 with Clarity

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

Manage assets across networks, review send and receive details, understand DApp connections and token approvals, and build practical knowledge around networks and wallet security.

Multi-chain assetsEVMLayer 2DAppApproval review
imtoken mobile wallet interface
01Create a WalletUnderstand account creation and what recovery material controls before you begin.
Open guide →
02Back Up a WalletKeep recovery material offline and avoid screenshots, chat transfers or untrusted forms.
Open guide →
03Receive AssetsMatch the sending network with your receiving address and verify the token network.
Open guide →
04Send AssetsReview destination, network, amount, gas and final transaction details before confirming.
Open guide →
05Connect to a DAppVerify the domain, requested account and network before reviewing later signatures separately.
Open guide →
Wallet capabilities

From viewing assets to on-chain actions, keep every decision clear

A wallet organizes multi-network information and submits on-chain requests. Networks, contracts and user confirmation determine outcomes, so each capability should be understood on its own terms.

Multi-chain assets

Multi-chain network relationship

Separate an asset’s network, address format, gas asset and confirmation state. Similar names and address formats do not make contracts or networks equivalent.

Understand multi-chain →

Send & receive

Confirm network and address for receiving; before sending, review amount, gas, transaction details and the final confirmation.

View the workflow →

imtoken APP

imtoken App product interface

Review assets, networks and activity on mobile while treating every DApp request as a separate decision.

imtoken Web

Use the browser environment to inspect connections, account requests and approvals. A connection never makes later signatures automatically trustworthy.

Explore Web use →

Wallet security

Wallet key security

Seed phrases and private keys remain under user control; never send them to anyone or enter them into untrusted pages.

Blockchain networks

Understand the network before moving assets

Multi-chain

One wallet can understand several networks, but every action still needs a clear chain, fee asset and settlement path.

Read more →
Multi-chain

Public chains

Nodes, blocks, transactions and confirmations form a verifiable public ledger state.

Read more →
Public chains

EVM

EVM networks share a contract execution model while chain IDs, gas, assets and deployments remain independent.

Read more →
EVM

Layer 2

Scaling networks maintain a defined relationship with mainnet; cross-layer actions require bridge and exit context.

Read more →
Layer 2

Gas & confirmations

Fees and confirmation times change with network conditions; transaction hashes help verify later status.

Read more →
Gas & confirmations
Usage path

A six-step path to a repeatable wallet routine

01

Get imtoken

Use the official download entry and avoid unverified installers.

02

Create or import a wallet

Understand the difference between creating and importing, and keep control of recovery material.

03

Back up offline

Keep seed phrases offline and never disclose private keys.

04

Select and verify the network

Check the network, address and fee asset before sending.

05

Receive or send assets

Confirm the destination network, amount and final request details.

06

Review transactions and approvals

Verify status by transaction hash and review DApp approvals you no longer need.

Web3 & DApp

Treat connections, signatures and approvals as separate decisions

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

Open Web3 guide →
Visit a DApp
Verify the domain
Start connection
Review account request
Inspect signature or approval
Complete the action
Disconnect unused sessions
Security

Security comes from decisions you can verify

Wallet security is not an absolute promise; it is a set of habits. Keep recovery material private, verify network, address and amount before transfers, and review DApp connections, signatures, transactions and approvals separately. Public devices, untrusted networks and remote-control sessions add risk. On-chain transactions are generally not reversible by a wallet, making pre-confirmation review essential.

Open Security Center →
Wallet security review
  • Back up seed phrases offline
  • Never disclose private keys
  • Verify network and address
  • Inspect signature requests
  • Manage DApp approvals
Academy

What Should You Understand Before Using a Digital Wallet?

Start with addresses, seed phrases, private keys and networks, then move into gas, transaction hashes, DApps and approvals. Learning in the order you use these concepts makes later decisions easier to verify.

Read the starter guide →
Ethereum · PoS

Understand validation mechanics without treating staking as a fixed-return product

Ethereum Staking Basics

Ethereum PoS uses validators for attestations and block proposals. Rewards depend on protocol conditions, while exits and withdrawals can involve waiting periods.

Learn Ethereum staking →

What to understand before participating

Validators can face protocol penalties, smart contracts carry technical risk, digital asset prices fluctuate, and third-party services can add risk. Staking does not guarantee rewards.

Explore PoS and validators →
Product & security updates

Recent guidance and notices

Product Notice
How to read wallet and network context

Confirm the network before reading asset and transaction details to reduce cross-network mistakes.

Network
Confirmation timing can vary

Congestion and protocol rules can affect fees and confirmation timing.

Security Notice
Never share recovery material

Seed phrases, private keys and verification codes should not be shared through chat, forms or remote-control tools.

Service
Downloads use one controlled entry

All product download actions start from the controlled download entry and require a user click.

FAQ

Frequently asked questions

A seed phrase can derive wallet keys, while a private key directly signs for a specific account. Keep both private.

Assets and fees exist within a network context. Sending on the wrong network can lead to loss or a difficult recovery path.

Gas is the fee mechanism used by many networks to price execution and transaction inclusion.

No. Connection, signature, transaction and token approval are different actions and should be reviewed separately.

No. Seed phrases and private keys are controlled by the user and should never be sent to anyone.

No. Rewards can change, exits may take time and validators may face penalties or technical risk.

View full FAQ →

Start from a clear download entry

Downloads are handled on a dedicated page and only start from a user action.

Download imtoken