OpSec: Operational Security

:::section{mins=3} What Is OpSec :::

:::lead You set up a Ledger, wrote the seed on paper, and put it in a drawer. A month later: a phishing site, an "approve all" signature, and the Ledger didn't save you — because you pressed "confirm" yourself. OpSec isn't a device. It's the everyday habits that decide whether your assets survive the week. :::

:::p OpSec (operational security) isn't a set of devices — it's a way of operating: the everyday habits that ultimately decide whether your assets stay yours. A hardware wallet, a password manager, a separate browser are tools, but a tool doesn't make the decision for you. In the opening scenario the Ledger did exactly its job: it showed the transaction and waited. A person pressed "confirm." That's why almost every large loss is not a "hardware hack" but a chain of small, ordinary choices — one password reused everywhere, a link from a DM, a signature given without looking. OpSec is the discipline of that chain: it closes not a single hole but the habit of leaving holes open. :::

:::p The cost of a mistake is higher here than almost anywhere else, because there's no safety net. Traditional finance lets you undo things: a bank can reverse a payment, refund fraud, demand ID at login, freeze an account as a last resort. Crypto has none of that by design — a transfer is final, no one reimburses you, and a seed phrase grants full access with no identity check at all. A hacker who gets your seed becomes you: instantly and permanently. That irreversibility is precisely why the habit matters more than the hardware — you can't repair the damage, only avoid it. :::

:::p Threats sort into three levels, each with its own logic of defense: :::

:::howto{label="Three levels of threats"}

• Mass attacks — phishing and malware — aren't aimed at you personally: they sweep up whoever bites, and basic measures stop them — a hardware wallet, transaction simulation in Rabby, plain common sense → Wallets.
• Targeted attacks begin where someone already knows you hold crypto, and this is where OpSec and privacy do the real work: the less the world knows about your holdings, the fewer reasons to pick you.
• Physical threats (coercion, the so-called "wrench attack") are reduced first by that same low profile; technical measures like a passphrase wallet with a decoy balance, or keys split across people and places, only limit what can be taken on the spot. Under direct coercion, one rule governs everything: your life is worth more than the funds (detailed in §4). :::

:::callout Think of preparing for a scuba dive. Before every descent, a diver runs through a checklist: tank pressure, regulator, buoyancy vest, buddy present and briefed on the plan. Nobody jumps in "hoping for the best," even if they've dived the same reef twenty times, because a mistake at depth can cost a life, and "rescue services" won't arrive quickly. Crypto works the same way: you operate in an environment where errors are irreversible and help isn't coming. OpSec isn't a one-time Ledger purchase. It's the habit of checking your gear before every dive, every day, no exceptions. :::

:::keypoints{label="Key Points"}

• The device is the last line of defense, not the first: in almost every major loss the owner authorized the transaction themselves. OpSec starts to decay the moment it's treated as a one-time setup rather than a daily habit
• A seed phrase has no place in a password manager or any cloud: the 2022 LastPass breach kept draining vaults for years afterward, because stolen vaults are cracked offline at the attacker's leisure (full breakdown below)
• html: Visibility is risk: the less the world knows about your holdings, the lower the odds of both a targeted hack and a physical attack — and physical attacks on holders rose sharply through 2025 → Scams
• The basic stack costs about $80 (a hardware wallet) and covers the vast majority of mass attacks — phishing, malware, clipboard hijacking; everything beyond it should answer a specific threat from your own model, not be bought by default :::

:::details{badge=Advanced title="Anatomy of a Real Incident: LastPass → $150 Million"} In August 2022 attackers penetrated LastPass's development environment, then compromised a senior DevOps engineer's personal computer to access encrypted user vaults. The vaults were cracked offline. The master password (the single password that unlocks your password manager and also encrypts the entire vault) was chosen by users themselves, and for many it was weak. Inside: seed phrases, private keys, exchange credentials.

Scale: the largest known theft is $150 million in XRP from Ripple co-founder Chris Larsen (January 30, 2024); the FBI later seized $24 million. TRM Labs (December 2025) traced roughly $35 million laundered through mixers and stresses this is only a fraction of the total: vaults with weak master passwords were still being cracked through late 2025.

:::p{html} Lessons:

• A seed phrase must never be stored in a password manager, even an encrypted one: if the service is compromised, everything is exposed
• The master password is the last line of defense; if it's weak, vault encryption is meaningless
• The incident unfolded over three years (2022–2025): offline decryption doesn't happen instantly, but it eventually reaches every vault

:::further{label="Further Reading"}

• LastPass Breach Report | TRM Labs
• $150M Cyberheist | Krebs on Security
• EFF Threat Modeling | ssd.eff.org :::

:::quiz{id=q-4-4-s1 label="Check yourself" correct=1 explanation="Most thefts aren't device hacks but social engineering and “approve all” signatures: your own finger taps confirm. Behavior, not a purchase, is the foundation."} Why doesn't a hardware wallet alone protect you from most losses?

• The seed is copied to the maker's cloud during setup, so a breach there exposes the key
• A device can't help if you sign a malicious transaction or reveal your seed yourself
• Hardware wallets are vulnerable to remote key interception over Bluetooth
• Without firmware updates, the keys can be extracted just by plugging the device into a PC :::

:::section{mins=4} Threat Modeling :::

:::lead You hold $500 in crypto — do you really need a dedicated laptop and a Shamir backup? No. And at $500,000? A basic Ledger no longer cuts it. Threat modeling is how you decide who and what you're defending against, before spending a cent on protection. :::

:::p Threat modeling sounds formal, but it comes down to four honest questions — and the answers, taken together, point straight at the level of protection that fits you. :::

:::p{html} What am I protecting? Start with the amount, because it sets the stakes. A hundred dollars justifies only basic hygiene; around ten thousand calls for the medium level; six figures and up demand the maximum setup. The number isn't a status here — it's a budget for how much inconvenience the funds are worth. :::

:::p{html} Who am I protecting against? Mass phishing catches everyone indiscriminately and makes up the bulk of all attacks. A targeted attacker is different: they already know you hold crypto and will spend effort on you specifically. Beyond that sit physical threats — someone willing to show up in person — and, more rarely, a state-level adversary with resources no individual can match. :::

