Cowrie Research

foundation-devices

3 min read

Foundation Devices

  • Name: Foundation Devices
  • URL: https://foundation.xyz/
  • Category: bitcoin hardware-wallet company / signer-firmware vendor / companion-wallet operator / self-custody supply-chain and release-trust boundary
  • Tags: bitcoin-ecosystem
  • Summary: Foundation Devices belongs as an entity note, not primarily as a protocol note. The useful question is who designs the Passport hardware line, signs and ships firmware releases, operates the Envoy companion-wallet stack, controls onboarding and update defaults, and defines the supply-chain and recovery posture users inherit. The practical leverage sits with the company-run signer lifecycle: hardware design choices, firmware provenance, manufacturing and tamper-check workflow, mobile companion defaults, and the release process that determines what self-custody users are actually trusting.
  • What it does:
    • Builds the Passport hardware-wallet line for offline Bitcoin signing, with camera- and microSD-based airgapped transaction transfer instead of normal USB-data or Bluetooth-wallet workflow
    • Ships Envoy as the mobile wallet and Passport companion app used for setup, account management, firmware updates, backup workflow, transaction coordination, Tor connectivity, and own-node connectivity
    • Publishes Passport firmware, Passport hardware design files, Envoy, and related libraries through its public GitHub organization, which makes the company unusually inspectable compared with more closed wallet vendors
    • Documents supply-chain verification, tamper-check guidance, reproducible-source expectations, and device recovery flows as part of the product lifecycle rather than leaving them implicit
    • Maintains the release, documentation, and product-distribution surface that decides how users actually encounter firmware upgrades, wallet connectivity, and recovery posture in practice
  • Key claims:
    • The Passport Core product page says the device has no direct connection with the outside world and instead uses a camera and QR codes for communication, which is the clearest first-party statement of the signing-isolation model
    • Foundation’s product and docs pages say Passport software and hardware are fully open source, and the public repositories include firmware, hardware design files, and Envoy rather than only marketing-site snippets
    • The Envoy materials position Envoy as both a Bitcoin wallet and the main Passport companion app, including onboarding, firmware updates, Tor, own-node connectivity, and backup-related workflow
    • The Passport firmware repository highlights a secure bootloader / firmware split and reproducible-build guidance, which makes release provenance and signer-update trust an explicit company-controlled surface
    • The Passport hardware repository publishes PCB, enclosure, and bill-of-materials files, which makes Foundation’s supply-chain and device-integrity story materially more concrete than a typical hardware-wallet vendor note
  • Whitepaper: No canonical company whitepaper surfaced in this pass. The strongest primary materials remain Foundation’s official site, Passport and Envoy docs, and the public firmware / hardware / app repositories already captured in ../whitepapers/foundation-devices-primary-sources-2026-05-01.md.
  • Sources:

Internal linkages

  • Project-layer alias: foundation-devices.
  • Keep the strongest product/operator comparison set on adjacent custody-device stacks: bitkey, coinkite, and casa.
  • Reusable lens: hardware-wallet notes often need a separate company cut because firmware signing, manufacturing trust, app defaults, and recovery workflow usually sit with one named operator.

Control surface

  • Practical authority sits in hardware design decisions, firmware release and signing workflow, build provenance, tamper-check procedure, onboarding flow, backup guidance, and the Envoy companion defaults that mediate day-to-day wallet use.

  • Even when the device is airgapped, users still depend on Foundation for the companion-app path, firmware-distribution channel, supply-chain assurances, and the documentation that shapes recovery and own-node practice.

  • Treat Foundation Devices as a self-custody operator boundary: the important question is not just what does Passport do? but who controls the signer lifecycle and trust pipeline around Passport and Envoy?

  • Last reviewed: 2026-08-05 UTC

Graph View

Backlinks