Casa primary-source snapshot

Fetched: 2026-05-01 UTC

1) Official homepage

Source: https://casa.io/

Selected signals from the homepage fetch:

Secure Storage for Bitcoin and Stablecoins

Additional signals from the source:

  • The current homepage title emphasizes bitcoin and stablecoins rather than only Bitcoin multisig, which is useful because the docs corpus still frames the company more broadly around the Bitcoin and Ethereum ecosystems
  • The readability extraction surfaced member testimonials more than technical detail, so the homepage was less useful than the docs set for recovering the real operating model

2) Wealth Security Protocol overview

Source: https://docs.casa.io/wealth-security-protocol/

Selected excerpts from the docs:

Casa provides secure storage solutions for digital wealth, namely cryptocurrency in the Bitcoin and Ethereum ecosystems.

Our flagship product is the Casa app, a software and expert service system designed to provide the highest level of cryptographic key security and usability.

Risks can be separated into the risk of loss and the risk of theft.

Additional signals from the source:

  • The main docs make Casa look more like a self-custody support system than a simple wallet: the app, operating procedures, and services are all part of the security model
  • The overview explicitly frames the central design problem as balancing loss risk against theft risk, which becomes a recurring categorization clue across the vault and recovery docs

3) 3-Key Vault

Source: https://docs.casa.io/wealth-security-protocol/chosen-key-schemes/2-of-3-basic-multisig.md

Selected excerpts from the docs:

Two keys are needed to sign and send a transaction.

1 key on the client’s mobile phone

1 hardware key kept by the client

1 emergency backup key kept by Casa

Additional signals from the source:

  • The 3-key vault page shows that Casa is not merely describing multisig in the abstract; it is shipping a concrete operational package that bundles assisted recovery, mobile-key backup, device health checks, and the Casa mobile app
  • The page also says no private keys are stored on Casa servers, which matters for distinguishing Casa from a custodian

4) 5-Key Vault

Source: https://docs.casa.io/wealth-security-protocol/chosen-key-schemes/3-of-5-key-shield.md

Selected excerpts from the docs:

Casa’s flagship premium key management scheme is the 5-key vault.

1 hardware key kept at home

1 hardware key at a separate location, such as an office

1 hardware key kept in a third location, such as a safety deposit box

1 emergency backup key kept by Casa

Additional signals from the source:

  • The 5-key vault page is a strong categorization signal because it makes multi-location key distribution, recovery support, and advisor help part of the product itself
  • It also explicitly mentions inheritance planning, emergency lockdown, and sovereign recovery instructions, which makes Casa look like survivability and operational-security infrastructure rather than only a multisig wallet UI

5) Emergency recovery and identity verification

Sources:

Selected excerpts from the docs:

Casa holds one of the signing keys in the user’s multisig setup for use only in emergency recovery scenarios.

Casa will only use the Recovery Key after a client has verified private data that they provided to us during setup.

the process includes a significant signing delay and a series of regular user notifications when a recovery request is made.

Additional signals from the source:

  • These pages are the clearest proof that Casa is structured as a collaborative recovery architecture rather than as a fully sovereign DIY wallet or as a full custodian
  • The delayed-signing and notification workflow is especially important because it reveals a designed operational control around recovery requests, not just a legal promise

6) Seedless hardware wallets and sovereign recovery

Sources:

Selected excerpts from the docs:

We decided not to rely on manually backed up recovery seeds.

All Casa balances can be recovered and accessed using widely available open-source software.

They are never dependent on Casa or Casa tools to access their assets.

Additional signals from the source:

  • Casa’s product stance is unusual because it treats key replacement and guided recovery as the default operating model rather than assuming users should manually preserve every seed phrase forever
  • The sovereign-recovery page is equally important because it limits how far the product can drift toward custodial dependence: Casa says users can always exit via open-source tools

Notes

  • Casa appears best cataloged as bitcoin-and-ethereum self-custody support platform / collaborative multisig recovery architecture / wealth-security service layer.
  • No canonical standalone whitepaper or litepaper surfaced in this pass.
  • The most useful primary sources were the Wealth Security Protocol docs, especially the vault-design and recovery pages, not the public homepage alone.