Shift Crypto

• Name: Shift Crypto
• URL: https://bitbox.swiss/imprint/
• Category: bitcoin hardware-wallet company / signer-firmware vendor / companion-wallet operator / self-custody release-and-support boundary
• Tags: bitcoin-ecosystem
• Summary: Shift Crypto belongs as an entity note, not primarily as a protocol note. The useful question is who designs and manufactures the BitBox line, signs and ships firmware and BitBoxApp releases, operates the docs and support path, and packages the buy / sell / swap / insurance surfaces users encounter inside the app. The practical leverage sits with the company-run signer lifecycle: hardware design, manufacturing trust, firmware provenance, companion-wallet defaults, recovery guidance, and the distribution shell around the BitBox stack.
• What it does:
  • Builds and sells the BitBox hardware-wallet line, with Shift Crypto’s own imprint page describing BitBox as a privately held Zurich-based company product shell rather than a detached open-source project
  • Ships BitBoxApp as the official companion application across desktop and mobile, covering setup, account management, transaction handling, buy/sell flows, swap access, optional insurance packaging, own-node connectivity, and Tor support
  • Publishes the firmware, app, bridge, and client-library repositories that define how first-party and third-party integrations actually reach the signer
  • Operates the support and documentation surface that teaches users backup, recovery, wallet compatibility, and device-use workflow
  • Packages Swiss design/manufacturing, open-source auditability, and microSD-centered backup as part of one company-controlled trust story instead of leaving those as unrelated product facts
• Key claims:
  • The BitBox imprint says “BitBox (Shift Crypto AG) is a privately-held company based in Zurich, Switzerland” and explicitly says Shift Crypto does not provide custodial services, which is the clearest first-party statement that the relevant entity boundary is the company around the self-custody stack
  • The homepage says BitBox devices are designed and manufactured in Switzerland, presents the BitBoxApp as “the center of the BitBox ecosystem,” and says firmware plus BitBoxApp are fully open source
  • The BitBoxApp page shows Shift Crypto is not only shipping a hardware signer: the first-party app also packages buy, sell, swap, optional bitcoin insurance, full-node connectivity, Tor routing, and compatibility with third-party wallets such as Electrum, Specter, Sparrow, and MyEtherWallet
  • The developer-resources page says the BitBox02 integrates with browser applications via WebHID or BitBoxBridge and with third-party bitcoin wallets through HWI, which means the company controls a reusable integration surface, not only a consumer device SKU
  • The firmware repository says the BitBox02 is meant to be used primarily with BitBoxApp, documents encrypted protobuf communication using Noise with out-of-band authentication, and publishes schematics, bill of materials, and x-ray files
  • The BitBoxApp repository shows a multi-layer company-run stack spanning React UI, Go backend, Qt desktop shell, Android target, simulator tooling, and configurable backend / full-node connections rather than a thin firmware updater
• Whitepaper: No canonical standalone Shift Crypto whitepaper surfaced in this pass. The strongest primary materials remain the BitBox imprint, product and app pages, developer resources, and the public GitHub repositories already captured in ../whitepapers/bitbox-shift-crypto-primary-sources-2026-05-01.md.
• Sources:
  • https://bitbox.swiss/imprint/
  • https://bitbox.swiss/
  • https://bitbox.swiss/app/
  • https://bitbox.swiss/dev/
  • https://github.com/BitBoxSwiss
  • https://github.com/BitBoxSwiss/bitbox02-firmware
  • https://github.com/BitBoxSwiss/bitbox-wallet-app

Internal linkages

• Project-layer product note: bitbox-shift-crypto.
• Keep the strongest adjacent hardware-self-custody company set on coinkite, foundation-devices, and ledger.
• Reusable lens: hardware-wallet notes often need a separate company cut because release provenance, manufacturing trust, docs/support workflow, and companion-app defaults usually sit with one named operator.

Control surface

• Practical authority sits in hardware design and manufacturing choices, firmware release and signing workflow, BitBoxApp defaults, partner packaging inside the app, backup and recovery guidance, and the support/documentation path users lean on when something goes wrong.

• Even in a self-custodial product, the company still shapes the trust pipeline: which first-party app path feels normal, which integrations are maintained, how updates reach users, and how recovery or privacy practices are explained.

• Treat Shift Crypto as the named operator boundary above BitBox: the important question is not just what can the device do? but who controls the signer lifecycle and software-distribution shell around it?

• Last reviewed: 2026-08-07 UTC