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

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

Manage Multi-chain Assets and Connect to Web3 with Clarity

From multi-chain assets and network selection to transfers, DApp connections and token approvals, imtoken brings wallet actions and blockchain knowledge into one clear path. Understand the network, address, fee and permission scope before you confirm, so security review becomes part of everyday wallet use.

Multi-chain assetsNetwork checksDApps & approvalsWallet security
imtoken multi-chain wallet interface
01

Create a Wallet

Understand accounts, addresses and recovery information before creating a new wallet.

Start here →
02

Back Up a Wallet

Keep the seed phrase offline. Do not screenshot it, upload it to cloud storage or share it.

Backup principles →
03

Receive Assets

Confirm the intended network before sharing an address so that network context stays clear.

Receive steps →
04

Send Assets

Review the address, network, amount and gas before sending, with a test transfer when appropriate.

Pre-send checks →
05

Connect to a DApp

Verify the domain, then review account, signature and approval requests independently.

Connection guide →

Wallet capabilities shaped around real tasks

Asset views, network management, transaction history and Web3 connections are related parts of the same workflow. Understanding how they interact makes multi-network decisions easier to verify.

Multi-chain assets

Keep network context clear across chains

The same address format can appear on several EVM networks, while balances, transactions and gas states remain separate. Review the selected network, token contract and confirmation state together.

Multi-chain network and asset relationship

imtoken App

Review assets and requests on mobile

See networks, assets, transaction history and DApp requests in one flow. For important actions, verify the source before reviewing the signature or approval.

imtoken App multi-chain asset view

Send & receive

Review the address, network, amount and gas together

Confirm the network when receiving. Before sending, recheck the destination and amount. After broadcast, use the transaction hash to inspect on-chain status.

View the full flow →

imtoken Web

Make each browser request a separate decision

Connecting an account does not approve future signatures. Recheck the domain, origin, permission scope and contract each time.

Learn about Web connections →

Wallet security

Keep recovery data offline and manage permissions deliberately

Seed phrases and private keys remain under the user’s control. Do not upload screenshots or send them to anyone. Review DApp approval targets and allowance amounts, and consider revoking permissions you no longer need.

Offline seed phrase and private key protection

Explore blockchain networks

Network names, address formats, gas, block height and confirmation rules define the context of an on-chain action. When switching networks, check where the transaction will actually occur.

Multi-chain use means multiple independent network contexts

Each network has its own blocks, transaction state and fee environment. Confirm the network so a matching address format is not mistaken for a matching chain.

Learn multi-chain basics →
Multi-chain network relationship

Public chains use distributed nodes to maintain an open ledger

After a transaction is broadcast, nodes process it and block producers include it. Additional blocks provide further confirmations.

Learn nodes and blocks →
Public chain nodes and blocks

EVM networks share compatible concepts but keep separate state

Address formats, contract interaction and gas models can look similar, while token contracts, balances and transactions must still be checked on the correct network.

Learn EVM basics →
EVM compatible networks

Layer 2 expands transaction processing above a base layer

Cross-layer transfers may involve bridges, batches or waiting periods. Review the source network, destination network and actual transfer status.

Understand Layer 2 →
Layer 2 and base network relationship

Gas represents the resource cost of on-chain execution

Fees can change with network conditions and transaction complexity. Once broadcast, use the transaction hash, block height and confirmation state to understand the result.

Learn fees and confirmations →

Review order

Network → fee → hash → confirmations

From obtaining a wallet to long-term security habits

Break the journey into actions that can be checked independently. Recovery information, network choice, transfers and approvals each have their own review points.

01

Get imtoken

Use the official download entry rather than an unknown installation link.

02

Create or import a wallet

Know whether you are creating a new account or restoring an existing one, and understand the role of recovery information.

03

Back up the wallet offline

Keep the seed phrase offline. Do not screenshot it, upload it or disclose the private key.

04

Select and verify the network

Confirm the network name, address format and intended use instead of relying on a familiar-looking address.

05

Receive or send assets

Verify the network when receiving and recheck the address, network, amount and gas before sending.

06

Review transactions and approvals

Use transaction hashes for on-chain results, inspect DApp signatures before confirming and review unused approvals regularly.

Web3 & DApps

A connection is only the beginning; review every request again

