bitbox-shift-crypto

BitBox

• Name: BitBox
• URL: https://bitbox.swiss/
• Category: hardware-wallet product stack / self-custody app-and-backup surface / developer-integrable signing environment
• Tags: bitcoin-ecosystem
• Summary: BitBox is the product layer: device models, BitBoxApp, backup flow, and third-party integration paths. The named operator boundary around hardware manufacturing, firmware and app release workflow, support, and partner packaging now lives in shift-crypto. Keep this note on the signer, app, and recovery surface users actually handle.
• What it does:
  • Provides BitBox hardware wallets for offline private-key storage and on-device transaction signing
  • Offers multiple device variants including Bitcoin-only and multi-asset editions, plus BitBox02 Nova with Bluetooth support for iPhone and iPad
  • Uses BitBoxApp as the main companion app for setup, transaction handling, account management, and day-to-day wallet use across desktop and mobile
  • Uses a microSD-centered backup and recovery flow, with optional paper or steel recovery-word backup paths
  • Supports integration with browser applications via WebHID or BitBoxBridge and with third-party bitcoin wallets through the Bitcoin Hardware Wallet Interface (HWI)
  • Exposes a broader product environment than a single device SKU: firmware, app, bridge, client libraries, backup tooling, and wallet-compatibility paths
• Key claims:
  • The homepage says BitBox hardware wallets store private keys offline and presents the BitBoxApp as “the center of the BitBox ecosystem,” which is the clearest first-party statement that the product is device-plus-app rather than a bare signer
  • The homepage repeatedly emphasizes instant backup and recovery using the included microSD card, which remains one of the clearest differentiators of the BitBox product surface
  • The homepage says the firmware and BitBoxApp are fully open source and positions Swiss design/manufacturing plus auditability as part of the trust model users encounter at the product layer
  • The developer-resources page says the BitBox02 can integrate with browser applications via WebHID or BitBoxBridge and with third-party bitcoin wallets via HWI, which keeps the product note grounded in real interoperability rather than only companion-app usage
  • The developer-resources page documents the secure chip (ATECC608B), open-source microcontroller firmware, and physical interaction requirements, reinforcing that the product security model depends on local user confirmation rather than remote signing convenience
  • The firmware repository says the device uses encrypted protobuf messages and Noise with out-of-band authentication for USB communication, and publishes schematics, bill of materials, and x-ray files
  • The BitBoxApp page shows the product surface extends into full-node connectivity, Tor routing, and compatibility with Electrum, Specter, Sparrow, and MyEtherWallet
• Whitepaper: No canonical standalone BitBox whitepaper surfaced in this pass. The clearest current sources of truth remain the official site, developer resources, BitBoxApp materials, and the public repositories already captured in ../whitepapers/bitbox-shift-crypto-primary-sources-2026-05-01.md.
• Sources:
  • https://bitbox.swiss/
  • https://bitbox.swiss/dev/
  • https://bitbox.swiss/app/
  • https://github.com/BitBoxSwiss
  • https://github.com/BitBoxSwiss/bitbox02-firmware
  • https://github.com/BitBoxSwiss/bitbox-wallet-app

Internal linkages

• Company / operator boundary above the product stack: shift-crypto.
• Strongest hardware-self-custody comparison points: coinkite, foundation-devices, and bitkey.

Protocol / company boundary

• Keep this note on the product surface: device properties, BitBoxApp behavior, backup and recovery mechanics, full-node and Tor support, and third-party wallet integration paths.
• Use shift-crypto for the named operator layer around manufacturing trust, release workflow, support, docs, and the partner-routing shell inside BitBoxApp.
• That split matters because how does BitBox work for a user or integrator? and who controls the software-distribution and trust pipeline around BitBox? are related but not identical questions.

Control surface

• At the product layer, the leverage sits in firmware provenance, BitBoxApp defaults, backup-and-recovery handling, bridge and WebHID integration paths, and the privacy / interoperability options exposed to users.

• The microSD backup model is the memorable product difference, but the deeper point is still that BitBox is a signer-plus-app-and-recovery stack rather than only a hardware dongle.

• Read it as disciplined Bitcoin self-custody plumbing, not as a new custody theory.

• For the company shell above that product surface, read shift-crypto.

• Last reviewed: 2026-08-07 UTC