This review contains affiliate links. If you buy via these links, I may earn a commission at no extra cost to you. It doesn’t change what I say about the product.
I want to be upfront about my experience here: I have not owned a Blockstream Jade as my primary signing device. I spent time with one at a local Bitcoin meetup where a member brought his Jade for a show-and-tell on the air-gap workflow, and I have reviewed the device in depth through Blockstream’s public documentation, the open-source firmware repository at github.com/Blockstream/Jade, the Pinserver paper at github.com/Blockstream/blind_pin_server, and substantial community signal from Bitcoiners who use it as a primary or secondary signing device. Where I’m working from documentation rather than personal ownership, I’ll say so.
That said, the Jade has earned a genuinely interesting place in the hardware wallet conversation, and the Pinserver mechanism is one of the most clever design decisions in recent hardware wallet history. This review will explain why.
TL;DR
Blockstream Jade is the camera-air-gap hardware wallet for Bitcoiners who want fully auditable open-source firmware and no USB required for signing. The price — around $65 at time of writing — is lower than both the Coldcard and Ledger alternatives. The Pinserver mechanism is novel: Jade uses a Blockstream-hosted (or self-hostable) server to simulate the brute-force resistance of a Secure Element, despite not having a dedicated SE chip. This is either elegant engineering or an additional trust dependency, depending on your threat model. Probably both.
What Jade is — and who Blockstream is
Blockstream is a Bitcoin infrastructure company founded in 2014. The company’s chairman is Adam Back, the cryptographer whose hashcash proof-of-work system directly inspired Bitcoin’s mining mechanism, and who is cited in the Bitcoin whitepaper. Blockstream built the Liquid Network — a Bitcoin sidechain for exchange settlements and certain confidential transactions — and has contributed significantly to Bitcoin protocol development, including work on SegWit and the development of the Miniscript policy language.
The Jade hardware wallet was originally designed around Liquid. Blockstream needed a signing device that could handle Liquid’s confidential transactions, and existing hardware wallets lacked the firmware support. The Jade emerged from that internal need and was subsequently released as a general-purpose Bitcoin (and Liquid) signing device for the wider community.
This origin matters for understanding the Jade’s character. It is not a consumer product that started from “how do we make hardware wallets accessible.” It is an infrastructure company’s internal tool that grew into a consumer product. The result is a device that rewards technically engaged users and asks more of newcomers than something like the Ledger Nano or Trezor Model One.
The Jade firmware is open source under the Apache 2.0 license. This is meaningful: every line of code that runs on your Jade is auditable, compilable from source, and verifiable. Blockstream has done deterministic builds — you can build the firmware yourself and verify the hash matches what’s distributed. This is a stronger transparency claim than Ledger’s closed operating system, and comparable to the Coldcard and Trezor in openness.
Hardware: STM32H7, color screen, camera, and two buttons
The Jade is a compact device with a color IPS display — a notable upgrade over the monochrome screens on earlier Coldcard and Trezor devices. The display makes QR code scanning and address verification more comfortable. Colors also allow richer warning UIs and clearer visual feedback during signing.
The main processor is an Espressif ESP32 (specifically the ESP32-S3 in recent hardware revisions), which is a capable dual-core microcontroller with Wi-Fi and Bluetooth hardware on-chip. Blockstream disables the wireless radios in firmware — the Jade is not a wireless device in operation. The presence of disabled wireless capability has attracted some discussion in the security community, though Blockstream’s firmware disablement is verified by the open source code.
Physical input is via two buttons (left and right) and a navigation “jog wheel” for scrolling and selection. This is more ergonomic than the Coldcard’s numeric-keypad-only input for menu navigation, and less polished than the Trezor Safe 5’s touchscreen. The Jade is a middle ground: functional, not luxurious.
The key hardware differentiators are:
Camera: The Jade has a front-facing camera used for reading QR codes. This enables the air-gap signing workflow without any physical media — you hold a QR code up to the Jade, it reads the PSBT, and produces a signed transaction QR code in return. No USB cable. No microSD card swap. Just QR codes. This is the cleanest camera-based air-gap implementation available at this price point.
microSD slot: For users who prefer file-based workflows, the Jade also has a microSD card slot. You can transfer PSBTs and signed transactions via card, similar to the Coldcard workflow. Both channels — QR and microSD — are available on the same device.
USB-C: The Jade charges and connects via USB-C. For users who want a connected workflow (via Jade’s USB connection to Sparrow or Green), this is the cable. For air-gap purists, the USB-C is for charging and firmware updates only.
No Secure Element: This is the critical hardware distinction from the Coldcard. The Jade does not have a dedicated Secure Element chip (like the Microchip ATECC608 or Infineon SLB9670). Secure Elements provide physical tamper resistance and brute-force protection for PIN guessing at the silicon level. Without a Secure Element, an attacker with physical access and the right equipment could theoretically extract the seed from device memory if they could bypass PIN protection. The Jade’s answer to this problem is the Pinserver — which we’ll discuss at length.
The Pinserver: the cleverest thing about Jade
This is the section that makes Jade genuinely interesting rather than just another open-source hardware wallet.
The standard Secure Element solves a specific problem: brute-force PIN protection. On a hardware wallet with a proper SE, after N wrong PIN attempts, the SE destroys the key material. An attacker who steals your hardware wallet cannot sit at a computer and try a million PINs because the hardware enforces a lockout with permanent deletion after too many attempts.
Without a Secure Element, how do you prevent brute-force PIN attacks? You need the PIN verification to require something the attacker doesn’t have — and that something shouldn’t be your seed, because the seed should be recoverable by you with just your backup words.
Blockstream’s answer: the Pinserver, based on the “blind PIN server” cryptographic scheme documented at github.com/Blockstream/blind_pin_server.
Here’s how it works at a conceptual level:
When you set up your Jade and create a PIN, the device does not simply store your seed encrypted with the PIN (which would allow offline brute-force if the encrypted seed was extracted). Instead, the Jade:
- Generates a random “pin secret” locally on the device
- Commits this pin secret to Blockstream’s Pinserver in a blinded way — the server holds part of a key that is required to decrypt the seed, but the server cannot see the seed itself and cannot reconstruct the decryption key alone
- On each PIN attempt, the Jade contacts the Pinserver, which performs its part of the PIN verification computation
- If the PIN is correct, the Jade reconstructs the decryption key from both the local portion and the server response, and decrypts the seed for signing
- After a small number of wrong PIN attempts, the Pinserver refuses further responses for that device, making brute-force impossible — even if someone has the device flash contents
The elegance here is the “blind” part: the Pinserver learns nothing about the seed or the PIN from this interaction. It is a stateless oracle that can say “valid” or “invalid” to a correctly formatted request, without knowing what it’s validating. The brute-force protection lives on the server side — the server can rate-limit and lock out — while the seed never leaves the device in plaintext.
The trust model implication: the Pinserver must be available for you to access your Jade. If Blockstream’s Pinserver goes down, you cannot unlock your Jade via PIN. You can still recover your funds using your BIP-39 seed phrase, because the seed is the underlying key — but you lose the convenient PIN-based access.
Importantly: Blockstream has published the Pinserver software as open source. You can self-host the Pinserver and configure your Jade to use your own instance instead of Blockstream’s. This takes the Blockstream trust dependency off the table, at the cost of running your own server. For users with serious sovereignty concerns, self-hosting the Pinserver is the correct move. For most users, the Blockstream-hosted server is a practical convenience with a clear and understood trust model.
This is more honest than most hardware wallet trust models. Most hardware wallets have some server dependency that is not clearly disclosed. Blockstream has documented and published theirs.
Setup flow: first power-on, seed generation, Pinserver association
I reviewed this flow from documentation and the meetup demonstration, not from personal first-power-on experience.
First power-on: The Jade boots with a welcome screen and prompts you to choose a language. The setup flow is more verbose than a Trezor but less cryptic than a Coldcard — Blockstream has invested in explaining what you’re doing and why.
Seed generation: You can generate a new 12 or 24 word BIP-39 seed on the device. The seed is shown word by word on the Jade’s color screen. You write it down. The Jade then asks you to confirm several words from the seed before proceeding — standard verification practice.
Jade also supports SLIP-39 Shamir Secret Sharing, which allows splitting the seed into shares such that M-of-N shares are required to reconstruct. For example: a 2-of-3 Shamir split means you create three shares, store them in three separate locations, and any two shares are sufficient to recover the seed — but a single compromised share reveals nothing useful to an attacker. This is a meaningful backup strategy improvement over standard single-phrase BIP-39 for users who want geographic distribution of their backup material.
Pinserver association: After seed setup, you set a PIN. The Jade performs the Pinserver handshake described above — it contacts Blockstream’s Pinserver (or your self-hosted instance) to establish the PIN verification relationship. This requires an internet connection during setup. After setup, signing operations do not require the Pinserver unless you are unlocking the PIN; QR-based signing once the device is unlocked requires no network connectivity.
Connected to Blockstream Green: The Jade integrates most naturally with Blockstream’s own Green wallet (for both Bitcoin mainnet and Liquid). Green detects the connected Jade and walks you through wallet creation or restoration. For users who prefer Sparrow or Specter — which I recommend for serious Bitcoin custody — the integration is also excellent.
Air-gap signing via QR codes and microSD PSBT workflow
This is where the Jade earns its recommendation from the air-gap-oriented Bitcoin security community.
QR code workflow with Sparrow:
- Import the Jade’s xpub/descriptor into Sparrow by either connecting via USB initially (to export the wallet file) or by having Jade display the xpub as a QR code that Sparrow scans via your webcam
- Sparrow creates a watch-only wallet
- To send, construct a transaction in Sparrow and export as a PSBT — Sparrow can display the PSBT as an animated QR code sequence on screen
- Hold the Jade’s camera up to your computer screen; the Jade scans the animated QR, parses the PSBT, and displays the transaction details for your review
- After confirming, the Jade signs and displays the signed transaction as a QR code
- Scan the signed transaction QR with your webcam in Sparrow; Sparrow decodes and broadcasts
No USB cable is involved in the signing flow. No microSD card to swap. Just camera and screen. This is genuinely clean: the air-gap never breaks because there is no physical transfer medium to plug in and out.
The animated QR encoding (Jade uses the BC-UR standard, also adopted by the Passport hardware wallet and supported by Sparrow) handles larger PSBTs by splitting them across multiple frames that cycle on the screen. The Jade and Sparrow can handle multisig PSBTs this way — even complex ones with multiple inputs and outputs — though very large multisig PSBTs may cycle through many frames.
microSD PSBT workflow: For users who prefer file-based transfers (perhaps for larger PSBTs, or for use with Specter Desktop which has strong file-based flows), the microSD slot provides the same experience as the Coldcard workflow: copy PSBT to card, sign on Jade, return signed transaction via card. Both channels are available and interchangeable.
Specter Desktop integration: Specter has dedicated Jade support, recognizes the device by USB for xpub export, and can handle PSBT signing via QR for air-gap use.
Greenlight Lightning: optional, hosted, honest about its tradeoffs
Jade offers integration with Greenlight, Blockstream’s hosted Lightning service. Greenlight is an interesting architecture: rather than running a full Lightning node yourself, Greenlight manages the node software on Blockstream’s infrastructure, while your Jade holds the keys. The node runs in the cloud; the keys stay on hardware you control.
This is meaningfully better than a fully custodial Lightning wallet like Wallet of Satoshi (where the service holds your keys and can spend your funds unilaterally). With Greenlight, only you can authorize payments because only your Jade can sign. Blockstream cannot steal your Lightning funds — they can only refuse to run the node.
That said: you are not running your own Lightning node. Blockstream is. The node’s channel relationships, routing, and uptime are Blockstream’s responsibility and under Blockstream’s operational control. If Blockstream’s Greenlight infrastructure goes down, your Lightning wallet is unavailable. If Blockstream decides to discontinue Greenlight, you need to migrate.
For users who want the absolute sovereign experience — running their own node, controlling their own channels — Greenlight is not that. It is a practical middle ground: self-custodial keys with hosted infrastructure. For someone who wants Lightning on their Jade without running an always-on server, Greenlight is a reasonable choice with eyes open.
I personally would use Phoenix Wallet for mobile Lightning and use the Jade purely for on-chain cold storage signing. Phoenix offers a comparable “you hold keys, ACINQ handles the node” model with a more polished mobile UX. But Greenlight is a legitimate option if you specifically want Lightning integrated with your Jade workflow.
Multisig UX: one of the best in the market
The Jade is, alongside the Coldcard, one of the most capable multisig signing devices available. It handles the full multisig PSBT workflow correctly and integrates with both Sparrow and Specter for coordinator roles.
For a 2-of-3 multisig setup — a common cold storage configuration — the workflow looks like:
- Each of three signing devices (say, a Jade, a Coldcard, and a Trezor) exports its xpub and derivation path
- Sparrow or Specter creates a multisig wallet descriptor from all three xpubs, defining the spending policy
- The wallet descriptor is registered on each signing device so each device understands the full policy and can verify output addresses
- Signing a transaction requires two of the three devices to sign the PSBT in sequence
The Jade’s color screen makes multisig transaction review more readable than the Coldcard’s monochrome display — you can see the full output address, the amounts, and the fee clearly in color, reducing the cognitive load of address verification.
The QR air-gap workflow is particularly suited to multisig: each signing device can receive the PSBT via QR, add its signature, and display the updated PSBT as a QR for the next device in sequence or for the coordinator to broadcast. No shared cables, no shared hardware adapters. Each device in a geographically distributed multisig can sign via QR independently.
For users building collaborative custody arrangements — where different family members or trusted parties hold different signing devices at different locations — the Jade’s camera air-gap is a genuine workflow improvement over microSD-only devices.
Blockstream Jade vs. the alternatives
vs. Coldcard Mk4: The Coldcard Mk4 is the Bitcoin-only purist benchmark. It has dual Secure Elements, Bitcoin-only firmware, a mature PSBT workflow, and the deepest community trust in the serious Bitcoin custody community. The Coldcard wins on Secure Element hardware security and Bitcoin-only attack surface. The Jade wins on price (~$65 vs ~$158), color screen, and the camera QR air-gap (which is cleaner than microSD-only workflows for many users). The Pinserver model is a meaningful engineering difference: Coldcard’s dual-SE approach is verifiable hardware security; Jade’s Pinserver is clever cryptography with a server dependency. Both devices support BIP-39. Coldcard adds BIP-85 and a duress PIN that Jade does not currently match.
vs. Ledger Nano X: The Ledger Nano X has a genuine Secure Element, Bluetooth mobile connectivity, and polished consumer UX. Ledger’s firmware is closed-source, which is a meaningful transparency deficit. The Jade wins decisively on open-source auditability. The Ledger wins on consumer onboarding and mobile Bluetooth workflow. For a Bitcoin-focused user who values open-source firmware, Jade is a better choice than Ledger at lower cost.
vs. Trezor Safe 5: The Trezor Safe 5 has a Secure Element, a touchscreen, and open-source firmware — a strong combination. Trezor supports Shamir backup (SLIP-39), as does the Jade. Both have open-source firmware under permissive licenses. The Trezor’s touchscreen UX is more polished for consumer use; the Jade’s camera air-gap is a distinctive workflow advantage. Trezor costs more. For the multisig air-gap user specifically, Jade competes seriously with Trezor; for the general user, Trezor’s touchscreen UX is easier to live with daily.
Who it’s for — and who it’s not for
Buy the Jade if:
You want a camera-based QR air-gap workflow — no USB cables for signing, no microSD cards to swap, just QR codes between your Jade and a screen. This is the Jade’s most distinctive capability and it makes the air-gap workflow more practical for many users.
You care about open-source firmware and the $65 price point is meaningful. At roughly half the price of a Coldcard or Trezor Safe 5, the Jade is the most accessible open-source hardware wallet available. For someone building a multisig setup with three devices, the cost savings compound.
You’re comfortable with the Pinserver trust model. If you understand that the Pinserver is Blockstream-hosted (or self-hostable), that it provides brute-force protection without a Secure Element, and that your BIP-39 seed is always your ultimate recovery mechanism, the trust model is well-understood and publicly documented.
You want Liquid sidechain support. If you use Liquid for exchange settlements or access to Liquid Bitcoin, the Jade has the best Liquid support of any consumer hardware wallet, which is unsurprising given its origin.
Don’t buy the Jade if:
You want a device with zero server dependency for PIN unlocking. The Pinserver requirement — even with the self-hosting option — is architecturally different from a true Secure Element that does everything locally. For users in adversarial environments where Blockstream’s servers might be inaccessible or where the server relationship is a concern, a Coldcard with dual SE hardware is the more appropriate choice.
You’re a complete beginner. The Jade setup is more technical than a Ledger Nano or Trezor, and the concepts involved — Pinserver, air-gap workflow, PSBT management with Sparrow — require some Bitcoin background to navigate. Start with the Trezor Safe 5 if you’re new, and consider graduating to a Jade or Coldcard as you learn.
You hold altcoins as a significant part of your portfolio. The Jade supports Bitcoin and Liquid only. No Ethereum app. No Solana. For a Bitcoin-only holder, this is a feature. For a diversified holder, it’s a limitation.
Verdict
The Blockstream Jade earns its 4.4 rating as the open-source, camera-air-gap option in the hardware wallet market. At ~$65, it offers more of what serious Bitcoin users care about — auditable open-source firmware, genuine air-gap signing capability, solid multisig support — than any competing device at the price. The QR camera workflow is genuinely elegant and represents a real usability improvement over microSD-only air-gap designs.
The 0.6 deduction reflects the Pinserver trust dependency and the absence of a dedicated Secure Element. These are real constraints that matter for specific threat models. An attacker with physical device access and the right tooling could theoretically extract seed material if the Pinserver lockout is defeated — a scenario the Coldcard’s dual Secure Elements handle more robustly at the hardware level. For most users, the Pinserver model is sufficient and well-documented. For the most security-sensitive use cases, the Coldcard’s hardware design provides stronger guarantees.
“Don’t trust, verify” applies here too. Jade lets you verify everything — the firmware is open, the Pinserver is published, and the cryptographic scheme is documented. You can audit it. That’s meaningful, and it’s a reason to take the Jade seriously.
Sources:
- Blockstream Jade product page: blockstream.com/jade
- Jade firmware source (Apache 2.0): github.com/Blockstream/Jade
- Blockstream Blind Pinserver paper and code: github.com/Blockstream/blind_pin_server
- Greenlight hosted Lightning documentation: blockstream.com/lightning
- BC-UR animated QR standard: github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-005-ur.md
- SLIP-39 Shamir backup specification: github.com/satoshilabs/slips/blob/master/slip-0039.md
- Sparrow Wallet: sparrowwallet.com
- Specter Desktop: specter.solutions