Cowrie Research

unchained

4 min read

Unchained

  • Name: Unchained
  • Legal name: Unchained Capital, Inc.
  • URL: https://www.unchained.com/
  • Category: collaborative bitcoin custody operator / financial-services company / recovery-and-settlement workflow control layer
  • Tags: bitcoin-ecosystem
  • Summary: Unchained belongs as an entity note because the useful question is not only how a 2-of-3 vault works. The practical control surface sits with the named company that runs the backup-key role, identity and support workflow, trading-desk settlement path, loan-servicing boundary, IRA wrapper and partner choreography, and inheritance execution playbooks around that vault model.
  • What it does:
    • Operates collaborative-custody Bitcoin vaults where clients hold two keys and Unchained holds one backup key that cannot move funds alone but remains part of the live recovery and continuity model
    • Packages business treasury governance features such as role-based approvals, auditor visibility, and key-rotation workflow inside the same company-run operating shell
    • Runs a trading desk that settles purchased bitcoin directly into Unchained vaults instead of making customers withdraw from a separate exchange workflow
    • Offers bitcoin-backed commercial loans whose collateral remains inside the collaborative-custody structure, with servicing and rehypothecation claims mediated by the Unchained operating model
    • Extends the same custody pattern into Bitcoin IRA and inheritance products, turning tax wrapper administration, legal-title workflow, beneficiary execution, and expert guidance into part of the real control surface
    • Sells premium advisory and white-glove service tiers, which matters because support, review, and human process are not just marketing decoration here; they are part of the security architecture Unchained is explicitly selling
  • Key claims:
    • The homepage describes Unchained as providing bitcoin financial services so users can buy, protect, borrow against, and retire with bitcoin while holding your own keys the whole time, which is a company-shell framing rather than a narrow wallet or vault label
    • The homepage’s structured data lists the legal name as Unchained Capital, Inc., which is a useful reminder that the real boundary here is a named operating entity rather than an abstract multisig pattern
    • The vaults page says Unchained holds only one key and cannot move bitcoin unilaterally, but that does not make the company irrelevant; it still controls the backup-key role, support workflow, and the conditions under which recovery help is actually available
    • The business-vaults page shows Unchained acting as treasury-governance middleware with granular permissions, auditor roles, and key-rotation support, which is much closer to an operator workflow boundary than to a static wallet SKU
    • The trading-desk materials make clear that Unchained uses the custody relationship to package direct-to-vault settlement, so the company boundary matters for routing, settlement, and where users end up holding assets after purchase
    • The commercial-loans page emphasizes zero rehypothecation and on-chain verifiability with a company-controlled service wrapper around collateral, which is exactly the kind of custody-and-finance operating claim that belongs in an entity note
    • The IRA and inheritance pages show Unchained extending the same company-run shell into retirement-account administration, executor guidance, beneficiary workflow, and legal-title coordination rather than stopping at pure wallet software
  • Whitepaper: No standalone Unchained whitepaper is the important artifact here. The clearest primary materials are the official site and focused product pages for vaults, business custody, trading, loans, IRA, and inheritance; see ../whitepapers/unchained-primary-sources-2026-04-28.md.
  • Sources:

Internal linkages

  • Project-layer product note: unchained.
  • Strongest collaborative-custody comparisons: casa and bitgo.
  • Useful institutional contrast once collateral, servicing, and wrapper workflow matter more than household recovery posture: anchorage-digital.

Protocol / company boundary

  • There is no especially useful neutral Unchained protocol boundary doing the main analytical work.
  • The meaningful split is between the user-facing collaborative-custody product surface in unchained and the broader Unchained company shell that controls the backup-key role, human support lane, settlement routing, lending and IRA wrappers, and inheritance execution choreography.
  • That is why Unchained belongs in companies/: practical authority sits in an operating entity and its workflow promises, not just in the multisig script template.

Control surface

  • Practical authority sits in backup-key policy, account and identity workflow, support escalation, direct-to-vault settlement routing, loan-servicing choreography, IRA wrapper administration, inheritance playbooks, and the premium advisory process that shapes how customers actually use the stack.

  • The company cannot usually spend customer bitcoin alone, but that is not the right test. If a named entity still governs recovery help, product access, servicing workflow, and the finance wrappers around custody, the entity boundary is part of the live security model.

  • Treat Unchained as a collaborative-custody operating company first. The vault structure matters, but the company-run workflow around it is where most practical leverage lives.

  • Last reviewed: 2026-08-07 UTC

Graph View

Backlinks