Unchained

• Name: Unchained
• URL: https://www.unchained.com/
• Category: bitcoin collaborative-custody product stack / treasury-and-inheritance workflow surface / direct-to-vault settlement product
• Tags: bitcoin-ecosystem
• Summary: Unchained remains useful at the project layer because there is a real product surface here: collaborative multisig vaults, business-vault permissions, direct-to-vault trading, bitcoin-backed loans, IRA packaging, and inheritance workflow. Keep this note on that user-facing stack. The broader operator and legal boundary that decides how the backup-key role, servicing, settlement, and wrapper workflow actually run now lives in unchained.
• What it does:
  • Offers 2-of-3 multisig vaults in which clients hold two keys and Unchained holds one backup key, for both individuals and businesses
  • Provides business-vault permissions, auditor visibility, approval-policy workflow, and key-rotation support around the same collaborative-custody base
  • Provides trading that settles bitcoin directly into cold-storage vaults rather than requiring exchange withdrawal flows
  • Offers bitcoin-backed commercial loans where customer collateral remains in multisig and can be verified on-chain with a key the borrower controls
  • Offers Bitcoin IRA products where customers hold real bitcoin in multisig cold storage while keeping tax-advantaged retirement-account structure
  • Provides inheritance planning, executor guidance, beneficiary structures, trust-oriented custody setups, and family/heir coordination tools
• Key claims:
  • The homepage defines Unchained as a place to buy, protect, borrow against, and retire with bitcoin while holding your own keys the whole time, which captures the breadth of the product stack better than a plain vault label
  • The vaults page says collaborative custody is meant to remove single points of failure while preserving user control, with two of three keys required to spend and Unchained unable to move funds unilaterally
  • The business-vaults page shows that the product is not just a consumer wallet shell: it includes treasury governance, team permissions, auditor roles, and organization-specific rotation workflow
  • The trading-desk page is useful because it shows Unchained packaging custody and purchase settlement together, with bitcoin landing directly into the vault product rather than passing through a generic exchange withdrawal path
  • The loans page emphasizes zero rehypothecation and on-chain verification using a customer-controlled key, which is a meaningful architectural distinction inside the product surface
  • The Bitcoin IRA and inheritance pages show Unchained extending the same collaborative-custody product model into retirement and estate workflow rather than treating those as unrelated adjunct services
• Whitepaper: No canonical Unchained whitepaper or litepaper surfaced in this pass. The clearest current sources of truth are the official site and focused product pages for vaults, business custody, trading, loans, IRAs, and inheritance; see ../whitepapers/unchained-primary-sources-2026-04-28.md.
• Sources:
  • https://www.unchained.com/
  • https://www.unchained.com/vaults
  • https://www.unchained.com/business-vaults
  • https://www.unchained.com/trading-desk
  • https://www.unchained.com/loans
  • https://www.unchained.com/bitcoin-ira
  • https://www.unchained.com/inheritance

Internal linkages

• Company / operator boundary for the backup-key role, servicing workflow, settlement policy, and wrapper administration: unchained.
• Strongest collaborative-custody peers: casa and bitkey.
• Institutional operator-stack contrast: fireblocks.

Protocol / company boundary

• Keep this note on the product shell: vault structure, business permissions, direct-to-vault settlement, loan packaging, IRA workflow, and inheritance features.
• Use unchained for the named-entity layer around backup-key policy, support and identity workflow, loan servicing, IRA and legal wrapper administration, and the broader who actually runs this relationship? question.
• That split matters because what does the product expose? and which company controls the recovery, servicing, and wrapper lane? are related but not identical questions.

Control surface

• At the product layer, leverage sits in vault configuration, approval and role design, settlement routing into custody, collateral workflow, IRA packaging, and inheritance execution surfaces.

• The broader company control surface still matters, but it now points upward to unchained because the decisive authority is not purely in the multisig script or the app UI.

• Read Unchained as a collaborative-custody product stack, not as a neutral protocol baseline.

• Last reviewed: 2026-08-07 UTC