imtoken Knowledge Center
Assets & Transactions
Balances, token displays and transaction history reflect both on-chain state and local presentation, so display issues must be separated from on-chain facts.
Wallet boundaries and on-chain records
An account and an address are related but not identical concepts. The wallet manages keys and derives addresses, while the blockchain records balances and transaction state. In the context of Assets & Transactions, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
What to verify during an operation
When reviewing assets, check the network, token contract and transaction history together rather than treating a single interface display as definitive evidence. In the context of Assets & Transactions, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
Practical verification points
Interpreting asset displays and history
For both receiving and sending, network selection is a first-line check. Tokens with the same symbol may use different contracts and liquidity paths on different chains. In the context of Assets & Transactions, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result. If a token is missing from the interface, first verify the address balance and token contract on an explorer for the correct network, then check whether the wallet needs the token added manually. A transaction hash helps distinguish “not broadcast,” “pending,” and “confirmed but not refreshed” situations.
Building a repeatable wallet routine
An account and an address are related but not identical concepts. The wallet manages keys and derives addresses, while the blockchain records balances and transaction state. In the context of Assets & Transactions, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
- Verify the active network and destination before confirming.
- Treat seed phrases and private keys as secret credentials.
- Review DApp, signature and approval requests independently.