Blockstream App / Jade

• Name: Blockstream App / Jade
• URL: https://blockstream.com/app/
• Category: bitcoin wallet-control-plane / hardware-wallet infrastructure / self-custody app-and-signer stack / Liquid-and-Lightning access layer
• Tags: bitcoin-ecosystem
• Summary: Blockstream App / Jade is the product-layer wallet-and-signer stack inside a wider Blockstream company shell. The useful part here is the rail-rich companion stack and real signer integration; the broader operator boundary lives one layer up at the company note.
• What it does:
  • Provides a non-custodial Bitcoin wallet across desktop, Android, and iOS under the current Blockstream App brand
  • Presents on-chain Bitcoin, Lightning, and Liquid assets in one wallet surface rather than as separate products
  • Integrates with Blockstream Jade hardware wallets for cold-storage signing while retaining companion-app convenience
  • Exposes privacy and operator features such as own-node connectivity, Tor routing, spending limits, and watch-only access
  • Publishes open-source Jade firmware, desktop/mobile wallet code, and a shared GDK wallet library, with reproducible-build guidance for official Jade firmware verification
• Key claims:
  • The current Blockstream App page says users get “On‑chain Bitcoin, Lightning, and Liquid assets, all at your fingertips in one unified view,” which is the clearest top-level statement that this is a multi-rail Bitcoin wallet stack rather than a narrow on-chain app
  • The same page says “Integration with Blockstream Jade gives you the best of both worlds: cold storage of your private keys combined with the convenience of the Blockstream app,” which is the clearest high-level reason to catalog App + Jade together
  • The app page also says there are “No mandatory documents or personal data” and that users can “Connect to your own node and route traffic through Tor with a single tap,” which makes the privacy and operator posture part of the product surface rather than an obscure advanced setting
  • The Android app repository describes the app as non-custodial and highlights “spending limits, watch-only access for observers, and our unique multisig security model,” which broadens the stack beyond a generic mobile wallet
  • The Jade product page says Jade uses a “Virtual Secure Element” and “blind oracle encryption” so the device can remain “fully open-source while preventing physical key extraction,” which is the central hardware-design claim Blockstream uses to distinguish Jade from secure-element black-box devices
  • The Jade firmware repository documents multiple official device targets (original Jade, Jade 1.1, Jade Plus, and Jade Core), companion-app-based update paths for official devices, and a parallel DIY / emulator path for developers, which makes the firmware repo unusually important as a primary source
  • The Jade reproducible-build guide explicitly says its purpose is to let users “verify the firmware offered by Blockstream is indeed built from the publicly available tagged source code,” which is a strong signal that firmware verification is a first-class part of the operating model
• Whitepaper: No canonical standalone Blockstream App or Jade whitepaper/litepaper surfaced in this pass. The clearest current sources of truth are the official Blockstream App and Jade product pages plus the Jade and Blockstream App repositories; see ../whitepapers/blockstream-app-jade-primary-sources-2026-05-01.md.
• Sources:
  • https://blockstream.com/app/
  • https://blockstream.com/jade/
  • https://github.com/Blockstream/Jade
  • https://github.com/Blockstream/green_qt
  • https://github.com/Blockstream/green_android
  • https://github.com/Blockstream/gdk

Internal linkages

• Broader operator boundary for the release, firmware, and multi-product shell: blockstream.
• Strongest comparison points: coinkite, foundation-devices, and bitkey.

Protocol / company boundary

• Keep this note on the product surface: Jade hardware, companion-app behavior, multi-rail wallet routing, firmware-verification flow, and the app-and-signer stack users directly inherit.
• Use blockstream when the sharper question is who controls the release, support, and broader commercial shell around that stack, including how it is packaged beside Greenlight, Core Lightning, and Liquid-adjacent enterprise products.
• That split matters because how does Blockstream App / Jade behave as a wallet-and-signer stack? and which company controls the provenance and operating shell around it? are related but not identical questions.

Control surface

• Practical authority sits in Jade firmware policy, Blockstream App defaults, Liquid-versus-Lightning-versus-onchain routing, backend and own-node connectivity choices, and how much of the wallet experience still leans on Blockstream-run infrastructure.

• The stack is useful because it combines signer, app, and multi-rail wallet plumbing in one place. That same bundling is also where policy and default power accumulate.

• For the wider company boundary tying this stack to Greenlight, Core Lightning stewardship, and enterprise Liquid tooling, read blockstream.

• Read it as a rail-rich Bitcoin wallet-and-signer stack, not as a generic consumer wallet brand.

• Last reviewed: 2026-08-06 UTC