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

Manage assets across networks, verify addresses and fees before transfers, connect to DApps with explicit signature and approval checks, and build a practical understanding of network behavior and wallet security.

Multi-chainWeb3 & DAppEVMLayer 2Security
imtoken app interface
01Create a Wallet

Prepare the right network and recovery plan before you begin.

02Back Up a Wallet

Prepare the right network and recovery plan before you begin.

03Receive Assets

Prepare the right network and recovery plan before you begin.

04Send Assets

Prepare the right network and recovery plan before you begin.

05Connect to a DApp

Prepare the right network and recovery plan before you begin.

Wallet capabilities

One wallet workflow, several distinct decisions

Multi-chain assets

Multi-chain network illustration

Separate asset names from the networks that actually carry them.

imtoken App

imtoken mobile app

View assets, manage networks, review history, and prepare DApp actions.

Send & Receive

Check receiving address, network, amount, gas, and the resulting transaction hash.

imtoken Web

Use browser connections deliberately: confirm the domain, requested account, signature, and permission.

Wallet security

Offline key security

Keep seed phrases and private keys offline and review approvals regularly.

Network explorer

Understand the network before the transaction

Multi-chain

Understand how assets and transactions live on different networks and why network selection matters.

Read the guide
Multi-chain

Public Chains

Connect nodes, blocks, and confirmations to the lifecycle of a public-chain transaction.

Read the guide
Public Chains

EVM

See how EVM addresses, gas, contracts, and token approvals fit together.

Read the guide
EVM

Layer 2

Understand Layer 2 relationships to mainnet, cross-layer transfers, and settlement checks.

Read the guide
Layer 2
Wallet path

A six-step path from setup to verification

01

Get imtoken

Verify each request and keep recovery material offline. Review addresses, networks, and approvals before confirmation.

02

Create or import a wallet

Verify each request and keep recovery material offline. Review addresses, networks, and approvals before confirmation.

03

Back up the wallet offline

Verify each request and keep recovery material offline. Review addresses, networks, and approvals before confirmation.

04

Choose and verify the network

Verify each request and keep recovery material offline. Review addresses, networks, and approvals before confirmation.

05

Receive or send assets

Verify each request and keep recovery material offline. Review addresses, networks, and approvals before confirmation.

06

Review transactions and approvals

Verify each request and keep recovery material offline. Review addresses, networks, and approvals before confirmation.

Web3 & DApp

A connection is only the beginning of the review

Connecting a wallet does not mean every signature or approval should be accepted. Treat each request as a separate decision.

Web3 guide
Visit the DApp
Verify the domain
Start the connection
Review account requests
Inspect signatures or approvals
Complete the action
Disconnect unused sessions
Security

Security comes from repeatable checks, not absolute promises

Protect seed phrases and private keys, keep backups offline, verify domains, inspect signatures, and compare the address, network, and amount before transfers. Public devices and networks add risk, and third-party contracts can behave independently from the wallet interface.

Open Security Center
Wallet security
  • Back up the seed phrase 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, networks, gas, transaction hashes, DApps, and approvals. Each concept answers a different question about ownership, routing, fees, verification, or permission.

Start learning
Public chains and confirmationsEVM & Smart ContractsLayer 2DApp approvalsWallet securityBlockchain glossary
Ethereum & PoS

Ethereum Staking Basics

Learn how Ethereum PoS validators participate in consensus, where rewards come from, how exits work, and why network status matters.

Read about staking

Know before participating

Rewards are not guaranteed. Waiting times, penalties, contract risk, service-provider risk, and asset-price volatility can all affect outcomes.

PoS & validators
Updates

Recent guidance and notices

Recent Update
Wallet workflow guidance

Review setup, backup, network selection, and verification as one continuous process.

Security Notice
Review every signature request

Connection does not imply consent to later signatures or approvals.

Network
Check network and confirmation state

Use a transaction hash and block explorer when a status is unclear.

Service
Support boundaries

Support never requires your seed phrase, private key, or verification code.

FAQ

Common questions before you act

A wallet manages key material and presents on-chain account information. An address is a public identifier used to receive assets; seed phrases and private keys must remain private.

It is not recommended. Screenshots can be synced to cloud services or accessed by other applications. Offline physical storage is generally safer.

A private key can control a specific account, while a seed phrase can derive multiple accounts. Both are highly sensitive recovery material.

The same asset name can exist on different networks. A transfer on the wrong network may not be recognized or processed as expected by the recipient.

Gas represents the computational resources used by a network to process transactions or contract interactions. Fees vary with network demand and transaction complexity.

A transaction hash identifies a specific on-chain transaction and can be used in a block explorer to inspect broadcast, inclusion, and confirmation status.

View all FAQs

Use imtoken with a clear verification path

Download entry, network knowledge, Web3 guidance, and security checks are available from the same site.

Download imtoken