Cypherock

• Name: Cypherock
• URL: https://www.cypherock.com/
• Category: bitcoin hardware-wallet company / signer-firmware vendor / recovery-architecture operator / self-custody release-and-support boundary
• Tags: bitcoin-ecosystem
• Summary: Cypherock belongs as an entity note, not primarily as a protocol note. The useful question is who designs and ships the vault-plus-card hardware set, controls the cySync companion software and firmware release path, chooses how the seedless backup and inheritance story is packaged, and defines the trust split between open vault code and proprietary secure-card components. The practical leverage sits with the company-run signer lifecycle: hardware design, recovery choreography, firmware and desktop-app provenance, docs/support workflow, and the physical-distribution shell around the Cypherock stack.
• What it does:
  • Builds and sells the Cypherock X1 hardware-wallet system, centered on one X1 Vault plus four X1 Cards rather than a single-device or paper-seed backup model
  • Ships cySync as the official desktop companion software for wallet setup, account management, transaction handling, portfolio visibility, firmware coordination, and day-to-day use of the hardware stack
  • Uses Shamir Secret Sharing to split wallet-secret material into five cryptographic parts across the vault and cards so recovery depends on distributed physical components rather than a single written seed phrase
  • Maintains the mixed-trust hardware and software model where vault-side firmware and companion software are open for inspection while the secure-card side remains proprietary and non-upgradeable
  • Operates the support and documentation surface that teaches users how the distributed backup model, loss tolerance, wallet restoration, and inheritance workflow actually work in practice
• Key claims:
  • The homepage markets Cypherock X1 as a seed-phrase-free hardware wallet with non-custodial inheritance, which is the clearest first-party signal that the product is being sold as a company-packaged recovery and continuity system rather than a bare signer device
  • The docs introduction says Cypherock X1 is BIP39 compliant, does not require users to maintain a seed-phrase backup, and is open-source and audited, which keeps the stack inside ordinary wallet rails while framing the recovery model as the main differentiator
  • The open-source-with-secure-elements documentation says Cypherock splits a wallet into five parts across the X1 Vault and four X1 Cards, keeps the X1 Vault code open for review, and keeps the X1 Card code proprietary and non-upgradeable, which makes the operator-controlled trust split explicit
  • The existing primary-source bundle and public GitHub organization show that Cypherock is not only selling hardware: the company also controls cySync, vault firmware publication, security documentation, and the surrounding support materials users rely on to understand recovery and replacement
  • The practical consequence is that users are not only trusting cryptography; they are trusting one named operator to ship the hardware set, publish the software path, explain the recovery ceremony, and preserve the open-versus-proprietary split that underwrites the whole trust story
• Whitepaper: No canonical standalone Cypherock company whitepaper surfaced in this pass. The strongest current primary materials remain the official site, docs around architecture, recovery, and open-source boundaries, plus the public repositories already captured in ../whitepapers/cypherock-primary-sources-2026-04-28.md.
• Sources:
  • https://www.cypherock.com/
  • https://docs.cypherock.com/introduction.md
  • https://docs.cypherock.com/design-decisions/the-balance-between-security-and-convenience.md
  • https://docs.cypherock.com/cypherock-x1-features/open-source-with-secure-elements.md
  • https://docs.cypherock.com/getting-started/how-to-recover-your-crypto-assets-in-the-case-of-loss-or-theft.md
  • https://docs.cypherock.com/security-overview/keylabs-third-party-security-audit
  • https://github.com/Cypherock
  • https://github.com/Cypherock/x1_wallet_firmware
  • https://github.com/Cypherock/cypherock-cysync

Internal linkages

• Project-layer alias: cypherock.
• Keep the strongest adjacent hardware-self-custody company set on foundation-devices, shift-crypto, and satoshilabs.
• Reusable lens: hardware-wallet notes often need a separate company cut because firmware provenance, companion-app defaults, recovery guidance, and manufacturing or device-trust assumptions usually sit with one named operator.

Control surface

• Practical authority sits in hardware design and sourcing, the vault-versus-card trust split, firmware and cySync release workflow, recovery and inheritance guidance, documentation and support quality, and the exact way the company teaches users to distribute and replace the physical components.

• Even in a self-custodial product, the company still shapes the trust pipeline: which software path feels canonical, how replacement and recovery work under stress, what parts stay inspectable, and what proprietary secure-element assumptions users must quietly accept.

• Treat Cypherock as the named operator boundary above the product: the important question is not just how are the shards split? but who controls the signer lifecycle and recovery shell around that split?

• Last reviewed: 2026-08-08 UTC