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 wallet official site

Manage Multi-chain Assets and Connect to Web3 with Clarity

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

From multi-chain assets, network selection, sending and receiving to DApp connections, signatures, approvals, network knowledge and wallet security, imtoken brings common workflows and critical checks into one clear path. Understand what each step does, decide deliberately, and verify outcomes using on-chain records.

Multi-chain AssetsNetwork ChecksDApps & ApprovalsWallet Security
imtoken mobile wallet product view
01

Create a Wallet

Understand wallets, addresses and control before creating an account.

View steps →
02

Back Up a Wallet

Keep the seed phrase offline, avoid screenshots and never disclose private keys.

Backup guide →
03

Receive Assets

Verify both the receiving address and network before sharing details.

Receive guide →
04

Send Assets

Review the address, network, amount and gas before submitting a transaction.

Transaction checks →
05

Connect to a DApp

Verify the domain and account request; inspect every signature and approval separately.

Connection guide →

Wallet capabilities

See assets, networks and actions as one connected workflow

Different tasks require different information. Multi-chain assets, mobile wallet use, browser connections and security are presented with distinct structures instead of one repeated pattern.

Multi-chain Assets

Recognize network-specific assets, address context and confirmations. Same-name tokens can exist on different chains, so verify the network and contract information instead of relying only on a display name.

Multi-chain network and asset relationship

imtoken App

View assets, manage networks, review transaction history and access DApps from a mobile device while keeping installation source, screen lock and network environment in mind.

imtoken App product view

Send & Receive

Check address and network when receiving; check amount, gas and transaction hash when sending. After submission, prioritize the on-chain record.

View the workflow →

imtoken Web

A browser connection creates a session, not blanket approval for future signatures. Review every signature and token approval independently.

Understand Web connections →

Wallet Security

Seed phrases and private keys remain under user control. Offline backup, address checks, approval reviews and device security work best as a repeatable checklist.

Offline private-key generation and storage concept

Blockchain Networks

Understand the network before making an on-chain action

Network selection affects addresses, gas, confirmations and asset display. All panel text remains present in the server-rendered HTML when JavaScript is unavailable.

Multiple chains are not one shared ledger

Each chain has its own blocks, nodes, fees and confirmation rules. When switching networks, verify where the asset exists, what network the recipient supports and whether same-name tokens could be confused.

Multi-chain network structure

Public chains coordinate state through network nodes

Transactions propagate through the network and are recorded in blocks. Block explorers help verify transaction hashes, block height and confirmation status.

Public-chain node and block relationship

EVM networks share an execution model, not a single chain

Similar address formats and tooling can be confusing. Before transfers or approvals, verify the active chain, contract address and gas asset.

EVM-compatible networks

Layer 2 networks have a specific relationship with mainnet

Cross-layer transfers may involve bridges, waiting periods and distinct arrival confirmations. An identical-looking address does not remove the need to verify the network.

Layer 2 and mainnet relationship

Gas and confirmations reflect network resources and state

Gas is not a fixed wallet charge. Congestion, transaction complexity and fee parameters can affect processing, while the transaction hash remains a key reference for status checks.

Learn about gas →
05

Verify the network first, then judge fees and waiting time.

Wallet journey

From obtaining imtoken to checking transactions and approvals

A repeatable sequence makes it easier to stop, verify and continue without skipping important checks.

01

Get imtoken

Use a trusted entry point to the download page and initiate downloads only through a deliberate user click.

02

Create or import a wallet

Understand the difference between creation and import. A website should not ask you to submit a seed phrase or private key into a form.

03

Back up offline

Keep the seed phrase offline; avoid screenshots, casual cloud sync and sharing it with supposed support staff.

04

Select and verify the network

Confirm that the asset network matches the recipient’s supported network and that the correct gas asset is available.

05

Receive or send assets

Check address and network when receiving; review amount, fees and destination again before sending.

06

Review transactions and approvals

Use the transaction hash to verify the on-chain outcome and periodically review DApp approvals you no longer need.

Web3 & DApps

A connection is only the beginning; review every request independently

Verify the DApp domain and purpose before connecting. Connecting a wallet does not mean every signature request should be accepted. Each signature and approval deserves its own review.