:::p{html} Which attack vectors apply? In practice they are phishing and malware, SIM-swap, social engineering, physical access to your devices, and supply-chain compromise. Each one is closed by its own measure, so naming them is exactly what turns a vague sense of danger into a concrete checklist. :::

:::p{html} What am I willing to spend? Protection costs time, money, and convenience, and every measure has a price. A YubiKey is fifty dollars but adds a step to every login; a dedicated laptop is five hundred and up, plus the friction of keeping it apart from everything else. The right level is the one whose cost is smaller than what it protects. :::

:::callout Threat modeling works like building codes. A garden shed needs four posts and a roof – no one demands a foundation or structural calculations. A residential house requires load-bearing walls, up-to-code wiring, and a fire alarm. A skyscraper needs a steel frame, seismic resistance, backup generators, and a team of engineers. Building a shed like a skyscraper is a waste of money. Building a skyscraper like a shed is criminal negligence. Your threat model is your "building code": it determines what level of protection is adequate for what you're protecting. :::

:::keypoints{label="Key Points"}

• html: In 2024 the FBI recorded $26 million in SIM-swap losses in the US, while in the UK incidents surged 1,055% over the year (from 289 to roughly 3,000 cases). In Australia, 90% of victims took no action that triggered the swap – it happened entirely without them → Scams
• Supply-chain attacks (compromising a software or hardware vendor upstream) are rare but catastrophic: LastPass 2022 → $150 million largest theft (Larsen); compromised Ledger Connect Kit (December 2023) → $600K drained in two hours
• Reassess your threat model every time the portfolio doubles: protection adequate for $5K becomes negligence at $50K
• Four questions – "what am I protecting / from whom / which vectors / how much am I willing to spend" – narrow hundreds of recommendations down to a handful of concrete steps :::

:::details{badge=Advanced title="Crypto Threat Matrix"} :::p{html} This matrix gathers the main threats into one view – how likely each is, what it costs you, and what closes it. Read it top to bottom: the most common attacks sit at the top and everyone must cover them; the rare but severe ones are at the bottom and matter once your portfolio grows. The "Defense" column is essentially your priority list.

:::details{badge=Advanced title="Advanced Threat Modeling: Attacks Through Your Environment"} :::p{html} Close-contacts attack. In January 2025, Ledger co-founder David Balland was kidnapped along with his wife – attackers knew about his role at the company. In 2025 France recorded more wrench attacks than any other country – 19 confirmed cases – with Europe accounting for about 40% of all incidents worldwide (CertiK). Defense: don't discuss amounts, even with family – only the minimum needed for an estate plan (§7). :::

:::p{html} Public-information attack. A Twitter post saying "bought 10 ETH" makes you a target. An ENS domain like vitalik.eth publishes your balance to the world. In November 2025, a San Francisco resident was robbed of $13 million: an attacker posing as a delivery courier forced his way in, bound the victim, and coerced wallet access under threat of violence – he was targeted because his crypto wealth was known. Defense: never link your identity to addresses; never post NFTs from your primary wallet. :::

:::p{html} Infrastructure (supply-chain) attack. In December 2023, attackers injected malicious code into Ledger Connect Kit – a JavaScript library used by dozens of DeFi frontends. Within two hours roughly $600K was stolen: users connected to legitimate sites, but signatures were redirected to the attacker's address. Defense: a hardware wallet displays the recipient address on its own screen – if it doesn't match what you expect, reject the transaction → Wallets. Only update firmware from the manufacturer's official site. ::: :::

:::further{label="Further Reading"}

• CertiK Skynet Wrench Attacks Report | certik.com
• EFF Threat Modeling Guide | ssd.eff.org :::

:::quiz{id=q-4-4-s2 label="Check yourself" correct=2 explanation="Defenses for $500 and for $500,000 differ: too much wastes resources, too little loses funds. Revisit your threat model every time the portfolio doubles."} What should determine your level of protection?

• The level most people recommend in crypto chats and guides
• The maximum protection available: better safe than sorry
• The size and value of what you're protecting, adjusted as it grows
• The reputation and price of the brands you use :::

:::section{mins=3} OpSec Levels :::

:::lead You've defined your threat model – now you need a concrete plan. OpSec splits into three levels, each building on the one before. Pick yours by the amount you're protecting, and finish the checklist: a half-done checklist protects less than it looks. :::

:::p The three levels aren't three independent options to choose between: each one contains the level below it, so you climb the ladder rather than pick a rung. The table below is a map — amount and who you are on the left, what to actually do on the right. Find your row and work the checklist top to bottom, skipping nothing. :::

:::p{html}

:::p The basic level is self-explanatory from the table above, and the maximum level is laid out in full below, under "Maximum Level Checklist." So the one worth walking through is the medium level: the step-up most people actually have to make once the amounts get serious. You set up a dedicated browser profile for crypto with no third-party extensions, because any extension can read the pages you open and tamper with a transaction. You move two-factor auth off SMS and onto a hardware key (YubiKey): SMS can be hijacked through a SIM-swap, a key cannot. You create a separate email for crypto (ProtonMail, say) so a breach of your main inbox doesn't drag your exchange accounts down with it. When using DeFi you turn on a VPN, revoke stale approvals regularly, and set up address monitoring (DeBank) so you catch fund movements immediately rather than after the fact. :::

:::callout Think of progressive training in a gym. A beginner doesn't load a max-weight barbell on day one — they drill the movement, build a base, and add weight only as the body adapts. Skip those stages and you don't get stronger faster; you get injured. A coach sets the load to your current capacity, not to the heaviest plate in the room. OpSec levels work the same way: the basic level is your form and your base, the medium and maximum levels are added load. Piling on advanced gear before the basics hold isn't strength — it's the security equivalent of a torn muscle. :::

:::keypoints{label="Key Points"}

• Cost per level: basic is roughly $80 (Ledger), medium is roughly $180 (add two YubiKeys + metal backup), maximum is roughly $700 (add dedicated laptop + Keystone) – compare against the amount you're protecting
• html: The most common mistake is skipping levels: a user with a Shamir backup but no exchange 2FA is less protected than someone who completed the basic checklist in full → Wallets
• The medium level closes two critical vectors that basic misses: SIM-swap (YubiKey instead of SMS) and search-engine phishing (dedicated browser with bookmarks only)
• Every checklist item traces back to a real incident: "separate email" → LastPass victims used their primary inbox; "don't discuss amounts" → 72 wrench attacks in 2025 began with information leaks :::

