The Academy follows the order in which people actually learn: wallets and keys first, then addresses, networks and gas, followed by transfers, transaction review, DApps, approvals and security.
Understand seed phrases, private keys and addresses before creating or importing a wallet. Knowing what must never be handed to another person matters more than memorizing interface buttons.
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, sending, balance checks, transaction lookup and DApp use all depend on network context. Making the network a standard check reduces multi-chain confusion.
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.
After an action, use the transaction hash to inspect public status, blocks and events. This builds an understanding of the difference between wallet interfaces and on-chain facts.
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.
Once basic transactions are understood, connections, signatures and approvals become easier to evaluate. The core Web3 habit is knowing exactly what each approval means.
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.