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
Home / Multi-chain
imtoken

Multi-chain

A practical imtoken guide to multi-network assets, chain IDs, native assets and bridging, with clear checks for network, permissions and security.

Download imtoken

Core concepts

Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities. In the context of multi-network assets, it also helps to connect chain IDs with native assets rather than treating them as isolated features. When checking state, prefer verifiable evidence such as network, address, contract and transaction hash. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare multi-network assets with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Practical workflow

When checking state, prefer verifiable evidence such as network, address, contract and transaction hash. In the context of chain IDs, it also helps to connect native assets with bridging rather than treating them as isolated features. Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare chain IDs with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

multi-network assets

Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities.

chain IDs

When checking state, prefer verifiable evidence such as network, address, contract and transaction hash.

native assets

Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules.

bridging

When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface.

Checks before confirmation

Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules. In the context of native assets, it also helps to connect bridging with multi-network assets rather than treating them as isolated features. When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare native assets with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Review checklist

  • Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities.
  • When checking state, prefer verifiable evidence such as network, address, contract and transaction hash.
  • Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules.
  • When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface.

Risks and follow-up

When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface. In the context of bridging, it also helps to connect multi-network assets with chain IDs rather than treating them as isolated features. Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare bridging with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Key risks

  • Never share a seed phrase, private key or verification code.
  • Third-party DApps, networks and contracts can fail or behave maliciously.
  • Staking and digital assets do not offer guaranteed returns or protection from price volatility.