On this page
Core concepts
After a Layer 2 task is completed, review bridges and arrival confirmations to make sure the outcome matches the intent. Long-lived approvals and persistent connections should be revisited periodically. Good wallet hygiene is a repeated process of checking critical details and retaining traceable on-chain information, not a one-time setting.
For Layer 2, first define its role in the current task, then check whether mainnet relationship and cross-layer transfers are consistent. When bridges is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For arrival confirmations, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: Layer 2
- Cross-check: mainnet relationship and cross-layer transfers
- Review carefully: bridges
- Verify afterward: arrival confirmations
Checks before you act
To understand Layer 2, treat mainnet relationship and cross-layer transfers as parts of the same on-chain workflow. The interface is only the entry point; the selected network, current chain state and permission scope determine what actually happens. Confirm the destination, source and network before continuing so the meaning of the request stays clear.
For mainnet relationship, first define its role in the current task, then check whether cross-layer transfers and bridges are consistent. When arrival confirmations is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For Layer 2, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: mainnet relationship
- Cross-check: cross-layer transfers and bridges
- Review carefully: arrival confirmations
- Verify afterward: Layer 2
How to evaluate a live request
cross-layer transfers rarely appears in isolation. It often intersects with bridges and arrival confirmations. A useful pattern is to separate each action into four checks: identify the object, verify the network, review permissions, and confirm the result. If one of those checks cannot be completed, stop and verify rather than relying on an unfamiliar site or remote instructions.
For cross-layer transfers, first define its role in the current task, then check whether bridges and arrival confirmations are consistent. When Layer 2 is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For mainnet relationship, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: cross-layer transfers
- Cross-check: bridges and arrival confirmations
- Review carefully: Layer 2
- Verify afterward: mainnet relationship
Risks and boundaries
When using imtoken for Layer 2, prioritize information that can be independently verified, such as addresses, network names, contract addresses, transaction hashes and block-explorer records. Visual design, urgency messages or claims from an unknown support account are not substitutes for verifiable on-chain details.
For bridges, first define its role in the current task, then check whether arrival confirmations and Layer 2 are consistent. When mainnet relationship is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For cross-layer transfers, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: bridges
- Cross-check: arrival confirmations and Layer 2
- Review carefully: mainnet relationship
- Verify afterward: cross-layer transfers
How to verify the outcome
From a risk perspective, mainnet relationship and cross-layer transfers deserve an independent review. Once a transaction is confirmed on-chain, a wallet normally cannot reverse it unilaterally. DApps and smart contracts can also introduce permission and contract risks, so every signature, approval and transfer should be understood before it is accepted.
For arrival confirmations, first define its role in the current task, then check whether Layer 2 and mainnet relationship are consistent. When cross-layer transfers is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For bridges, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: arrival confirmations
- Cross-check: Layer 2 and mainnet relationship
- Review carefully: cross-layer transfers
- Verify afterward: bridges
Practical checklist
- Never share your seed phrase, private key or verification code.
- Verify the address, network and amount before sending.
- Review each DApp signature and token approval independently.
- Use transaction hashes and block explorers to verify on-chain status.
- Revoke approvals and disconnect sessions that are no longer needed.