StepsReceiving assetsSending assetsGas & confirmationTroubleshooting
  1. 01

    Receiving assets

    Receiving assets is a practical part of understanding Send & Receive. Build a repeatable transfer checklist around addresses, networks, amounts, gas and transaction hashes. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    Receiving assets within Send & Receive is not an isolated feature. In practice it is shaped by network state, account permissions, transaction parameters and user decisions. Understanding those relationships first makes similar-looking screens and labels much less confusing.

    For Receiving assets, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with receiving assets
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  2. 02

    Sending assets

    Sending assets is a practical part of understanding Send & Receive. Build a repeatable transfer checklist around addresses, networks, amounts, gas and transaction hashes. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    A useful way to think about Sending assets within Send & Receive is to separate what the interface displays from what the blockchain records. The wallet organizes information and submits requests, while the target network records the resulting state. Addresses, networks, contracts and transaction hashes are therefore important verification points.

    For Sending assets, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with sending assets
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  3. 03

    Gas & confirmation

    Gas & confirmation is a practical part of understanding Send & Receive. Build a repeatable transfer checklist around addresses, networks, amounts, gas and transaction hashes. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    The risky part of Gas & confirmation within Send & Receive is often the surrounding context rather than the button itself: which network is active, which site initiated the request, what permission is being granted, and whether the amount and fee make sense. Turning those checks into a routine is more reliable than reacting to prompts one by one.

    For Gas & confirmation, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with gas & confirmation
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone
  4. 04

    Troubleshooting

    Troubleshooting is a practical part of understanding Send & Receive. Build a repeatable transfer checklist around addresses, networks, amounts, gas and transaction hashes. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.

    imtoken guidance focuses on information you can verify. When something is unclear, do not rely on a single line in a pop-up. Check the address, network, contract, transaction history and explorer data where relevant, then decide whether the action matches your intent.

    For Troubleshooting, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.

    Practical checks

    • Verify the network and account before working with troubleshooting
    • Double-check important addresses, contracts, amounts or permissions
    • Never send a seed phrase, private key or verification code to anyone

Related reading

Getting StartedNetwork GuidesSecurity