imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken
中文Download
Home / Wallet & Assets
Product guide

Wallet & Assets

When working with Wallet & Assets, the safest assumption is that every network, contract, and request deserves its own context check. Assets live on specific networks. Addresses identify accounts and receive assets. Native coins and contract tokens have different origins. The guidance below turns that principle into concrete review steps and shows how to verify results without relying on screenshots, labels, or repeated submissions.

Download imtoken

assets live on specific networks

addresses identify accounts and receive assets

native coins and contract tokens have different origins
the destination network matters before receivinggas follows the rules of the active networkbalances must be read in network context
On this pageCore capability: Assets live on specific networksReal-world use: Native coins and contract tokens have different originsVerify on-chain results: Sending creates an on-chain transactionWeb3 and permission boundaries: A transaction hash tracks submitted activityOngoing management: Token contract addresses help identify assets

Core capability: Assets live on specific networks

Focus on addresses identify accounts and receive assets

First, in Wallet & Assets, Core capability: Assets live on specific networks describes a relationship between wallet controls and blockchain state. Assets live on specific networks. Addresses identify accounts and receive assets. While using Wallet & Assets, it helps to record the state before and after the action, especially when one account is visible across several networks or DApps. The fact that an item appears in an interface does not by itself prove that a transfer, approval, or contract interaction has completed. Account, network, asset identity, and request type should remain separate checks.

First follow-up in Wallet & Assets: Focus on addresses identify accounts and receive assets is useful because it turns one action into a before-and-after state that can be reviewed. Native coins and contract tokens have different origins. The destination network matters before receiving. Confirm the active account and network in the product before submission, then use a transaction hash, block status, or contract record to verify the result when appropriate. Try to manage long-lived permissions separately from one-time transactions. The product can organize information and requests, but it does not replace protocol rules, contract logic, or the user’s responsibility to review each signature and approval on its own terms.

  • Confirm assets live on specific networks.
  • Check how addresses identify accounts and receive assets affects the current request.
  • Use native coins and contract tokens have different origins as a separate verification point.

Real-world use: Native coins and contract tokens have different origins

Focus on the destination network matters before receiving

Second, in Wallet & Assets, Real-world use: Native coins and contract tokens have different origins describes a relationship between wallet controls and blockchain state. Native coins and contract tokens have different origins. The destination network matters before receiving. While using Wallet & Assets, it helps to treat network context as a prerequisite for every step, especially when one account is visible across several networks or DApps. The fact that an item appears in an interface does not by itself prove that a transfer, approval, or contract interaction has completed. Account, network, asset identity, and request type should remain separate checks.

Second follow-up in Wallet & Assets: Focus on the destination network matters before receiving is useful because it turns one action into a before-and-after state that can be reviewed. Sending creates an on-chain transaction. Gas follows the rules of the active network. Confirm the active account and network in the product before submission, then use a transaction hash, block status, or contract record to verify the result when appropriate. Try to be especially careful with assumptions that arise from similar-looking networks. The product can organize information and requests, but it does not replace protocol rules, contract logic, or the user’s responsibility to review each signature and approval on its own terms.

  • Confirm native coins and contract tokens have different origins.
  • Check how the destination network matters before receiving affects the current request.
  • Use sending creates an on-chain transaction as a separate verification point.

Verify on-chain results: Sending creates an on-chain transaction

Focus on gas follows the rules of the active network

Third, in Wallet & Assets, Verify on-chain results: Sending creates an on-chain transaction describes a relationship between wallet controls and blockchain state. Sending creates an on-chain transaction. Gas follows the rules of the active network. While using Wallet & Assets, it helps to avoid repeated submissions when the current state is unclear, especially when one account is visible across several networks or DApps. The fact that an item appears in an interface does not by itself prove that a transfer, approval, or contract interaction has completed. Account, network, asset identity, and request type should remain separate checks.

Third follow-up in Wallet & Assets: Focus on gas follows the rules of the active network is useful because it turns one action into a before-and-after state that can be reviewed. A transaction hash tracks submitted activity. Balances must be read in network context. Confirm the active account and network in the product before submission, then use a transaction hash, block status, or contract record to verify the result when appropriate. Try to distinguish a waiting state from a failed state. The product can organize information and requests, but it does not replace protocol rules, contract logic, or the user’s responsibility to review each signature and approval on its own terms.

  • Confirm sending creates an on-chain transaction.
  • Check how gas follows the rules of the active network affects the current request.
  • Use a transaction hash tracks submitted activity as a separate verification point.

Web3 and permission boundaries: A transaction hash tracks submitted activity

Focus on balances must be read in network context

Fourth, in Wallet & Assets, Web3 and permission boundaries: A transaction hash tracks submitted activity describes a relationship between wallet controls and blockchain state. A transaction hash tracks submitted activity. Balances must be read in network context. While using Wallet & Assets, it helps to keep secret recovery material separate from troubleshooting data, especially when one account is visible across several networks or DApps. The fact that an item appears in an interface does not by itself prove that a transfer, approval, or contract interaction has completed. Account, network, asset identity, and request type should remain separate checks.

Fourth follow-up in Wallet & Assets: Focus on balances must be read in network context is useful because it turns one action into a before-and-after state that can be reviewed. Token contract addresses help identify assets. Approvals and transfers are different on-chain actions. Confirm the active account and network in the product before submission, then use a transaction hash, block status, or contract record to verify the result when appropriate. Try to perform an independent review after submission. The product can organize information and requests, but it does not replace protocol rules, contract logic, or the user’s responsibility to review each signature and approval on its own terms.

  • Confirm a transaction hash tracks submitted activity.
  • Check how balances must be read in network context affects the current request.
  • Use token contract addresses help identify assets as a separate verification point.

Ongoing management: Token contract addresses help identify assets

Focus on approvals and transfers are different on-chain actions

Fifth, in Wallet & Assets, Ongoing management: Token contract addresses help identify assets describes a relationship between wallet controls and blockchain state. Token contract addresses help identify assets. Approvals and transfers are different on-chain actions. While using Wallet & Assets, it helps to ask what every signature proves or changes, especially when one account is visible across several networks or DApps. The fact that an item appears in an interface does not by itself prove that a transfer, approval, or contract interaction has completed. Account, network, asset identity, and request type should remain separate checks.

Fifth follow-up in Wallet & Assets: Focus on approvals and transfers are different on-chain actions is useful because it turns one action into a before-and-after state that can be reviewed. Assets live on specific networks. Addresses identify accounts and receive assets. Confirm the active account and network in the product before submission, then use a transaction hash, block status, or contract record to verify the result when appropriate. Try to separate interface cues from verifiable chain state. The product can organize information and requests, but it does not replace protocol rules, contract logic, or the user’s responsibility to review each signature and approval on its own terms.

  • Confirm token contract addresses help identify assets.
  • Check how approvals and transfers are different on-chain actions affects the current request.
  • Use assets live on specific networks as a separate verification point.

Practical checklist

  • Review assets live on specific networks.
  • Review native coins and contract tokens have different origins.
  • Review sending creates an on-chain transaction.
  • Review a transaction hash tracks submitted activity.
  • Review token contract addresses help identify assets.

Continue learning

Create & Backup Send & Receive Assets & Transactions