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
Home / Wallet & Assets
imtoken

Wallet & Assets

A practical imtoken guide to multi-chain assets, addresses and networks, token contracts and transaction history, with clear checks for network, permissions and security.

Download imtoken

Core concepts

Confirm the active network and public address before interpreting balances or transaction history. In the context of multi-chain assets, it also helps to connect addresses and networks with token contracts rather than treating them as isolated features. Create or import the wallet first, then complete an offline backup and keep recovery material away from everyday online storage. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare multi-chain assets with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Practical workflow

Create or import the wallet first, then complete an offline backup and keep recovery material away from everyday online storage. In the context of addresses and networks, it also helps to connect token contracts with transaction history rather than treating them as isolated features. For DApps, treat connection, signing, approval and transfer as separate decisions instead of trusting everything after a session is connected. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare addresses and networks with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Capability

A practical imtoken guide to multi-chain assets, addresses and networks, token contracts and transaction history, with clear checks for network, permissions and security.

Workflow

Confirm the active network and public address before interpreting balances or transaction history. Create or import the wallet first, then complete an offline backup and keep recovery material away from everyday online storage.

Checks before confirmation

For DApps, treat connection, signing, approval and transfer as separate decisions instead of trusting everything after a session is connected. In the context of token contracts, it also helps to connect transaction history with multi-chain assets rather than treating them as isolated features. After submitting a transaction, use its hash on the matching network to verify the outcome instead of relying on one interface message. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare token contracts with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Review checklist

  • Confirm the active network and public address before interpreting balances or transaction history.
  • Create or import the wallet first, then complete an offline backup and keep recovery material away from everyday online storage.
  • For DApps, treat connection, signing, approval and transfer as separate decisions instead of trusting everything after a session is connected.
  • After submitting a transaction, use its hash on the matching network to verify the outcome instead of relying on one interface message.

Risks and follow-up

After submitting a transaction, use its hash on the matching network to verify the outcome instead of relying on one interface message. In the context of transaction history, it also helps to connect multi-chain assets with addresses and networks rather than treating them as isolated features. Confirm the active network and public address before interpreting balances or transaction history. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare transaction history with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Key risks

  • Never share a seed phrase, private key or verification code.
  • Third-party DApps, networks and contracts can fail or behave maliciously.
  • Staking and digital assets do not offer guaranteed returns or protection from price volatility.