bitcoin-wallet-backup
Wallet backup formats: BIP39 mnemonic, SLIP-39 Shamir Backup, SeedQR, CompactSeedQR, Coldcard's CTL-format, paper backup hygiene, metal backup vendors and threat models. USE WHEN: designing backup UX, evaluating backup security, helping recover a backed-up seed.
What this skill does
# Wallet Backup Formats
## BIP39 mnemonic (standard)
12 / 15 / 18 / 21 / 24 words from BIP39 wordlist + optional
passphrase. Recoverable into any BIP39-compatible wallet.
Encoding density: 12 words ≈ 132 bits (128 entropy + 4 checksum).
Average length: ~70-90 ASCII chars.
## SLIP-39 Shamir Backup
Trezor-introduced format using Shamir's Secret Sharing:
- M-of-N share threshold.
- Each share is 20-33 words from a different wordlist (1024 words).
- Can be split into **groups** (e.g., 2-of-3 family + 2-of-2 board)
for hierarchical recovery.
Use case: distributing shares geographically/socially without giving
any single party full key access.
Compatibility: Trezor (native), Keystone (partial), most others
require BIP39 → SLIP-39 conversion.
**Important**: SLIP-39 uses a different wordlist than BIP39 — the
shares are not BIP39 words.
## SeedQR
A QR code encoding of BIP39 mnemonic for hardware wallet interaction.
Format:
- Each word's wordlist index (0-2047) → 4 decimal digits → 4
characters.
- 12 words → 48-char string → QR code.
CompactSeedQR variant: encodes raw entropy bytes directly (more dense,
slightly less wallet-compatible).
Use case: airgap signing devices (SeedSigner, Krux) scan a printed
SeedQR rather than typing 12 words.
## Coldcard's CTL format
`words.txt` → 24 words newline-separated. Tarot-encoded paper grids
also supported on Coldcard for entry resilience.
## Plate / metal backups
Stamping seed words into stainless steel / titanium plates protects
against fire, water, and light damage.
Vendors:
- **Cryptosteel Capsule** — letter tiles in steel cylinder.
- **Blockplate** — stamped grid.
- **SeedXOR** — XOR-based two-plate scheme (2-of-2).
- **Hodlr Plate** — center-punch grid.
- **Cobo Tablet** — stainless steel embossed plates.
Trade-offs:
- Stamped plates: durable but visible; unauthorized observer can
read words.
- Tile-based: theft-detect-friendly (one missing tile breaks key).
- XOR plates: unreadable without both halves.
## Paper backup hygiene
- Use **acid-free** paper for >5 year shelf life.
- Avoid thermal printer paper (fades).
- **Don't laminate** seed-on-paper unless you also want to make it
indestructible by fire — laminated paper burns sealed inside its
pouch and is harder to destroy intentionally.
- Store in **2+ physical locations** — single point of failure.
## Threat model considerations
| Threat | Mitigation |
|--------|-----------|
| House fire | metal backup + offsite copy |
| Flood | metal backup + offsite |
| Burglary | hidden / encrypted (passphrase) |
| Coercion | passphrase = "duress" wallet with small balance + BIP85 main wallet |
| Heir access | Shamir 2-of-3 with a lawyer / family member / safety deposit box |
| Inheritance | encrypted instructions revealed on death (Casa Inheritance, dead-man switches) |
## Passphrase backup
Passphrase ("25th word") is **not** included in the BIP39 mnemonic.
It must be backed up **separately** with the same care.
- Store somewhere completely different from the seed.
- Memorize if possible.
- If compromise risk is real, use multi-factor (e.g., split into 2
pieces).
**Loss of passphrase = loss of wallet** (no protocol-level recovery).
## Backup verification
After backup, **practice recovery** before depositing real funds:
1. Erase the wallet.
2. Restore from backup (and passphrase, if used).
3. Verify the first receiving address matches.
4. Optionally: sign a test message and verify with original
recorded data.
Many funds are lost not from the seed loss but from a backup that
was never tested.
## Common pitfalls
- **Photo of seed** on phone → cloud-synced → exposed.
- **Passphrase not backed up** → permanent loss.
- **Confusing BIP39 ↔ SLIP-39 wordlists** during recovery.
- **Using a wallet's "backup file" (encrypted blob)** without
understanding what's inside — wallet-specific format may not be
importable elsewhere.
- **Single backup location** → physical risk.
- **Mixed-up passphrase capitalization** during recovery → completely
different wallet, looks empty.
## See also
- [hd/SKILL.md](../hd/SKILL.md)
- [entropy/SKILL.md](../entropy/SKILL.md)
- [../../hardware/seedsigner/SKILL.md](../../hardware/seedsigner/SKILL.md)
- [../../hardware/coldcard/SKILL.md](../../hardware/coldcard/SKILL.md)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.