:::details{badge=Advanced title="Medium Level Checklist"} The medium level only counts as done when every box is checked – skipping any one leaves a vector open:

:::p{html}

• Hardware wallet for all significant amounts
• Seed phrase on paper/metal, in a safe. NOT in photos, NOT in cloud
• Separate browser profile for crypto
• Minimal browser extensions (wallet only)
• A hardware 2FA key for all accounts (not SMS)
• Separate email for crypto
• A no-logs VPN when using DeFi
• Password manager with unique passwords
• Monthly revoke of stale token approvals
• Address monitoring with movement alerts
• Never discuss amounts publicly
• Bookmarks for all DeFi sites (never through Google)

:::details{badge=Advanced title="Maximum Level Checklist"} The maximum level builds on medium – take it on when the amounts are genuinely large:

:::p{html}

• Everything from medium level +
• Dedicated laptop for crypto (no other tasks, games, browsing)
• Multiple hardware wallets: one for DeFi (hot), one for cold storage
• Multisig for large amounts (2-of-3)
• Timelock on large transfers
• Legal structure (LLC, trust)
• Estate plan (notary + instructions)
• Separate phone for crypto-related 2FA
• Darkweb monitoring for your data leaks
• Don't use ENS for cold storage
• Regular rotation of hot wallet addresses
• Passphrase wallet (seed = decoy, seed + passphrase = real funds)
• Shamir Backup or geographic distribution of seed shares
• Air-gapped signing (QR or microSD, no USB/Bluetooth)

:::further{label="Further Reading"}

• Crypto Security Guide |
• YubiKey Setup | yubico.com :::

:::quiz{id=q-4-4-s3 label="Check yourself" correct=1 explanation="Security is only as strong as its weakest link: an advanced trick with a skipped basic is useless. Finish the basic checklist first, then climb."} What's the most common mistake when building OpSec levels?

• Revisiting your threat model too frequently
• Skipping levels: a Shamir backup but no exchange 2FA
• Choosing tools that cost more than the portfolio itself
• Using the same hardware wallet for every address :::

:::section{mins=3} Physical Security :::

:::lead January 2023, London: a crypto investor shows off his portfolio on his phone over dinner with friends. Two weeks later, his home is robbed. The lesson is blunt — what others don't know about your holdings, they can't come and take. Physical security is the foundation under everything else. :::

:::p The rules of physical security are few and blunt. Keep the seed on paper or metal in a safe or a bank deposit box — never in a photo, a cloud drive, or a note on your phone, because each of those is one breach away from public. Don't discuss amounts with friends or family beyond the minimum your estate plan requires (§7). Don't leave a hardware wallet sitting in view, and don't open your wallet in public places where a screen or a PIN entry can be watched. :::

:::p{html} How to actually back up a seed (paper, metal, bank deposit box, Shamir) lives in → Wallets. What matters here is the physical angle: paper ignites at ~230°C, while metal backups (Cryptosteel, Billfodl, Blockplate, $30–100) survive up to 1500°C and shrug off water. The physical-security rule: two copies must never die in the same event – fire, flood, or theft should not take all of them at once. :::

:::callout A museum vault holds a painting worth millions. The museum doesn't hang it in an open courtyard – it sits in a climate-controlled room with humidity regulation, behind armored glass, with guards and cameras. Nobody photographs the vault layout for Instagram. They transport the painting in a special case, with an escort, on a route that's never published. If someone steals it, the museum can't call the bank and ask to "reverse the theft." Your seed phrase is that painting: a one-of-a-kind original, irreplaceable if lost. And it deserves the same treatment – not like a Netflix password, but like a masterpiece that can never be restored. :::

:::keypoints{label="Key Points"}

• In January 2025 kidnappers severed Ledger co-founder David Balland's finger while demanding €10 million – the attack was possible because his role at the company was public knowledge
• Confirmed wrench-attack losses in 2025 exceeded $40.9 million (CertiK data); the real figure is higher due to unreported cases
• A seed backup has to survive a single disaster: keep copies in separate places (home plus a bank box) and on fireproof metal rather than paper, so that one fire, flood, or break-in can't take them all at once
• html: A passphrase wallet (25th word) generates two distinct addresses from one seed: the first is a decoy holding $100–500, the second holds your real funds; the attacker sees only the decoy → Wallets :::

:::details{badge=Advanced title="Wrench Attack Defense: Passphrase and Plausible Deniability"} :::p{html} Four defense layers against a wrench attack: :::

:::p{html}

1. Plausible deniability. A passphrase wallet (the "25th word"; setup is in → Wallets) turns one seed into two sets: 24 words open a decoy ($100–500), 24 words + passphrase open your real funds. Under coercion you hand over the seed – the attacker sees only the decoy. Store the passphrase apart from the seed: lose it and the main wallet is gone forever. Important caveat: a decoy only works while the attacker doesn't know your balances. If they have traced the address or seen a leak, handing over $500 against known millions only proves you are hiding the rest – and invites them to push harder. So prevention comes first – don't expose amounts; and under direct physical coercion it is safer to hand over what is accessible: your life is worth more than the funds. :::

:::p{html} 2. Multisig. A Gnosis Safe 2-of-3 setup: you + spouse + lawyer. Even under coercion, a single person cannot transfer funds – two confirmations are required → Smart Contracts. :::

:::p{html} 3. Timelock. Large transfers are delayed by 24–48 hours. During that window you can cancel or call for help. :::

:::p{html} 4. Geographic distribution. Keys or Shamir shares are stored in different cities or jurisdictions: physical access to all of them simultaneously is impossible. :::

:::p{html} Real-world math: the average wrench-attack loss in 2025 was roughly $568K ($40.9M across 72 cases, CertiK). A $500 decoy on a passphrase wallet costs 0.09% of that amount. ::: :::

:::further{label="Further Reading"}

• Casa Security | casa.io
• Cryptosteel | cryptosteel.com
• CertiK Skynet Wrench Attacks Report | certik.com :::

