Bitkey primary sources — 2026-05-01

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is Bitkey’s development blog plus the public Bitkey repository.

Primary-source snapshots

1) Development blog overview

• URL: https://bitkey.build/
• Key excerpt:
  • The development blog introduces Bitkey as a mobile app, hardware device, and set of recovery tools for simple, secure self-custody.
  • Recent posts foreground recovery, inheritance, privacy, seedless design, and hardware integrity rather than only transaction signing.
  • That editorial surface already hints that Bitkey is a broader operating system for Bitcoin self-custody.

2) Code-release post

• URL: https://bitkey.build/sharing-the-code-behind-bitkey/
• Key excerpt:
  • Block says it published the code for Bitkey’s hardware device, mobile app, server, and hardware electrical designs.
  • The post explains that the goal is to let people audit how Bitkey works and verify that the shipped software matches Bitkey’s claims.
  • It also highlights reproducible-build ambitions and explicit vulnerability-reporting expectations.

3) Public repository overview

• URL: https://github.com/proto-at-block/bitkey
• Key excerpt:
  • The repository contains separate projects for Android, iOS, shared wallet logic, firmware, nodes, server / Wallet Security Module, and infrastructure.
  • The repo says the source is available for auditing purposes and points readers to verifiable-build guidance for the Android app.
  • This makes Bitkey look materially broader than a simple hardware-wallet firmware repo.

4) “What do you mean, ‘There’s no seed phrase’?”

• URL: https://bitkey.build/what-do-you-mean-theres-no-seed-phrase/
• Key excerpt:
  • Bitkey says its model uses three keys, none of which can move money alone, and requires two keys for spending.
  • The post describes recovery routes for lost phone, lost hardware, loss of both user devices with trusted-contact help, and an emergency path using the two keys the user controls.
  • That framing is useful because it reveals Bitkey as a recovery architecture, not just a signer.

5) “Not our keys, not our business”

• URL: https://bitkey.build/not-our-keys-not-our-business/
• Key excerpt:
  • Bitkey says it used Chain Code Delegation to make collaborative multisig private with respect to wallet balance and transaction history in normal operation.
  • The post says UTXO exposure during recovery is temporary and not logged, and it mentions planned server-verifiability work.
  • This is one of the clearest signals that Bitkey is doing novel privacy engineering around collaborative custody.

6) “Hardware wallets are not enough”

• URL: https://bitkey.build/hardware-wallets-are-not-enough/
• Key excerpt:
  • Bitkey explicitly argues that hardware signers solve only part of the self-custody problem.
  • The post says real self-custody must also solve for loss, theft, coercion, inheritance, and real-life survivability.
  • That is a strong primary-source cue to catalog Bitkey as a full custody-and-recovery system instead of a simple hardware wallet.

Working conclusion

Bitkey is best cataloged as collaborative Bitcoin self-custody infrastructure with recovery, privacy, and inheritance as first-class product layers. The strongest evidence is the combination of hardware, app, server-assisted recovery, open code / schematics, and repeated primary-source emphasis on survivability rather than only secure signing.