Protecting your identity on an open ledger
In 2022, federal authorities recovered $3.6 billion in stolen Bitcoin — the largest financial seizure in US history.
How? The thieves stored their private keys in cloud storage. Plain text. The blockchain never forgets, and neither did iCloud.
This case captures both sides of self-custody: the assets were stolen because the original owners trusted an exchange (Bitfinex, hacked in 2016). The thieves lost them because they trusted cloud storage. Everyone in this story made custody mistakes.
Part 1 covered what keys are and how they relate. This part covers how to protect them — and what happens when your wallet becomes your identity.
Theory is easy. Execution is where people lose money.
Don't put everything in one place. A common setup:
If your hot wallet gets drained by a malicious contract, you lose spending money. Not your savings.
Most theft doesn't come from cracked encryption. It comes from users approving transactions they didn't understand.
Before signing anything: read what you're actually approving. What contract is this? What permissions does it want? Verify the URL — phishing sites look identical to real ones. Question unexpected requests — legitimate protocols don't DM you asking to "verify your wallet." And revoke old approvals periodically — token approvals persist forever unless you remove them. Sites like Revoke.cash let you audit what you've approved.
The Seth Green incident from Part 1? He signed a transaction. That's all it took.
Your mnemonic phrase is a physical security problem, not a digital one.
Write it on paper or etch it in metal for fire and water resistance. Store it in a safe or deposit box. Split it across multiple locations if warranted.
Never screenshot it. Never store it in cloud services. Never email it to yourself. Never type it anywhere except your wallet's official recovery flow.
The $3.6 billion recovery happened because investigators got a warrant for cloud storage. Don't make it that easy for anyone.
Your wallet address is more than a payment endpoint. It's becoming identity infrastructure.
Every transaction is permanent and public. Your address accumulates history: assets held over time, protocols used, NFTs owned, governance votes cast. This creates reputation without requiring personal information.
DAOs check wallet history before allowing participation. Protocols airdrop tokens based on past behavior. Your address is your resume.
Raw addresses are hostile to humans. 0x47bb4cCA98FC49B971d86c5t26562c86E6284CeD means nothing to anyone.
Domain services fix this. ENS gives you yourname.eth on Ethereum. Bonfida gives you yourname.sol on Solana. These names resolve to addresses, work across apps, and create consistent identity across the ecosystem.
Owning yourname.eth is like owning yourname.com in 1995 — except it points to your wallet instead of a server.
Self-custody enables pseudonymous participation — activity under a persistent identity not linked to your legal name. Your financial activity isn't automatically shared with banks or employers. You can't be discriminated against based on nationality or credit score. Different wallets can hold different identities.
But pseudonymity isn't anonymity. Sophisticated analysis can link wallets to real identities through exchange deposits, behavioral patterns, or metadata leaks. Privacy requires active effort — not just using a wallet without KYC.
Self-custody versus custodial isn't binary. Most sophisticated users operate at multiple points simultaneously.
Full self-custody — you control all keys. Maximum sovereignty, maximum responsibility. Best for significant holdings or jurisdictional concerns.
Hybrid approaches — reduce single-point-of-failure risk while preserving control. Multisig requires multiple keys to sign a transaction. Social recovery lets trusted contacts help you regain access. Smart contract wallets add programmable rules for access and recovery.
Custodial services — exchanges hold your keys. Familiar UX, customer support, sometimes insurance. Counterparty risk returns, but for small amounts or frequent trading, the tradeoff often makes sense.
Many people use all three: exchange for trading, hot wallet for DeFi, cold storage for savings.
Self-custody isn't about ideology. It's about threat modeling.
What are you protecting? $500 in ETH — an exchange is probably fine. $50,000 in diversified holdings — consider cold storage. Life savings in an unstable jurisdiction — self-custody might be essential.
From whom? Exchange insolvency — self-custody protects you. Your own mistakes — custodial services might be safer. Government seizure — depends on the government. Hackers — both approaches have vulnerabilities, just different ones.
The question isn't which approach is better. It's which tradeoffs you understand and which ones you're accepting without realizing it.
Next: Part 3 goes deeper on mnemonic phrases — the technical standards behind the 12 words that control everything.
Protecting your identity on an open ledger
In 2022, federal authorities recovered $3.6 billion in stolen Bitcoin — the largest financial seizure in US history.
How? The thieves stored their private keys in cloud storage. Plain text. The blockchain never forgets, and neither did iCloud.
This case captures both sides of self-custody: the assets were stolen because the original owners trusted an exchange (Bitfinex, hacked in 2016). The thieves lost them because they trusted cloud storage. Everyone in this story made custody mistakes.
Part 1 covered what keys are and how they relate. This part covers how to protect them — and what happens when your wallet becomes your identity.
Theory is easy. Execution is where people lose money.
Don't put everything in one place. A common setup:
If your hot wallet gets drained by a malicious contract, you lose spending money. Not your savings.
Most theft doesn't come from cracked encryption. It comes from users approving transactions they didn't understand.
Before signing anything: read what you're actually approving. What contract is this? What permissions does it want? Verify the URL — phishing sites look identical to real ones. Question unexpected requests — legitimate protocols don't DM you asking to "verify your wallet." And revoke old approvals periodically — token approvals persist forever unless you remove them. Sites like Revoke.cash let you audit what you've approved.
The Seth Green incident from Part 1? He signed a transaction. That's all it took.
Your mnemonic phrase is a physical security problem, not a digital one.
Write it on paper or etch it in metal for fire and water resistance. Store it in a safe or deposit box. Split it across multiple locations if warranted.
Never screenshot it. Never store it in cloud services. Never email it to yourself. Never type it anywhere except your wallet's official recovery flow.
The $3.6 billion recovery happened because investigators got a warrant for cloud storage. Don't make it that easy for anyone.
Your wallet address is more than a payment endpoint. It's becoming identity infrastructure.
Every transaction is permanent and public. Your address accumulates history: assets held over time, protocols used, NFTs owned, governance votes cast. This creates reputation without requiring personal information.
DAOs check wallet history before allowing participation. Protocols airdrop tokens based on past behavior. Your address is your resume.
Raw addresses are hostile to humans. 0x47bb4cCA98FC49B971d86c5t26562c86E6284CeD means nothing to anyone.
Domain services fix this. ENS gives you yourname.eth on Ethereum. Bonfida gives you yourname.sol on Solana. These names resolve to addresses, work across apps, and create consistent identity across the ecosystem.
Owning yourname.eth is like owning yourname.com in 1995 — except it points to your wallet instead of a server.
Self-custody enables pseudonymous participation — activity under a persistent identity not linked to your legal name. Your financial activity isn't automatically shared with banks or employers. You can't be discriminated against based on nationality or credit score. Different wallets can hold different identities.
But pseudonymity isn't anonymity. Sophisticated analysis can link wallets to real identities through exchange deposits, behavioral patterns, or metadata leaks. Privacy requires active effort — not just using a wallet without KYC.
Self-custody versus custodial isn't binary. Most sophisticated users operate at multiple points simultaneously.
Full self-custody — you control all keys. Maximum sovereignty, maximum responsibility. Best for significant holdings or jurisdictional concerns.
Hybrid approaches — reduce single-point-of-failure risk while preserving control. Multisig requires multiple keys to sign a transaction. Social recovery lets trusted contacts help you regain access. Smart contract wallets add programmable rules for access and recovery.
Custodial services — exchanges hold your keys. Familiar UX, customer support, sometimes insurance. Counterparty risk returns, but for small amounts or frequent trading, the tradeoff often makes sense.
Many people use all three: exchange for trading, hot wallet for DeFi, cold storage for savings.
Self-custody isn't about ideology. It's about threat modeling.
What are you protecting? $500 in ETH — an exchange is probably fine. $50,000 in diversified holdings — consider cold storage. Life savings in an unstable jurisdiction — self-custody might be essential.
From whom? Exchange insolvency — self-custody protects you. Your own mistakes — custodial services might be safer. Government seizure — depends on the government. Hackers — both approaches have vulnerabilities, just different ones.
The question isn't which approach is better. It's which tradeoffs you understand and which ones you're accepting without realizing it.
Next: Part 3 goes deeper on mnemonic phrases — the technical standards behind the 12 words that control everything.