:::quiz{id=q-4-4-s4 label="Check yourself" correct=2 explanation="The 24 words open a decoy holding $100–500; 24 words + passphrase open the real funds – the attacker sees only the decoy. But the passphrase must never be stored with the seed."} How does a passphrase wallet (the "25th word") help under physical coercion?

• It encrypts the seed on disk so it can't be read without the password
• It freezes access to funds for 48 hours after a suspicious login
• One seed yields two wallets: a small decoy and the real one
• It hides the main balance, showing only a small amount until you enter a PIN :::

:::section{mins=4} Digital Hygiene :::

:::lead You can buy a Ledger for $79, but if your exchange password is "qwerty123" and the same one guards your email and Discord, a single leaked database hands over everything. Without basic digital hygiene, every other measure is useless. :::

:::howto{label="Minimum for everyone"}

• Unique passwords via password manager (1Password, Bitwarden)
• 2FA on all accounts (NOT SMS, use authenticator or hardware key)
• OS and browser updated
• Don't install random browser extensions
• Don't download random files from Discord/Telegram
• A browser profile used only for crypto: wallet and DeFi bookmarks, no other extensions or personal browsing :::

:::p{html} SIM-swap is the main targeted attack on your phone. The attacker harvests your data from breaches and social media, impersonates you to the carrier ("lost my phone, need a new SIM"), and ports your number to their SIM. Verification usually happens not in a store with a passport but remotely, by knowing your personal details (a security word, "secret questions"), which is exactly what makes this route the weak link. Once ported, every SMS, and with it your 2FA codes and exchange access, goes to them. The defense is essentially one thing: never use SMS as 2FA – then there's nothing to intercept; on top of that set a carrier PIN or port-freeze and keep the second factor in an authenticator app or a YubiKey (a hardware key is mandatory on exchanges holding large amounts). For large holdings, a phone used only for 2FA (no SIM, WiFi only) removes the link entirely: even if your main number is hijacked, the authenticator on that device stays untouched. :::

:::p{html} The second non-negotiable habit is anti-phishing. The full rules (bookmarks instead of search, URL checks, Rabby simulation) are covered in → Scams and → Transactions; here the point is to make them routine, not a one-time check. :::

:::p{html} The advanced tools for this – hardware 2FA, a separate email, a dedicated browser and DNS, a VPN – are organized by level in the checklists above (§3). What matters here isn't the list but the idea of digital hygiene itself: applying them regularly, as a habit, not configuring them once and forgetting. :::

:::callout Picture a house with a $5,000 armored front door – and a ground-floor window left ajar. A burglar won't bother with the door; they'll climb through the window. Digital hygiene is exactly this: your security equals your weakest entry point, not your strongest. A $79 hardware wallet won't save you if the same "qwerty123" guards the email that recovers your exchange access. The point of hygiene is to close every window, not to reinforce one door. :::

:::keypoints{label="Key Points"}

• Password reuse is the most common breach: one leaked service opens every account that shares the password. A password manager gives each site a unique password while you remember only the master password (a seed phrase never goes in it – see §1 for why)
• An authenticator app is tied to its device: lose the phone without backup codes or an export and you lose access too. Save the backup codes when you enable 2FA and keep a spare key or device in reserve
• Most infections come not through code flaws but through stale software and a careless click: keep your OS and browser updated, extensions minimal, and never open files from Discord/Telegram. This closes the mass-attack vector almost for free
• haveibeenpwned.com shows whether your email has appeared in a breach; if it has, rotate passwords and enable 2FA on linked accounts. Check periodically, not just once :::

:::details{badge=Advanced title="Maximum Digital Security"} This is the ceiling of digital hygiene: you reach for it when the basic habits aren't enough because you're a visible target. The principle is simple: isolate everything and keep your keys away from any internet-connected machine, so that compromising one piece can't reach your funds. Four tools cover this from different angles.

:::p{html} Qubes OS – an operating system where every application runs inside an isolated virtual machine (VM). Your crypto browser sits in one VM, email in another, personal files in a third. Compromising one VM doesn't touch the rest. Edward Snowden has publicly recommended Qubes. Downside: requires 16+ GB RAM and familiarity with Linux. :::

:::p{html} Tails OS – an "amnesic" system that boots from a USB drive. After shutdown it leaves no trace: no history, no cache, no files. Ideal for one-off operations like recovering a wallet from seed: boot Tails → enter seed → transfer funds → shut down → data gone. :::

:::p{html} Air-gapped signing. Keystone Pro and Coldcard Mk4 have no USB, Bluetooth, or WiFi. Transactions pass via QR code or microSD: the computer builds an unsigned transaction → displays a QR → the device reads the QR offline → signs → displays a signed QR → the computer scans and broadcasts. Even if the computer is infected, keys never leave the device. :::

:::p{html} Faraday bag ($15–40) blocks all radio signals: NFC, Bluetooth, WiFi, cellular. Storing a Keystone or Coldcard in a Faraday bag between sessions adds another layer of isolation against remote firmware attacks. :::

:::p{html} Who needs this: portfolios above $500K, public figures in crypto, multisig treasury operators for DAOs. For everyone else, the medium level with YubiKey and a separate browser is sufficient. ::: :::

:::further{label="Further Reading"}

• Qubes OS | qubes-os.org
• Tails OS | tails.net
• Keystone Hardware Wallet | keyst.one
• NIST Password Guidelines | nist.gov :::

:::quiz{id=q-4-4-s5 label="Check yourself" correct=1 explanation="All it takes is convincing a carrier to reissue the SIM, and your 2FA codes go to the attacker ($26M in US losses in 2024, FBI). Use a YubiKey or a TOTP app – never SMS."} Why shouldn't you use SMS for 2FA on crypto accounts?

• SMS codes are visible on a locked phone screen
• SIM-swap: your number is ported to another SIM and the 2FA codes intercepted
• SMS codes stay valid too long and can be brute-forced
• Carriers store SMS on servers, where they can be pulled in a breach :::

:::section{mins=3} Specific Tools :::

:::lead This chapter gathers every tool from the sections above into one list, sorted by level and with ballpark prices. Treat it as examples, not a prescription: what matters is the category — a hardware wallet, non-SMS 2FA, a password manager — while the specific product is your call. :::