Open the Web3 guide →
  1. Visit the DApp
  2. Verify the domain
  3. Start the connection
  4. Review the account request
  5. Inspect the signature or approval
  6. Complete the action
  7. Disconnect unused sessions

Security

Keep critical credentials inside an environment you control

Seed phrases and private keys remain under user custody. Official staff will not ask for a seed phrase, private key or verification code. Verify the address, network and amount before transfers, and verify the domain, signature content and approval scope before DApp actions. Blockchain transactions are generally not reversible by a wallet provider, and third-party DApps or contracts may introduce risk.

Open Security Center →
Offline wallet key security concept
  • Back up the seed phrase offline
  • Do not disclose private keys
  • Verify network and address
  • Inspect signature requests
  • Manage DApp approvals

Academy

Start with the concepts that matter before first using a digital wallet

The learning path begins with addresses, seed phrases and private keys, then moves through networks, gas, transaction hashes, DApps and approvals.

Featured starter

What Should You Understand Before Using a Digital Wallet?

An address is a public receiving identifier, while seed phrases and private keys relate to account control. The network determines where a transaction occurs, gas pays for on-chain execution, a transaction hash identifies the record, and DApp connections, signatures and approvals represent different levels of interaction.

Start learning →
Network basics

Public Chains & Confirmations

Understand blocks, nodes and confirmation counts.

Contracts

EVM & Smart Contracts

Addresses, gas, contracts and token approvals.

Scaling

Layer 2 Basics

Mainnet relationships, bridges and arrival checks.

Web3 security

DApp Approvals

Review approval target, amount and revocation.

Security basics

Wallet Security

Combine backup, device and transaction checks.

Terminology

Blockchain Glossary

Learn common on-chain terms through user tasks.

Ethereum & PoS

Understand validators and network rules before deciding whether to participate

Staking does not guarantee returns. Rewards can change, exits may involve waiting, validators may face network penalties, and smart contracts or third-party services carry technical risk.

Ethereum Staking Basics

Learn about Ethereum PoS, validators, reward sources, network state, withdrawals and exits without treating network rewards as a fixed-yield or principal-protected product.

Read the basics →

What to Understand Before Participating

Network penalties, validator state, smart-contract risk, waiting periods, asset-price volatility and third-party service risk can all affect outcomes.

Explore PoS & Validators →

Product & Security Updates

Put the useful information first

When no verified date is available, use neutral labels instead of inventing partnerships, financing, licenses, user counts or market rankings.

Recent Update · Product

Wallet and network learning paths reorganized

Task-oriented navigation connects wallet, network, Web3 and security concepts more directly.

Security Notice

Support should never ask for a seed phrase or private key

Stop any flow that asks for account-control credentials and verify the entry point again.

Network Notice

Same-name assets do not imply the same network

Verify the network, contract and recipient support before transferring.

Service Notice

Downloads use one /download.html entry point

Content pages do not reveal the final mobile download destination.

FAQ

Frequently Asked Questions

Answers focus on practical decisions around wallet control, network selection, gas, transaction hashes, DApps and approvals.

Where are wallet assets actually stored?

Assets are generally recorded on the blockchain. The wallet manages account control, constructs transactions and reads network state.

How are seed phrases and private keys different?

Both relate to account control and should never be sent to anyone or submitted into a web form.

Why must I verify the network before a transfer?

Similar address formats may exist on different networks, and sending through the wrong network can be difficult or impossible to recover.

Who receives gas fees?

Gas reflects network execution and block resources; it is not simply a fixed wallet service charge.

What is a transaction hash for?

It identifies an on-chain transaction and can be used in a suitable block explorer to check status, block and confirmations.

Can I approve signatures automatically after connecting a DApp?

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

Should approvals be reviewed later?

Yes. Consider revoking permissions you no longer use and check the approval target, amount and contract address.

Does Ethereum staking guarantee returns?

No. Rewards, waiting periods, validator state, network penalties and digital-asset prices can all change.

View full FAQ →

imtoken

Start with a clear, verifiable workflow

Understand networks, addresses and security principles before managing multi-chain assets or connecting to Web3.

Download imtoken