Growth · 2 min read
"Write Down These 24 Words" — The Backup Nobody Does Right
🔑 "Write Down These 24 Words" — The Backup Nobody Does RightThe recovery phrase instruction during wallet setup is liability transfer disguised as user onboarding. "Write it down somewhere safe" is not a security strategy—it's an admission that the product has no better solution.The failure modes are well-documented:Chainalysis estimates $100B+ in cryptocurrency is irretrievably lost due to lost keys and forgotten recovery phrases. User research from wallet teams (published in Medium posts and discussed at Devcon) consistently shows that users either store phrases insecurely (photos, cloud storage, plaintext files) or lose them entirely (moved houses, forgot where they put the paper).The industry is slowly solving this with better backup UX patterns:→ Verification during setup. Argent's onboarding flow requires users to confirm random words from their phrase before proceeding. This catches users who skip the backup step entirely.→ Periodic recovery rehearsal. "When was the last time you verified you can recover this wallet?" prompts with guided recovery testing improve long-term backup reliability.→ Social recovery. Argent's guardian system allows designated contacts to authorize account recovery without ever accessing the seed phrase. Their published data shows 89% reduction in "lost access" support tickets compared to traditional seed-only wallets.→ Shamir secret sharing for geographic distribution. Split the phrase into shares where any M-of-N can reconstruct. Tools like Trezor's Shamir Backup and third-party implementations provide this out-of-box.The hardware wallet ecosystem is evolving too. Ledger Recover—despite its controversy documented extensively on r/cryptocurrency and the Ledger subreddit—represents an attempt at cloud-backed recovery with identity verification. The tradeoffs are debatable, but the UX problem it addresses is real.Backup UX is security UX. Make recovery possible, verifiable, and rehearsed.→ MayWap | Designing backup flows that actually work