Step-by-step Guide
Web3 Guides
A practical imtoken guide to web3 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
To understand Web3 Guides, treat connect to DApps and check domains 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 connect to DApps, first define its role in the current task, then check whether check domains and signatures are consistent. When approvals is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For disconnect, 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: connect to DApps
- Cross-check: check domains and signatures
- Review carefully: approvals
- Verify afterward: disconnect
- 02
Checks before you act
check domains rarely appears in isolation. It often intersects with signatures and approvals. 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 check domains, first define its role in the current task, then check whether signatures and approvals are consistent. When disconnect is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For connect to DApps, 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: check domains
- Cross-check: signatures and approvals
- Review carefully: disconnect
- Verify afterward: connect to DApps
- 03
How to evaluate a live request
When using imtoken for Web3 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 signatures, first define its role in the current task, then check whether approvals and disconnect are consistent. When connect to DApps is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For check domains, 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: signatures
- Cross-check: approvals and disconnect
- Review carefully: connect to DApps
- Verify afterward: check domains
- 04
Risks and boundaries
From a risk perspective, connect to DApps and check domains 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 approvals, first define its role in the current task, then check whether disconnect and connect to DApps are consistent. When check domains is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For signatures, 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: approvals
- Cross-check: disconnect and connect to DApps
- Review carefully: check domains
- Verify afterward: signatures
- 05
How to verify the outcome
After a Web3 Guides task is completed, review signatures and approvals 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 disconnect, first define its role in the current task, then check whether connect to DApps and check domains are consistent. When signatures is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For approvals, 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: disconnect
- Cross-check: connect to DApps and check domains
- Review carefully: signatures
- Verify afterward: approvals
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.