Types of Wallets: Self-Custody vs. Managed
Before you can touch any DeFi protocol, you need to understand the tool that makes it all possible: your wallet. A crypto wallet doesn't actually "store" your coins the way a physical wallet stores cash — instead, it stores the private keys that prove you own a given address on the blockchain and lets you sign transactions with those keys. The critical distinction for this entire course is between self-custody wallets, where you personally hold the private keys, and custodial (or managed) wallets, where a third party — typically an exchange or an app — holds the keys on your behalf.
Software wallets like MetaMask, and hardware wallets like Ledger or Trezor, are self-custody: when you create one, you generate a seed phrase (covered in depth in the next lesson) that only you possess, and the wallet software simply helps you use those keys to sign transactions. No company can freeze this wallet, reverse a transaction from it, or recover it for you if you lose access — the control is entirely yours, for better and for worse. Custodial wallets, by contrast, are what you're using when you hold crypto on an exchange like Coinbase without withdrawing it: the exchange's systems hold the actual private keys, and your balance is really just an entry in their internal database that they promise to honor.
This distinction is not a minor technical detail — it's the single most important fact for understanding DeFi, because DeFi protocols require self-custody. A smart contract has no way to "log you in" with a username and password; it can only interact with a wallet address that can cryptographically sign a transaction proving ownership. This is why step one of every DeFi interaction, from swapping tokens to depositing into a lending pool, is "connect wallet" — and why that wallet must be a self-custody one you control directly, not a custodial exchange balance.
Within self-custody wallets, there's a further split worth knowing: hot wallets (software running on an internet-connected device, like a browser extension or phone app) are convenient for frequent, smaller DeFi interactions but are exposed to malware and phishing on that device; cold wallets (hardware devices that keep your private key offline and only sign transactions when physically connected and confirmed) are far more resistant to remote attacks but less convenient for frequent use. Many experienced DeFi users run both: a hot wallet for everyday, smaller-value activity, and a cold wallet for long-term holdings or any single transaction large enough that the extra friction of plugging in a hardware device is worth the security it buys.
Worked Example
Think of a custodial exchange wallet like cash kept in someone else's safe. It's convenient — if you want it moved, you just ask, and if you forget the combination, there's a manager who can help you recover access through an identity-verification process. But you need their permission and systems to be functioning before you can act: if the business temporarily halts withdrawals, freezes an account due to a compliance flag, or becomes insolvent, your access is at their mercy, regardless of what you personally did.
A self-custody wallet, by contrast, is like holding that same cash yourself, in a safe only you have the combination to. No one can tell you no, freeze it, or require you to prove your identity to move it. But there is also no manager to call: if you lose the combination (your seed phrase) or give it to the wrong person, there's no recovery process, no customer service line, and no reversal. This is precisely the custody trade-off discussed in the "DeFi vs. CEX" lesson, now applied specifically to the wallet layer that makes every other DeFi interaction possible.
Extending the hot-versus-cold distinction: imagine a user who keeps $200 in a browser-extension hot wallet for weekly small swaps and experimentation, and a separate hardware wallet holding the bulk of their savings, used only a few times a year to move funds in or out of DeFi positions. If the browser wallet's device is ever compromised by malware, the attacker's potential take is capped at roughly $200 — an acceptable, bounded loss the user consciously accepted in exchange for convenience — while the much larger cold-wallet balance was never exposed to that device at all.
Exercise
List every wallet you currently use — this might include an exchange app like Coinbase or Kraken, a browser extension like MetaMask, a mobile wallet app, or a hardware device like a Ledger. For each one, mark it clearly as either "custodial" (a company holds the keys) or "self-custody" (you hold the keys, typically evidenced by the fact that you — and only you — have a seed phrase for it), and if self-custody, further mark it "hot" or "cold."
Once your list is complete, confirm whether you have at least one self-custody software wallet installed on a device you trust and feel comfortable using. If you don't yet, note that as an action item — the next two lessons in this module ("Private Keys, Seeds and Backups" and "Setting Up Your First Wallet Safely") will walk you through generating one correctly. Also write one sentence on how you'd split value between a hot wallet and a cold wallet once you're active in DeFi, given your own expected transaction frequency and the amounts involved. Every DEX, lending protocol, and liquidity pool in the rest of this course assumes you have a working self-custody wallet connected, so getting this step right now will make every subsequent module go smoothly.
Recap
- Self-custody wallets (you hold the keys) are required for DeFi; custodial wallets (an exchange holds the keys) cannot directly interact with smart contracts.
- Self-custody trades the convenience and recoverability of a custodian for full, unassisted control over your own funds.
- Within self-custody, hot wallets suit frequent smaller activity and cold wallets suit larger or longer-term holdings — confirming you have a working setup now sets you up for every remaining lesson in this course.