Assets & Transactions

Start with accounts, networks, and asset state

Understand token display, contract addresses, balance changes, and on-chain records. A wallet interface can present information from several networks, but it does not hold on-chain balances inside the page itself. Control comes from the ability to create valid signatures with the relevant keys. That model makes network, account, and token-contract checks more important than a familiar icon.

Similar address formats can appear across compatible networks while the balances remain completely separate. When receiving, sending, or adding a token, review the network and address together. For same-name assets, verify the contract through a trusted source instead of relying on the label.

Turn transfers into a reviewable sequence

For “Assets & Transactions”, verify the active network first, then the destination address, asset, amount, and any memo or tag requirement. Review gas or network fees before signing so the cost is understood separately from the transfer amount.

After broadcast, keep the transaction hash and use the appropriate explorer to distinguish pending, successful, and failed states. If a balance does not match expectations, inspect the network, token contract, confirmations, and transaction result before resubmitting the same intent.

Build a repeatable operating routine

A stable routine reduces mistakes that come from familiarity: re-check the network after switching, compare the beginning and end of a pasted address, review the fee, read the signature, and confirm the final on-chain result.

DApp connections introduce a separate layer of permissions. A successful connection does not make later requests safe by default. Disconnect sessions you no longer need, review persistent approvals, and stop when a contract or permission cannot be explained.

• Check the active network
• Verify address, contract, or approval target
• Review amount, fees, and request details
• Keep the transaction hash when relevant
• Reject requests you cannot explain

Keep security boundaries explicit

Your seed phrase and private key should stay under your control. imtoken staff will not ask for them or ask you to send a verification code. Normal wallet connections and DApp interactions do not require typing recovery secrets into a website.

On-chain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts can also carry risk, so the most effective control point is before signing: verify the address, network, amount, contract, and approval target.