imtoken Knowledge Center
Layer 2｜imtoken
Understand Layer 2 relationships with base layers, bridges, settlement and network selection.
On this page
Why Layer 2 exists
To understand Layer 2, place why layer 2 exists inside the full on-chain workflow instead of treating it as an isolated label. Layer 2 networks remain distinct environments even when they settle to a base layer. Moving assets across layers usually requires a bridge rather than a normal transfer. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Withdrawal timing depends on the Layer 2 design and current network state. The recipient must support the destination network. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach why layer 2 exists is to use a consistent review sequence. First, layer 2 networks remain distinct environments even when they settle to a base layer. Next, moving assets across layers usually requires a bridge rather than a normal transfer. After a transaction, signature or approval is submitted, withdrawal timing depends on the layer 2 design and current network state. Finally, the recipient must support the destination network. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Layer 2 networks remain distinct environments even when they settle to a base layer
- Moving assets across layers usually requires a bridge rather than a normal transfer
- Withdrawal timing depends on the Layer 2 design and current network state
- The recipient must support the destination network
Base layer and Layer 2
To understand Layer 2, place base layer and layer 2 inside the full on-chain workflow instead of treating it as an isolated label. Layer 2 networks remain distinct environments even when they settle to a base layer. Moving assets across layers usually requires a bridge rather than a normal transfer. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Withdrawal timing depends on the Layer 2 design and current network state. The recipient must support the destination network. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach base layer and layer 2 is to use a consistent review sequence. First, layer 2 networks remain distinct environments even when they settle to a base layer. Next, moving assets across layers usually requires a bridge rather than a normal transfer. After a transaction, signature or approval is submitted, withdrawal timing depends on the layer 2 design and current network state. Finally, the recipient must support the destination network. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Layer 2 networks remain distinct environments even when they settle to a base layer
- Moving assets across layers usually requires a bridge rather than a normal transfer
- Withdrawal timing depends on the Layer 2 design and current network state
- The recipient must support the destination network
Bridges and cross-layer transfers
To understand Layer 2, place bridges and cross-layer transfers inside the full on-chain workflow instead of treating it as an isolated label. Layer 2 networks remain distinct environments even when they settle to a base layer. Moving assets across layers usually requires a bridge rather than a normal transfer. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Withdrawal timing depends on the Layer 2 design and current network state. The recipient must support the destination network. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach bridges and cross-layer transfers is to use a consistent review sequence. First, layer 2 networks remain distinct environments even when they settle to a base layer. Next, moving assets across layers usually requires a bridge rather than a normal transfer. After a transaction, signature or approval is submitted, withdrawal timing depends on the layer 2 design and current network state. Finally, the recipient must support the destination network. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Layer 2 networks remain distinct environments even when they settle to a base layer
- Moving assets across layers usually requires a bridge rather than a normal transfer
- Withdrawal timing depends on the Layer 2 design and current network state
- The recipient must support the destination network
Arrival and network selection
To understand Layer 2, place arrival and network selection inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify arrival and network selection in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach arrival and network selection is to use a consistent review sequence. First, the practical point is to verify arrival and network selection in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- The practical point is to verify arrival and network selection in the context of the selected blockchain network
- The user should compare the request with the intended address, asset, account or contract before confirming
- On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
- Third-party DApps, services and smart contracts can introduce risks that need separate review