Step-by-step Guide
Network Guides
A practical imtoken guide to network guides, including core concepts, verification steps and risk-aware usage.
Confirm the account, network and intended destination. Keep seed phrases and private keys offline and never provide them to another person.
- 01
Core concepts
adding networks rarely appears in isolation. It often intersects with identifying networks and gas. 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 adding networks, first define its role in the current task, then check whether identifying networks and gas are consistent. When confirmations is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For block explorers, 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: adding networks
- Cross-check: identifying networks and gas
- Review carefully: confirmations
- Verify afterward: block explorers
- 02
Checks before you act
When using imtoken for Network Guides, 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 identifying networks, first define its role in the current task, then check whether gas and confirmations are consistent. When block explorers is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For adding networks, 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: identifying networks
- Cross-check: gas and confirmations
- Review carefully: block explorers
- Verify afterward: adding networks
- 03
How to evaluate a live request
From a risk perspective, block explorers and adding networks 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 gas, first define its role in the current task, then check whether confirmations and block explorers are consistent. When adding networks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For identifying networks, 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: gas
- Cross-check: confirmations and block explorers
- Review carefully: adding networks
- Verify afterward: identifying networks
- 04
Risks and boundaries
After a Network Guides task is completed, review identifying networks and gas 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 confirmations, first define its role in the current task, then check whether block explorers and adding networks are consistent. When identifying networks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For gas, 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: confirmations
- Cross-check: block explorers and adding networks
- Review carefully: identifying networks
- Verify afterward: gas
- 05
How to verify the outcome
To understand Network Guides, treat block explorers and adding networks 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 block explorers, first define its role in the current task, then check whether adding networks and identifying networks are consistent. When gas is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For 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: block explorers
- Cross-check: adding networks and identifying networks
- Review carefully: gas
- Verify afterward: confirmations
Final checks
- 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.