Assets & Transactions

Wallet balances are a presentation of on-chain state

Start by making the real object of “Wallet balances are a presentation of on-chain state” explicit. An asset screen reads network data and token metadata to present balances. This is not just vocabulary: it tells you where the displayed data comes from, what the next confirmation can change and which facts should be checked on the relevant network. For Assets & Transactions, a familiar name, icon or interface is not enough by itself; network, account and intended action belong in the same decision.

What to verify in practice

A common mistake in this area is treating a plausible screen as complete evidence. An asset screen reads network data and token metadata to present balances. Node, indexing or metadata issues can affect what is displayed, so verify the address on the relevant explorer when the real state matters. If a request unexpectedly asks for broader permission, a network switch, recovery material or an unexplained signature, stop and verify the source. Declining an action you cannot explain is safer than guessing what a contract or signature might do.

For this part of Assets & Transactions, keep one boundary in mind: Separate what a wallet interface displays from what the blockchain actually records. Interface familiarity is not a substitute for on-chain facts. Decisions around “Wallet balances are a presentation of on-chain state” should be based on the current network, account and request rather than assuming a previous successful action makes the next one trustworthy. On-chain transactions generally cannot be unilaterally reversed by a wallet, and third-party DApps, smart contracts or bridges can introduce separate risks.

A custom token begins with its contract address

For Assets & Transactions, a practical review can be split into target, network and result. Tokens with the same name can exist on multiple networks, and imitations can use familiar symbols. Confirm both network and contract address from a trusted source rather than relying on a name or icon. Then use public on-chain evidence where appropriate: Keep a transaction hash or another public reference for verification. This order reduces the chance that interface familiarity will hide an important detail and makes troubleshooting easier when something looks wrong.

A durable routine does not need to be complicated. For “A custom token begins with its contract address”, define the expected action, perform only what is necessary, and verify the result afterward. Tokens with the same name can exist on multiple networks, and imitations can use familiar symbols. Public references such as a transaction hash, network name or address can help with troubleshooting, while a seed phrase, private key or verification code should stay out of webpages, support tickets and chats.

For this part of Assets & Transactions, keep one boundary in mind: Separate what a wallet interface displays from what the blockchain actually records. Interface familiarity is not a substitute for on-chain facts. Decisions around “A custom token begins with its contract address” should be based on the current network, account and request rather than assuming a previous successful action makes the next one trustworthy. On-chain transactions generally cannot be unilaterally reversed by a wallet, and third-party DApps, smart contracts or bridges can introduce separate risks.

Transaction history includes more than transfers

A common mistake in this area is treating a plausible screen as complete evidence. Native transfers, token movements, approvals, swaps and NFT actions create different records. A transaction hash can reveal the contract call and events, while a short wallet summary may not show every permission change. If a request unexpectedly asks for broader permission, a network switch, recovery material or an unexplained signature, stop and verify the source. Declining an action you cannot explain is safer than guessing what a contract or signature might do.

Risk signals worth noticing

Start by making the real object of “Transaction history includes more than transfers” explicit. Native transfers, token movements, approvals, swaps and NFT actions create different records. This is not just vocabulary: it tells you where the displayed data comes from, what the next confirmation can change and which facts should be checked on the relevant network. For Assets & Transactions, a familiar name, icon or interface is not enough by itself; network, account and intended action belong in the same decision.

For this part of Assets & Transactions, keep one boundary in mind: Separate what a wallet interface displays from what the blockchain actually records. Interface familiarity is not a substitute for on-chain facts. Decisions around “Transaction history includes more than transfers” should be based on the current network, account and request rather than assuming a previous successful action makes the next one trustworthy. On-chain transactions generally cannot be unilaterally reversed by a wallet, and third-party DApps, smart contracts or bridges can introduce separate risks.

Build an asset-review routine

A durable routine does not need to be complicated. For “Build an asset-review routine”, define the expected action, perform only what is necessary, and verify the result afterward. Keep track of the networks and addresses you actually use and the approvals you still need. Public references such as a transaction hash, network name or address can help with troubleshooting, while a seed phrase, private key or verification code should stay out of webpages, support tickets and chats.

For Assets & Transactions, a practical review can be split into target, network and result. Keep track of the networks and addresses you actually use and the approvals you still need. Do not rush to interact with unfamiliar tokens or links attached to them. Then use public on-chain evidence where appropriate: Verify on-chain facts first, then decide whether any action is necessary. This order reduces the chance that interface familiarity will hide an important detail and makes troubleshooting easier when something looks wrong.

For this part of Assets & Transactions, keep one boundary in mind: Separate what a wallet interface displays from what the blockchain actually records. Interface familiarity is not a substitute for on-chain facts. Decisions around “Build an asset-review routine” should be based on the current network, account and request rather than assuming a previous successful action makes the next one trustworthy. On-chain transactions generally cannot be unilaterally reversed by a wallet, and third-party DApps, smart contracts or bridges can introduce separate risks.