:::p The tables split into two sets. The basic stack stops mass attacks and everyone needs it; the advanced stack is added for large amounts and for specific threats from your own model (§2), not "just in case." Prices are indicative — an order of magnitude rather than a price list, and almost every line has free or cheaper equivalents. The deciding column is "Why": it's the purpose, not the "Examples" column, that tells you whether a tool is for you. :::

:::p{html} Basic level: :::

:::p{html}

:::p{html} Where to buy a hardware wallet. Only from the manufacturer or authorized resellers: never third-party marketplaces, discount sellers, or used. The most common scam: the device or box arrives with a ready-made "recovery phrase" (a card, a sticker, or "enter these words" instructions); the scammer keeps a copy and drains the wallet the moment you fund it. A genuine device never arrives with a pre-set PIN or seed: the phrase is generated only by you, on the device, during first setup. There are also counterfeit units whose firmware quietly exfiltrates the seed during initialization (often 30–60% cheaper, and that discount is the bait). After unboxing, run the Genuine Check in the app, and never enter your seed into any site or app. :::

:::p{html} Advanced level: :::

:::p{html}

:::callout Walk into a working kitchen and you won't find one magic gadget — you'll find the right tool for each job. A home cook needs a decent chef's knife, a board, and one good pan; a restaurant line adds a blast chiller, a sous-vide bath, and a dozen specialized blades because the volume demands it. Nobody buys the restaurant kit to cook a weeknight dinner. And which brand of knife sits on the magnet is the cook's own preference — what matters is that it's sharp and the right shape for the cut. The tool list below reads the same way: match the category to your level, and let taste decide the label. :::

:::keypoints{label="Key Points"}

• Replacing TOTP codes (Google Authenticator) with a YubiKey ($50) blocks SIM-swap completely: the key is bound to a physical device and never transmits over the network – unlike SMS and even TOTP, which can be copied if someone accesses your phone
• Quad9 DNS (9.9.9.9) blocks requests to known malicious domains at the DNS level – free protection that kicks in before the browser even opens the page
• html: Revoke.cash displays all active token approvals and lets you revoke them in one click – a monthly check reduces the risk of a drain through a forgotten approval on an old contract → Transactions :::

:::details{badge=Advanced title="Maximum Stack"} :::p{html} The maximum stack is a shift in principle: removing the single points of failure that remain even at the medium level. Each tool here closes a specific residual risk – signing and storage move offline (Keystone, Coldcard: keys never touch a networked device), control over funds is split across several signers (Gnosis Safe), and your working environment, messaging, and backups are isolated from one another (Qubes, Signal, Cryptosteel). This is the level for $100K+ portfolios, public figures, and DAO treasuries – for everyone else it's overkill that only adds friction.

You don't need to assemble the whole stack at once: start with whichever link is your weakest right now – usually online signing or sole control over a large balance. :::

:::further{label="Further Reading"}

• YubiKey Setup Guide | yubico.com
• Mullvad VPN | mullvad.net
• ProtonMail | proton.me :::

:::quiz{id=q-4-4-s6 label="Check yourself" correct=2 explanation="SMS is stolen via SIM-swap and a TOTP secret can be copied if someone reaches your phone. A YubiKey is bound to hardware – which is why you keep two: a primary and a backup."} Why is a YubiKey safer than SMS or even a TOTP app?

• It generates longer one-time codes than TOTP
• The secret is stored in an encrypted cloud and synced across devices
• It's a physical key: the secret never leaves the device or travels the network
• It isn't tied to your phone, so you can't lose it along with your number :::

:::section{mins=4} Estate Planning :::

:::lead You're the only person alive who knows the combination to a safe holding a million dollars. Tomorrow a bus hits you, and the million is gone for good. It isn't hypothetical: an estimated 3–4 million BTC are lost forever, much of it because access died with the owner. Estate planning is the fix, and it can't wait. :::

:::p That estimate is worth sitting with: 3–4 million BTC, about a fifth of all that will ever exist, are gone for good — and a large share simply because the owner died without leaving a way in. At $100K per coin that's $300–400 billion locked behind dead men's passwords. The remedy, by contrast, is mundane, and it works at any size of holding. :::

:::p{html} The simplest plan has three parts that stay separate on purpose. The first is a letter of instruction: a plain document stating that you own crypto, roughly how much, and how someone would access it — but never the seed itself. The second is the seed phrase in a sealed envelope, deposited with a notary or in a bank safety-deposit box, physically apart from the letter. The third is a short instruction for your family: who to contact, where the envelope is, and that the steps inside must be followed in order. Keeping the three apart means no single document, and no single person, can drain the wallet alone. :::

:::callout Imagine sending a valuable package – not by regular mail, but by certified letter with a declared-value inventory, through a notary. The letter is sealed; the envelope reads: "open only in the presence of a lawyer and two witnesses." A copy of the inventory is with the notary, another in a bank safety-deposit box. Even if one envelope is lost, the remaining copies let you reconstruct the contents. Estate planning in crypto works the same way: sealed instructions in multiple locations, trusted people who know the procedure, and the seed phrase itself never passing through unsecured channels – no email, no messenger, no cloud. :::

:::keypoints{label="Key Points"}

• A "dead man's switch" is a service that requires periodic proof of life (monthly or quarterly); if you fail to respond N times in a row, instructions are automatically sent to your trusted contacts (Google Inactive Account Manager is a free option for non-crypto data)
• Family instructions must be written for someone with zero crypto experience — literal and step by step: which app to install, how to connect the device, where to enter the words from the envelope, and how to move funds to an exchange and out to a bank
• Never put a seed phrase in a will – a will becomes a public document once probate opens; the will should only state: "digital assets are stored per instructions held by notary [name]" :::

