Balance sources
Balance sources is a distinct part of understanding Assets & Transactions. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for balance sources: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
Similar address formats do not make networks interoperable. Before transferring, re-check the network, amount, gas and destination. For important actions, keep a public address or transaction hash and verify the on-chain result with a block explorer. Stop when interface data conflicts with chain data.
Practical checks
- Confirm the active network and account for balance sources
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain
Token contracts
Token contracts is a distinct part of understanding Assets & Transactions. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for token contracts: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
After connecting to a DApp, inspect every signature, transaction and token approval independently; disconnecting does not necessarily revoke an on-chain allowance. Similar address formats do not make networks interoperable. Before transferring, re-check the network, amount, gas and destination.
Practical checks
- Confirm the active network and account for token contracts
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain
Activity history
Activity history is a distinct part of understanding Assets & Transactions. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for activity history: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
Security is a continuing routine: offline backups, trusted devices, fewer unnecessary approvals, caution on public networks and skepticism toward unexpected requests. After connecting to a DApp, inspect every signature, transaction and token approval independently; disconnecting does not necessarily revoke an on-chain allowance.
Practical checks
- Confirm the active network and account for activity history
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain
Display issues
Display issues is a distinct part of understanding Assets & Transactions. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for display issues: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
Review the active network, account and target together rather than relying on a page label or icon. Security is a continuing routine: offline backups, trusted devices, fewer unnecessary approvals, caution on public networks and skepticism toward unexpected requests.
Practical checks
- Confirm the active network and account for display issues
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain