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