Casa

• Name: Casa
• URL: https://casa.io/
• Category: collaborative bitcoin-and-ethereum custody operator / recovery-and-continuity company / support-mediated multisig control layer
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: Casa belongs as an entity note, not a protocol note. The useful question is who controls the assisted-recovery workflow, the Casa-held emergency key role, the identity-verification procedure, the delay-and-notification policy, and the continuity model that sits on top of the nominally self-custodial key scheme.
• What it does:
  • Provides assisted multisig custody tiers built around a phone key, one or more hardware keys, and a Casa-held emergency recovery key
  • Operates private identity-verification, signing-delay, and repeated-notification procedures before Casa participates in an emergency recovery flow
  • Packages the app, support workflow, advisor layer, and continuity playbooks as part of the security architecture rather than as optional front-end decoration
  • Publishes sovereign-recovery instructions so balances can be recovered with broadly available open-source tooling instead of depending forever on Casa software
  • Promotes a seedless-hardware-wallet operating model where device replacement and guided recovery are part of the intended workflow, not an edge-case patch
• Key claims:
  • Casa’s Wealth Security Protocol overview says Casa provides secure storage solutions for digital wealth in the Bitcoin and Ethereum ecosystems and frames the flagship product as a software-and-expert-service system for cryptographic key security and usability
  • The same overview centers the core design tradeoff on minimizing both theft risk and loss risk at once, which is exactly why the company workflow matters more than a bare wallet label
  • The 3-Key Vault docs describe a 2-of-3 setup with one key on the client’s phone, one hardware key, and one Casa emergency backup key, plus assisted recovery and encrypted cloud-backed mobile-key backup
  • The 5-Key Vault docs describe a 3-of-5 setup with one mobile key, three hardware keys in separate locations, and one Casa emergency backup key, plus advisor support, emergency lockdown, and assisted recovery if two keys are lost
  • The emergency-recovery docs say Casa only uses its recovery key after the client verifies setup data, and Casa’s signature still must be combined with enough client signatures to complete a recovery transaction
  • The account-recovery docs say Casa uses a private authentication process with a significant signing delay and repeated user notifications when a recovery request is made
  • The sovereign-recovery docs say balances can be recovered with widely available open-source software, which matters because it makes the company boundary analytically sharp: Casa is part of the normal operating model even if it is not an absolute withdrawal monopoly
  • The homepage currently says Secure Storage for Bitcoin and Stablecoins, while the protocol docs still describe operation across the Bitcoin and Ethereum ecosystems; that scope drift is worth preserving because distribution emphasis and actual control surface are not identical
• Whitepaper: No classic standalone whitepaper is the point here. The clearest primary materials remain Casa’s Wealth Security Protocol documentation, chosen-key-scheme pages, and recovery / identity-verification docs; see ../whitepapers/casa-primary-sources-2026-05-01.md.
• Sources:
  • https://casa.io/
  • https://docs.casa.io/wealth-security-protocol/
  • https://docs.casa.io/wealth-security-protocol/chosen-key-schemes/2-of-3-basic-multisig.md
  • https://docs.casa.io/wealth-security-protocol/chosen-key-schemes/3-of-5-key-shield.md
  • https://docs.casa.io/wealth-security-protocol/chosen-features/emergency-recovery-key.md
  • https://docs.casa.io/wealth-security-protocol/chosen-features/identity-verification-for-account-recovery.md
  • https://docs.casa.io/wealth-security-protocol/chosen-features/seedless-hardware-wallets.md
  • https://docs.casa.io/wealth-security-protocol/chosen-features/sovereign-recovery-instructions.md

Internal linkages

• Legacy project-layer alias preserved for old links: casa.
• Keep the comparison set on the clearest collaborative-custody and recovery peers: bitkey and unchained.
• Useful contrast where more authority remains inside institutional operator workflow rather than assisted household self-custody: anchorage-digital and bitgo.
• Reusable lens: Casa matters when a product calls itself self-custody while keeping real leverage in recovery ceremony, identity checks, support mediation, and continuity defaults.

Control surface

• Practical authority sits in Casa-held emergency-recovery permissions, the identity-verification procedure, recovery delays, repeated-notification policy, support workflow, encrypted backup defaults, and the operational playbooks that shape how users actually replace devices or recover from key loss.

• The company cannot usually move funds alone, but that is not the right test. If Casa still governs the trusted recovery lane, continuity choreography, and emergency co-signing conditions, the entity boundary is part of the live security model.

• Treat Casa as a collaborative-custody operator first. The app is only the most visible surface of the company-run recovery and continuity stack.

• Last reviewed: 2026-08-05 UTC