Verify the DApp domain before connecting. After connection, separately review account requests, message signatures, transaction signatures and token approvals. When finished, disconnect connections you no longer need and review ongoing permissions.

Connecting a wallet does not mean every signature request should be accepted. Review each signature and approval on its own.

Open the Web3 guide →

Visit the DApp

Use a trusted entry point.

Verify the domain

Check the complete domain and source.

Start the connection

Connect only the account you intend to use.

Review the account request

Understand what public account information is requested.

Check the signature or approval

Review the target, content, allowance and expected result.

Complete the action

Wait for on-chain confirmation and keep the transaction hash.

Disconnect when no longer needed

Reduce unnecessary ongoing connections and permissions.

Security

Security is a set of repeatable habits, not an absolute promise

Wallet security begins with ongoing control of recovery information, devices, transfer details and approval permissions. Seed phrases and private keys should remain under the user’s control, and legitimate staff should not ask for them or for verification codes. Check the address, network and amount before transferring. With third-party DApps, verify the domain, signature content, contract and approval scope. On-chain transactions usually cannot be reversed by a wallet alone, so irreversible actions deserve careful review before confirmation. Public devices, public Wi-Fi, remote-access tools and unknown links can increase risk; important actions are better handled on devices and networks you control.

Open Security Center
Wallet security and offline recovery protection
  • Back up the seed phrase offline
  • Do not disclose private keys
  • Verify networks and addresses
  • Review signature requests
  • Manage DApp approvals

Academy · Featured starter guide

What Should You Understand Before Using a Digital Wallet?

A wallet address identifies an account, seed phrases and private keys relate to control, the network determines where assets and transactions exist, gas reflects execution costs, a transaction hash lets you inspect a broadcast transaction, and DApps plus approvals extend wallet interaction to smart contracts. Connecting these ideas before transferring or using Web3 reduces mistakes caused by isolated definitions.

Read the starter guide →
Scaling

Layer 2 basics

Understand base-layer relationships and cross-layer transfers.

Ethereum & PoS knowledge

Understand staking as a network mechanism rather than a fixed-return product. Rewards, exit timing, validator state, contract risk and digital asset price volatility all deserve separate consideration.

Ethereum Staking

Ethereum staking basics

Ethereum PoS uses validators to participate in block proposal and attestation. Reward sources relate to network participation, while withdrawals and exits depend on protocol rules and network state and may involve waiting.

Understand staking →

Before participating

Validator, penalty, contract and market risks

Staking does not guarantee returns. Rewards can change, validators may face network penalties, smart contracts can carry technical risk, third-party services add separate risk, and digital asset prices can fluctuate.

Learn PoS & validators →

Product & security updates

Content-first notices about usage changes, network checks, security awareness and service information, without unverified claims about partners, scale or market position.

Recent Update · Product

A clearer wallet review path

Keep network, address, transaction state and approval target in one continuous review flow.

Security Notice

Be cautious of requests for seed phrases or private keys

Do not continue any conversation that asks for recovery secrets.

Network

Confirm the destination network before cross-network actions

A matching address format does not make networks interchangeable.

Product Notice

DApp connection and token approval are different actions

Review each signature and approval separately after connecting.

Service

Use the unified imtoken download entry

All download actions across the site lead to the same official download page.

Frequently asked questions

Quick answers about recovery information, networks, gas, transaction hashes, DApp approvals and Ethereum staking.

Can I send my seed phrase to support for recovery?

No. Seed phrases and private keys should remain under the user’s control. Legitimate support should not request them.

What should I check before a transfer?

At minimum, verify the destination address, target network, amount and expected gas. A small test transfer may be useful in some situations.

What can a transaction hash tell me?

It can be used with a block explorer to check broadcast state, inclusion, block height and confirmations.

Does connecting a DApp equal a token approval?

No. Connection, message signing, transactions and approvals are separate requests and should be reviewed separately.

Why can Layer 2 transfers take time?

Different networks use different settlement, batching and exit rules, so waiting depends on the actual network mechanism.

Does Ethereum staking guarantee returns?

No. Rewards can change, exits can involve waiting, validators can be penalized, and contract plus market risks remain.

View all FAQs →

imtoken

Start every wallet action with a clear review

Use the unified download entry for imtoken and check the relevant network, address, signature or approval before confirming.

Download imtoken