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.
Home / Layer 2

Layer 2

Learn how Layer 2 relates to the base layer, including bridging, settlement, and network selection.

On this pageWhy Layer 2 existsRelationship with the base layerBridging across layersArrival and confirmation timingNetwork-selection checks

Why Layer 2 exists

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. Layer 2 systems can differ in settlement, bridging, and withdrawal mechanics. Before moving assets across layers, verify the source network, destination network, bridge path, and expected waiting time. 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. Layer 2 systems can differ in settlement, bridging, and withdrawal mechanics. Before moving assets across layers, verify the source network, destination network, bridge path, and expected waiting time. 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.

Relationship with the base layer

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. Layer 2 systems can differ in settlement, bridging, and withdrawal mechanics. Before moving assets across layers, verify the source network, destination network, bridge path, and expected waiting time. 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. Layer 2 systems can differ in settlement, bridging, and withdrawal mechanics. Before moving assets across layers, verify the source network, destination network, bridge path, and expected waiting time. 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.

Bridging across layers

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. Layer 2 systems can differ in settlement, bridging, and withdrawal mechanics. Before moving assets across layers, verify the source network, destination network, bridge path, and expected waiting time. 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. Layer 2 systems can differ in settlement, bridging, and withdrawal mechanics. Before moving assets across layers, verify the source network, destination network, bridge path, and expected waiting time. 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.

Arrival and confirmation timing

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 arrival and confirmation timing, 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 arrival and confirmation timing, 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.

Network-selection checks

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 network-selection checks, 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 network-selection checks, 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