Prepare before you start
Before using this send & receive assets guide, identify the account, network, asset, and exact outcome you want. Similar-looking addresses do not make two networks interchangeable, and a wallet interface cannot automatically correct a transfer that was sent on the wrong chain; in Send & Receive Assets, read this specifically alongside “Prepare before you start” and receiving addresses. A clear task definition makes every later check more meaningful; in Send & Receive Assets, read this specifically alongside “Prepare before you start” and receiving addresses. A durable routine for Send & Receive Assets is to make receiving addresses a first-pass check, use network matching as a second check, and rely on verifiable information related to transfer amounts rather than interface assumptions.
Understand receiving addresses and network matching
Start by understanding how receiving addresses and network matching affect the operation. Do not rely on a default network or an autofilled address for a high-value action; in Send & Receive Assets, read this specifically alongside “Understand receiving addresses and network matching” and network matching. Confirm the network, destination, token contract when relevant, and the account that will sign; in Send & Receive Assets, read this specifically alongside “Understand receiving addresses and network matching” and network matching. For a first-time workflow, a smaller test can help you understand the sequence, but the same checks are still required; in Send & Receive Assets, read this specifically alongside “Understand receiving addresses and network matching” and network matching. This part of Send & Receive Assets should be read together with the surrounding workflow: network matching affects how you interpret transfer amounts, while gas helps confirm the state after the action.
- Confirm the intended account and network.
- Verify the address, contract or DApp independently.
- Know what will change after the request is confirmed.
Work through transfer amounts and gas carefully
When you reach transfer amounts and gas, read what the wallet is actually asking you to approve. A DApp connection is not blanket consent for later signatures; in Send & Receive Assets, read this specifically alongside “Work through transfer amounts and gas carefully” and transfer amounts. If a contract, permission, amount, or destination differs from what you expected, cancel the step and restart from a trusted entry point instead of trying to “fix” an unclear request in place; in Send & Receive Assets, read this specifically alongside “Work through transfer amounts and gas carefully” and transfer amounts. For Send & Receive Assets, connect transfer amounts with gas and transaction hashes; the important part is the relationship between those concepts and the on-chain evidence you can verify afterward.
Verify the on-chain result
After submission, verify the result with the transaction hash rather than trusting only a success toast; in Send & Receive Assets, read this specifically alongside “Verify the on-chain result” and gas. The explorer should show the network, sender, recipient, fee, status, and confirmation progress; in Send & Receive Assets, read this specifically alongside “Verify the on-chain result” and gas. For steps involving transaction hashes, the process may include waiting periods or multiple stages, so the first wallet notification is not always the final on-chain state. When working through “Verify the on-chain result,” check the source, network, request details and resulting state in that order, with extra attention to gas and transaction hashes.
Troubleshooting common mistakes
Common mistakes include the wrong network, a copied address error, an incorrect token contract, insufficient gas, duplicate submissions, and confusing a connection request with a transaction; in Send & Receive Assets, read this specifically alongside “Troubleshooting common mistakes” and transaction hashes. Troubleshoot in a fixed order: network, address, transaction hash, contract, then current status; in Send & Receive Assets, read this specifically alongside “Troubleshooting common mistakes” and transaction hashes. If arrival confirmations looks unusual, first establish whether a transaction was actually broadcast. Do not treat an interface success message as the final answer for Send & Receive Assets. Use transaction hashes, arrival confirmations and receiving addresses to confirm that the expected change occurred on the intended network.
Good habits after the task is complete
Once the task is complete, disconnect DApps you no longer need and review approvals that may remain active; in Send & Receive Assets, read this specifically alongside “Good habits after the task is complete” and arrival confirmations. Keep seed phrases and private keys offline and never send them through screenshots, cloud notes, or support chats; in Send & Receive Assets, read this specifically alongside “Good habits after the task is complete” and arrival confirmations. Interfaces can change over time; a repeatable verification routine is more reliable than memorizing where a button used to be; in Send & Receive Assets, read this specifically alongside “Good habits after the task is complete” and arrival confirmations. If “Good habits after the task is complete” is unclear, stop before approving and return to the basics of arrival confirmations and receiving addresses, then verify the result with a transaction hash, contract address or block record where applicable.
Security and risk reminder
Seed phrases and private keys are controlled by the user. imtoken will never ask for them. Blockchain transactions are generally irreversible by a wallet provider, and third-party DApps, smart contracts, network conditions and digital-asset prices can introduce additional risk.