Wallet guides are organized around tasks rather than interface buttons: creation, backup, receiving, sending, transaction checks and asset-display troubleshooting each have their own prerequisites and safety checks.
Creating a wallet generates new control information, while importing uses existing recovery material to restore access. Neither flow should involve entering a seed phrase on an unfamiliar website.
Do not rely on a button label or a familiar-looking page as the reason to continue. Compare the request with the on-chain target, network state and expected result, and stop when those pieces do not line up.
Receiving is more than copying an address. Guides first identify the asset and network, then explain address checks and when to use a block explorer to verify arrival.
A common mistake is to treat a normal-looking interface as proof that the underlying blockchain action is correct. Public addresses, transaction hashes, contract addresses and network parameters provide independent ways to verify what is happening.
Sending guides put recipient, network, amount, gas and transaction hash into one workflow so one correct field is not mistaken for an entirely correct transaction.
A repeatable order of checks is more reliable than memory. Review source, network, account, target and expected outcome each time so the same safety logic carries across wallets and DApps.
When balances are missing, transactions are pending or DApps fail to connect, troubleshoot network context and on-chain state. Display problems never require sending a seed phrase or private key to anyone.
When a task involves a third-party contract, bridge, validator or web service, separate that external risk from the wallet itself. A wallet can display and sign a request, but it cannot guarantee the safety of outside code or services.
Seed phrases and private keys remain under the user’s control. Legitimate support should not ask for a seed phrase, private key or verification code. Review address, network and amount before transferring; blockchain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review spender and permission scope and consider revoking unused approvals.