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.

Multi-chain

Understand how multi-chain wallets manage different networks and how to avoid chain-selection mistakes.

On this pageWhat multi-chain meansSwitching network contextSame-name token differencesChecks before cross-chain actionsMulti-chain risks

What multi-chain means

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For what multi-chain means, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For what multi-chain means, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Switching network context

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For switching network context, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For switching network context, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Same-name token differences

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For same-name token differences, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For same-name token differences, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Checks before cross-chain actions

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For checks before cross-chain actions, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For checks before cross-chain actions, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.

Multi-chain risks

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For multi-chain risks, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

A practical check

The first step in any on-chain action is confirming the network. The selected network determines where the transaction is broadcast, how fees are calculated, which explorer can verify status, and what confirmation rules apply. Similar address formats are not proof that assets are on the same network. For multi-chain risks, separate the object you are acting on, the active network, the expected outcome, and the evidence you can independently verify. Do not rely on interface wording alone; use addresses, transaction hashes, explorers, and contract details where appropriate. For this topic, a useful sequence is: understand the concept, check before acting, submit only when the details are clear, verify on-chain status, and review any permissions that remain afterward.

Before proceeding, confirm the network, the address or contract, the amount or permission scope, and the expected result. Keep sensitive recovery information offline and never send a seed phrase, private key, or verification code to another person.
On-chain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps, smart contracts, bridges, and staking services may involve technical or operational risk. Digital-asset prices can also fluctuate. Review each action based on your own circumstances.

Keep learning with imtoken

Use the related guides to understand the network, permissions, and security checks before your next on-chain action.

Download imtoken