:::details{badge=Advanced title="Shamir's Secret Sharing and Dead Man's Switch"} The simple three-part plan above covers most cases. This block is for larger amounts and for anyone who wants to remove a single point of failure: how to split the seed across several stores (Shamir), how to set up an automatic trigger if you go silent (a dead man's switch), and how to spread control through a family multisig.

:::p{html} Shamir's Secret Sharing (the K-of-N mechanics are in → Wallets): a seed is split into N parts, K of which restore it. For inheritance, what matters isn't how it works but how you distribute the parts – so no single person can assemble the seed alone, and losing one part doesn't lock your heirs out. :::

Share distribution:

:::howto{label="Share distribution"}

• Part 1: safe at home
• Part 2: bank safety deposit box
• Part 3: with a lawyer
• Part 4: with a close relative (different city)
• Part 5: in a different country :::

The "how to assemble" instructions are the most underrated part of the plan. Write them in plain language for one specific person with no crypto experience: which app to install, how to connect the device, where to enter the words from the envelope, how to move funds to an exchange and out to a bank. Two things people forget: confirm the heir can actually follow the steps alone (have them read it without your help), and update the instructions whenever you change wallet or exchange — stale steps are worse than none.

:::p{html} Dead man's switch: a service that requires periodic proof of life (monthly or quarterly). If you fail to respond N times in a row, it automatically sends pre-prepared instructions to your trusted contacts. :::

:::howto{label="Services"}

• Casa ($120/year) – managed key recovery + inheritance planning
• Safe Haven – digital inheritance on blockchain
• Google Inactive Account Manager (free) – for non-crypto data: if the account is inactive for N months, designated contacts are notified :::

:::p{html} Family multisig. A multisig wallet (Safe, for example) on a 2-of-3 scheme: keys held by you, your spouse, and a lawyer, with any two needed to approve a transfer. While you're alive it's you plus either one; if you're gone, the remaining two act together. But 2-of-3 removes one single point of failure and creates another: any two signers can move the funds without you — meaning the spouse and the lawyer, in collusion, can bypass both you and the other heirs. So you choose signers whose collusion is either impossible (independent parties with no shared interest) or harmless (they are the heirs themselves — the money stays in the family either way). Add a timelock on large transfers as a backstop: a few days' delay leaves room to contest a movement, and a licensed fiduciary lawyer risks liability for abuse. For large estates, 3-of-5 with independent, separated keys is safer — collusion then needs a majority, not just two → Smart Contracts. ::: :::

:::details{badge=Advanced title="Legal Aspects and Common Mistakes"} :::p{html} Legal structures for crypto inheritance:

• Will: include crypto assets in the will, but never list seed phrases or keys – a will becomes a public document once probate opens. Wording: "digital assets are stored per instructions in a sealed envelope held by notary [name, contact]."
• Trust/LLC: in certain jurisdictions (US – Wyoming, Nevada; Switzerland; Liechtenstein) crypto can be registered under a legal entity (LLC or trust). On the owner's death, control passes to designated beneficiaries per trust documents – no probate required. Setup cost: $500–$5,000 depending on jurisdiction.
• Tax implications: in most countries crypto inheritance is subject to inheritance tax at market value on the date of death. In the US: the federal threshold is $13.61 million (2024); below that, the rate is 0%. In the EU: varies by country (Germany: 7–50% depending on the relationship and amount). The family should be prepared for tax obligations.

:::further{label="Further Reading"}

• Casa Inheritance | casa.io
• Shamir's Secret Sharing | wikipedia.org
• Wyoming DAO LLC Act | sos.wyo.gov :::

:::quiz{id=q-4-4-s7 label="Check yourself" correct=1 explanation="A will should only state that assets are held “per instructions with a notary,” with the seed in a separate sealed envelope. Otherwise the inheritance becomes a publicly accessible key."} Why must you never put a seed phrase directly in a will?

• A notary isn't allowed to certify cryptographic keys
• Once probate opens, the will becomes public and outsiders would see the seed
• Paper isn't durable, and a written seed becomes unreadable over time
• Heirs won't be able to prove the wallet belongs to them :::

:::section{mins=5} Blockchain Privacy :::

:::lead You withdrew ETH from an exchange to your own address. The exchange knows your name — and the moment that record leaks or is requested, whoever holds it can read every transaction, balance, and NFT you own. The blockchain is public. Privacy isn't a crime; it's a right. :::

:::p The link between an address and a real name forms in ordinary steps. You pass KYC on an exchange, then withdraw to your own address — so the exchange now ties that address to your identity, and a compliance request or a data leak makes the link public. You can also hand it over yourself: an ENS name like vitalik.eth points straight at your balance, and a single "look at my new NFT!" post connects your handle to the wallet that minted it. :::

:::p{html} Basic address hygiene – separate addresses per purpose, don't publish them, no ENS on cold storage – is covered in → Block Explorers; it's the necessary minimum, but it only makes analysis harder, it doesn't hide the data. To actually conceal amounts and links there's a separate class of cryptographic tools – their spectrum and trade-offs are below. :::

:::callout A house with glass walls on a busy street – every passerby can see what you eat for dinner, how much money is on the table, which books you read, and who comes to visit. You're not doing anything illegal – but living in an aquarium is uncomfortable. Curtains aren't a sign of criminality; they're a normal desire for privacy. A public blockchain is a glass-walled house: every transaction, every balance, every interaction is visible to all. Privacy tools are the curtains: they don't hide crimes – they restore the normal state in which your finances are your own business. :::

:::keypoints{label="Key Points"}

• KYC leaks are a real attack vector: in 2020 attackers stole a Ledger database of 272,000 customers including names, addresses, and phone numbers; victims still receive phishing emails and physical threats years later
• Privacy is a spectrum, not an on/off switch: from Monero (everything hidden by default) to Ethereum, where it's added in layers – stealth addresses, shielded pools, FHE; you choose what to hide
• After Tornado Cash, tools shifted from black-box anonymity to "privacy + provable legitimacy": Privacy Pools let you prove your funds aren't linked to crime without revealing your history
• Privacy isn't absolute – it's only as strong as the anonymity set, and timing plus your network IP can re-link the flows; a privacy tool without address hygiene and a VPN is only half a defense :::

:::details{badge=Advanced title="Modern Privacy Technologies"} On-chain privacy is a spectrum, not a switch. At one end is network-level privacy: Monero hides everything by default, Zcash offers optional "shielded" transactions via ZK. At the other is Ethereum: the chain is transparent, and privacy is added in separate layers. There are four, each hiding something different:

:::p{html} Stealth addresses (the ERC-5564 standard). The sender derives a one-time address for you from your "meta-address," so an observer can't link the payment to your main wallet. This is privacy at the receiving layer, built into the wallet rather than an external mixer (Vitalik Buterin co-authored the standard). Implementations: Umbra (over 77,000 addresses), Fluidkey; native Ethereum support is in progress. :::

:::p{html} Shielded pools (ZK). You deposit into a shared pool and spend via a zero-knowledge proof – your balance and the deposit→withdrawal link stay hidden. Railgun, Aztec (privacy as an L2 layer, not an overlay), and Hinkal belong here. :::

:::p{html} Privacy Pools (association sets). The next generation of mixers: ZK plus association sets. You cryptographically prove your funds are not linked to criminal addresses without revealing your own history. Launched on Ethereum mainnet in March 2025 – from a paper Vitalik co-authored, and he was among the first users. :::

:::p{html} FHE – computing on encrypted data. Fully Homomorphic Encryption lets a smart contract compute directly over ciphertext without decrypting it. Zama's fhEVM launched the first production mainnet with confidential USDT in late 2025, and a confidential-token standard (ERC-7984) has appeared. The key idea is selective disclosure: data stays hidden from the public but is provable to an auditor when needed. :::

:::p{html} The common shift. After the Tornado Cash sanctions, the field moved away from "black-box" anonymity toward "privacy + provable legitimacy" (association sets, selective disclosure). It's also Ethereum's official direction – the Privacy Stewards of Ethereum roadmap: private payments, selective disclosure, privacy L2s, and decentralized identity. :::

:::p{html} The honest limits. Privacy is only as strong as the anonymity set: while a pool has few participants, there's barely a crowd to hide in. Even stealth addresses fail if metadata gives you away – transfer timing and your network IP can re-correlate the flows, so a privacy tool without address hygiene and a VPN is only half a defense. And the contract or relayer itself is a new attack surface, while confidential transactions cost more than ordinary ones. ::: :::

:::details{badge=Advanced title="Regulatory Pressure and Compliant Privacy"} :::p{html} Tornado Cash timeline – a precedent for the entire industry:

• August 2022: OFAC (the US Treasury's Office of Foreign Assets Control) added Tornado Cash to the sanctions list, claiming the protocol laundered over $7 billion. Smart-contract addresses were blocked – any interaction became a sanctions violation for US residents.
• May 2024: a Dutch court sentenced co-founder Alexey Pertsev to 64 months in prison for facilitating money laundering.
• November 2024: the US Fifth Circuit Court of Appeals ruled that OFAC exceeded its authority – immutable smart contracts do not qualify as "property" under IEEPA because nobody owns or controls them.
• March 2025: OFAC officially lifted the Tornado Cash sanctions, complying with the court ruling.
• August 2025: a New York jury delivered a mixed verdict on co-founder Roman Storm: guilty of operating an unlicensed money transmitter, but deadlocked on the more serious money-laundering and sanctions charges.

De-sanctioning a protocol doesn't protect the people who built it: its developers still face criminal liability. Users who interacted with Tornado Cash during the sanctions period technically violated the law – even if their funds were entirely legitimate.

:::p{html} Meanwhile the market is being legitimized. Railgun's share of crypto mixers grew from 13% (2022) to 71% (2025), on roughly $4 billion in volume and a TVL around $100 million (DefiLlama; ~$90–113M in late 2025) – demand shifted toward tools with provable legitimacy. And in March 2026, in a report to Congress (under the GENIUS Act), the US Treasury for the first time acknowledged that mixers have legitimate uses – shielding personal wealth, business payments, and donations – while maintaining its anti-money-laundering stance. ::: :::

:::further{label="Further Reading"}

• Privacy Stewards of Ethereum (roadmap) | pse.dev
• ERC-5564 Stealth Addresses | eips.ethereum.org
• Privacy Pools (0xbow) | 0xbow.io
• Zama fhEVM | zama.ai
• Railgun Protocol | railgun.org
• OFAC Tornado Cash Delisting | ofac.treasury.gov :::

:::quiz{id=q-4-4-s8 label="Check yourself" correct=1 explanation="Tornado Cash sanctions were lifted in March 2025, yet Pertsev was sentenced to 64 months in the Netherlands and Storm was convicted in the US on one count — unlicensed money transmitting (the jury deadlocked on the heavier charges). Both verdicts are under appeal. A tool's legal status and your liability for using it are separate things."} What's the key lesson of the Tornado Cash case for an ordinary user?

• Using any mixer automatically makes you complicit in money laundering
• Lifting sanctions protects neither the developers nor past users of the protocol
• Once sanctions are lifted, all past Tornado Cash transactions count as legal
• Regulators concluded that private transactions can't be traced or banned :::

:::section{mins=3} Maintenance: The Weekly Loop :::

:::lead Fifteen minutes on Sunday morning — checking balances, updating wallets, reading one incident postmortem — turns security from a one-time setup into a working habit. :::

:::p You've set up your security — password manager, 2FA, hardware wallet, hot/cold split. Does that mean you can forget about it for six months? The crypto space answers "no" roughly once a week. Protocols discover vulnerabilities, wallets release patches, new scam schemes appear faster than old ones disappear. Security isn't a state — it's a process. :::

:::p Why weekly? Daily is exhausting, and you'll quit within a month. Monthly is too infrequent: in December 2023, the compromised Ledger Connect Kit hit dozens of DeFi frontends within two hours, and users who followed security news weekly learned about the threat before they lost funds. A week is the optimal cycle: frequent enough to catch everything, rare enough not to become a chore. :::

:::p The specific ritual: pick a day (say, Sunday morning) and set aside 15 minutes. Anchor it to an existing habit — "after morning coffee I check crypto security." A habit tied to a trigger sticks far better than an abstract intention. :::

:::p{html} Three blocks of five minutes. First — asset review: open DeBank and scan your positions. All balances intact? Unfamiliar tokens appeared? This could be a dust attack: a tiny amount of an unknown token lands as bait, and interacting with it (approve, swap) triggers a drain contract → Scams. If you have positions in lending protocols, check the health factor: below 1.5 means you're approaching liquidation. :::

:::p Second block — updates. Update Rabby or MetaMask to the latest version (security patches), check your hardware wallet firmware via Ledger Live or Trezor Suite, update your browser. An outdated wallet version is an open attack surface. :::

:::p Third block — security news. Read one incident write-up on rekt.news or DeFiLlama Hacks. Ask yourself: "Am I using a protocol that was hacked today? Does my behavior pattern resemble what led to those losses?" :::

:::callout{icon=🌱} A weekly security check is like weeding the garden. Every Sunday you step outside for 15 minutes and pull weeds while they're small. Each individual weed is trivial: two tugs and it's in the bucket. But skip two or three weeks, and the weeds intertwine with the crop roots, stealing water and sunlight — now instead of 15 minutes, you need three hours with a hoe. Skip a month, and the bed is lost: easier to dig up and start over. The weekly crypto security ritual works the same way: small efforts that prevent big problems. :::

:::details{badge=Advanced title="Monitoring Automation"} Manual weekly checks cover normal operations. Automation is for emergencies — when you're asleep and your protocol is being exploited.

:::p{html} At the free tier, which everyone should set up, Etherscan Watch List sends an email on any transaction involving your addresses — setup takes two minutes → Block Explorers. DeBank's mobile app adds push notifications on balance changes, so you learn about fund movements even without checking email. :::

Active DeFi users will benefit from Tenderly Alerts, which lets you define precise trigger conditions: for example, "notify if Aave health factor drops below 1.3" or "if an approval is revoked by someone other than me." The free plan supports up to five alerts. Telegram bots (@EtherDrops_bot, @whale_alert) are even faster, delivering notifications within 10–30 seconds of a transaction — noticeably ahead of email.

For larger portfolios ($50K+), treasury-grade tools are available. Forta Network is a decentralized monitoring bot network that detects anomalous patterns such as mass approvals or flash-loan calls. OpenZeppelin Defender goes further, letting you configure automatic actions on incidents — for example, pausing a contract or triggering an emergency withdrawal. :::

:::further{label="Further Reading"}

• rekt.news | Archive of exploit and rug pull breakdowns
• Tenderly | Advanced monitoring with custom conditions :::

:::quiz{id=q-4-4-s9 label="Check yourself" correct=2 explanation="An unfamiliar token you never bought is the classic dust-attack bait. Approving or swapping it can hand a drain contract permission to move your real assets, so the safe move is to ignore it entirely — don't approve, don't swap, don't send."} What should you do if an unfamiliar token you didn't buy appears on your address?

• Sell it on a DEX while it's still worth something
• Approve it in your wallet and check what it is
• Don't interact with it — it could be a dust attack, and approve/swap may trigger a drain contract
• Send it to another address to clean up your wallet :::

:::section{mins=4} Monthly Audit & Quarterly Check :::

:::lead Approvals pile up, paper backups fade, concentration in a single protocol creeps higher — a monthly audit catches the strategic risks that weekly checks miss. :::

:::p The weekly ritual catches tactical problems: updates, dust attacks, positions approaching liquidation. The monthly audit is a strategic review: stepping back to assess the bigger picture. You're not asking "was something stolen yesterday" but "have risks accumulated that will blow up tomorrow?" :::

:::p{html} A typical example: over the past month you approved ten protocols while testing new DeFi products. You no longer use eight of them. Each approve is permission for a smart contract to spend your tokens without limit. If one of those contracts gets compromised, the approve lets it take everything. In practice, an active DeFi user accumulates 20–50 approvals over six months. Revoking on L2 costs under $0.01 → Transactions. :::

:::p The second focus is physical backup security. Paper seed phrases degrade: ballpoint ink fades within 2–3 years under high humidity; pencil lasts longer but smudges. A monthly check takes 30 seconds: all words legible, paper undamaged, backup in place. If the seed has been on paper for more than two years, consider a metal backup (Cryptosteel, Billfodl, $30–100): it solves the degradation problem permanently (§4). :::

:::p Third focus: digital hygiene. Check haveibeenpwned.com — if your email appeared in a breach, credential stuffing is already knocking. Review browser extensions — remove anything you don't use. Check active sessions on exchanges: if you see a login from an unfamiliar device, change the password immediately. :::

:::p And have you concentrated too much of your portfolio in one protocol? More than 20% is a gamble. Anchor Protocol users on Terra who held 50%+ in UST lost everything in May 2022 within 72 hours. :::

:::p Every quarter, add three checks to the monthly audit. Address rotation: if an address has been "exposed" through exchange KYC or a public ENS — create a new one for DeFi and transfer assets. In 2020, the Ledger customer database of 272,000 people leaked: victims still receive phishing emails and physical threats years later (§8). Storage strategy review: if your portfolio grew, compare against the thresholds in §3. And most importantly — a recovery test: take your backup seed phrase and verify you can actually restore access (not on your main device — on a separate one or in test mode). :::

:::p{html} Two quarterly habits round out the audit. If you keep an estate plan (§7), keep it current — changed addresses, new wallets, or a different trusted contact quietly void it, and a plan describing last year's portfolio won't work when it's needed. And review the protocols where your funds sit: for each, was there an incident in the past month (rekt.news)? When was the last audit and who ran it → Audits? Has TVL dropped sharply (>30% in a month is a warning sign)? :::

:::callout{icon=📰} A monthly audit is like a fact-checker's job at a newsroom. Every day, journalists file stories (the weekly ritual watches the day-to-day). But once a month, the fact-checker pulls the archive and reviews: have the numbers in published articles gone stale? Has a source retracted their statement? Has a link broken? Problems accumulate invisibly — yesterday a figure was accurate, today it's not. Without a fact-checker, the newsroom doesn't notice credibility eroding. Your portfolio is the same "newsroom": approvals accumulate, paper backups fade, concentration in one protocol creeps up — all of it invisible until you run the audit. :::

:::further{label="Further Reading"}

• Revoke.cash | Check and revoke token approvals
• haveibeenpwned.com | Check your email for data breaches :::

:::quiz{id=q-4-4-s10 label="Check yourself" correct=1 explanation="An approval is a standing permission for a contract to move your tokens, and it persists long after you stop using the protocol. If that contract is later compromised, the attacker drains your funds through the permission you already granted — which is why revoking unused approvals each month matters."} Why are approvals left on unused protocols dangerous?

• They slow down the wallet
• Each approve lets the contract spend your tokens — if the contract is compromised, the attacker takes everything through the existing permission
• They increase fees on future transactions
• They're publicly visible and expose your portfolio :::