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

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 balances and network selection to transfers, DApp connections, signatures, approvals and wallet security, imtoken brings practical actions and on-chain knowledge into one clear path. Review the address, network and request details every time, and keep recovery information under your own control.

Multi-chain AssetsNetwork ChecksDApp ConnectionsApproval ManagementOn-chain Verification
imtoken mobile wallet product view
01

Create a Wallet

Understand accounts, addresses and recovery information before you create one.

Learn the basics →
02

Back Up a Wallet

Keep the seed phrase offline. Do not screenshot, upload or send it to anyone.

Backup principles →
03

Receive Assets

Verify the receiving address and network before expecting a transfer.

Receiving guide →
04

Send Assets

Check the address, network, amount, gas and any required memo before sending.

Transfer checks →
05

Connect to a DApp

Connections, signatures, transactions and approvals are separate actions.

Connection flow →
Wallet Capabilities

Keep the on-chain context clear from balances to transactions

A wallet does more than show balances. It connects addresses, networks, transactions and permissions. Understanding those relationships makes each confirmation easier to evaluate.

Multi-chain Assets

Identify the network before interpreting the asset

The same asset name can exist on different networks. Verify the network, address format and token contract before drawing conclusions from a balance or transaction.

Multi-chain network relationship illustration

Send & Receive

Build a complete check around the receiving address, network, amount, gas and transaction hash.

View the flow →

imtoken App

Use the mobile wallet to view assets, manage networks, follow transaction history and review critical fields before confirming.

imtoken app product view

imtoken Web & DApp Access

A browser connection only establishes account interaction. Signatures, transactions and token approvals still require independent review of the target, request details and permission scope.

Understand web connections →

Wallet Security

Keep seed phrases and private keys offline and private. Treat unfamiliar approvals, remote access and phishing domains with caution.

Offline wallet key protection illustration
Blockchain Networks

Understand the active network before interpreting the transaction

Public chains, EVM networks, Layer 2 systems and gas mechanisms each carry their own context. After switching networks, assets, fees, confirmation speed and explorers may all change.

Multi-chain means multiple network contexts

Each chain has its own network state, fee asset, confirmation behavior and explorer. A similar-looking address never replaces a network check.

Explore multi-chain →
Multi-chain network relationship illustration

Public chains run through nodes, blocks and consensus

After broadcast, a transaction must be received and included by the network. Confirmation and finality depend on that chain's mechanism.

Understand public chains →
Public blockchain structure illustration

EVM compatibility does not make networks identical

Similar addresses and contract models do not replace checks for chain ID, gas asset and destination network.

Understand EVM →
EVM-compatible network illustration

Layer 2 systems maintain a relationship with mainnet

Cross-layer transfers can involve a bridge, waiting and multiple confirmations. Verify source and destination networks before choosing a route.

Understand Layer 2 →
Layer 2 and mainnet relationship illustration

Gas reflects network execution cost

Fees vary with network rules, congestion and transaction complexity. When a transaction is pending, inspect its hash before repeating the action.

Gas & confirmations →
Use the relevant network's on-chain data as an important reference for transaction state.
Wallet Path

Turn every step into something you can verify

From getting the wallet to reviewing transactions and approvals, the goal is not speed. It is knowing what each confirmation means.

Get imtoken

Use the site's unified download entry and verify the source you are visiting.

01

Create or import a wallet

Know whether you are creating a new account or restoring one, and keep recovery material under your control.

02

Back up offline

Do not screenshot, upload or send seed phrases or private keys.

03

Select and verify the network

Confirm the target chain, gas asset and recipient-supported network.

04

Receive or send assets

Review the address, network and amount, and use a small test transfer when appropriate.

05

Review transactions and approvals

Keep the transaction hash, verify confirmation and revisit DApp permissions that are no longer needed.

06
Web3 & DApps

A connection is only the beginning; review every request on its own

Before entering a DApp, verify the domain and network. After connecting, inspect what the site is asking for. Message signatures, transaction signatures and token approvals have different effects, so treat each as a separate decision.

Security reminder

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

Open the Web3 guide →
  1. Visit the DApp
    Start from a source you trust.
  2. Verify the domain
    Check spelling, origin and network context.
  3. Start the connection
    Expose only the account needed.
  4. Review account requests
    Understand what the DApp wants to access.
  5. Inspect signatures or approvals
    Check the target, allowance and request details.
  6. Complete the action
    Verify the result on-chain.
  7. Disconnect when no longer needed
    Review standing approvals as well.
Security

Security comes from repeated verification, not a blanket promise

Wallet security spans recovery material, devices, networks, DApps, signatures, approvals and transfers. Keep seed phrases and private keys under your own control. Official personnel will not ask for them, and they should never be sent to anyone. Be especially careful with public devices, public networks, remote-control tools, fake support messages, unsolicited airdrops and phishing links. Because confirmed on-chain transactions generally cannot be reversed by a wallet alone, verify addresses, networks, amounts and contract requests before approving them.

Open the security center →
Offline wallet key protection illustration
  • Back up seed phrases offline
  • Do not disclose private keys
  • Verify networks and addresses
  • Read signature requests
  • Manage DApp approvals
Academy · Featured

What Should You Understand Before Using a Digital Wallet?

An address identifies where assets can be received; seed phrases and private keys relate to account control; the network determines where the asset lives and how gas works; the transaction hash is used to inspect on-chain status; DApp connections, signatures and approvals introduce distinct permission layers. Understanding how these concepts fit together is more useful than memorizing a sequence of taps.

Start with the fundamentals →
Scaling

Layer 2 Basics

Mainnet relationships, bridges and arrival checks.

Ethereum & PoS

Understand the mechanism before deciding whether to participate

Staking does not guarantee returns. Rewards, exit waiting, validator state, protocol penalties, smart-contract risk and market volatility can all affect outcomes.

Ethereum Staking Fundamentals

Ethereum PoS uses validators to participate in block proposals and attestations. Reward sources, network state, withdrawals and exits can change with protocol conditions and should not be read as a fixed annual return.

Understand staking →

Know Before Participating

Validators can face protocol penalties, exits can involve waiting, third-party services and smart contracts add risk, and digital asset prices can fluctuate.

Understand validators →
Product & Security Updates

Prioritize actionable information when something changes

View all updates →
Recent Update

Product notice: unified download entry and onboarding path

All download actions begin from the site's download entry. Content pages do not trigger downloads automatically.

View →
Network

Network reminder: verify the destination chain before sending

Similar address formats never replace checks for network, gas asset and recipient support.

Learn →
Security

Security reminder: no one should ask for your seed phrase

Be cautious with fake support, unfamiliar links, remote access and requests to export private keys.

Learn →
Service

Service note: staking rewards and exit timing can change

Understand validator mechanics, protocol queues, contract risk and market volatility before participating.

Learn →
FAQ

Start with the most common on-chain questions

View full FAQ →

No. Seed phrases and private keys should remain under the user's control, and official personnel will not ask for them.

Compatible address formats do not make networks identical. Assets, gas and transaction state still belong to their respective networks.

Keep the transaction hash and inspect its state on the relevant network before repeating the action.

Connections, signatures, transactions and token approvals are independent requests with different permission effects.

Cross-layer routes can involve bridges, batch submission, challenge periods or other protocol-specific mechanisms.

No. Rewards can change with protocol, validator and network conditions, while asset prices can also fluctuate.

imtoken

Start with a clear first step

Use the unified download entry, then follow the beginner path through creation, backup, network checks and on-chain verification.

Download imtoken