sparrow-wallet.app Independent guide Buy bitcoin to self-custody

Hardware signing · reviewed 2026-08-10

Sparrow Wallet hardware wallet support, device by device

Sparrow is designed to be the desktop half of a cold storage setup. It builds the transaction, watches the blockchain and holds nothing secret; a separate device holds the key and performs the signature. This page covers which devices that actually works with, the three ways the data gets between them, and how to decide whether you want a cable in the picture at all.

Buy bitcoin to move into cold storage

  • USB connected signing
  • SD card PSBT files
  • Animated QR signing
  • NFC smartcards

The short version: if your device is one that Bitcoin people already recommend, it works. Sparrow's own feature list claims support for all common hardware wallets in both USB and airgapped modes, and in practice the awkward cases are narrow and predictable rather than mysterious — Ledger multisig registration, message signing on taproot addresses, and smartcards that were never designed to be multisig co-signers.

Unofficial

Compatibility matrix

Every device Sparrow documents

Read the table left to right as a description of how the device talks to Sparrow, not as a quality ranking. USB means the device plugs into your computer and Sparrow drives it over a connected session. Airgap names the transfer method the device supports when it never connects to the computer at all — no cable, no pairing, no driver, only files on an SD card or codes on a screen. Multisig is whether the device works comfortably as one signer in a shared quorum, and Taproot covers taproot addresses and spending. A cell that shows a word instead of a tick means "yes, by this specific mechanism".

Device support as documented by the Sparrow project. "Airgap" lists the transfer method, not a yes/no.
Signing deviceUSBAirgapMultisigTaproot
Coldcard (Mk4, Q)SD card, QR (Q)
Trezor Safe 3 / Safe 5 / Safe 7
Trezor Model T / Onepartial
Ledger Nano S+ / X / Gen5partial
Blockstream JadeQR codes
BitBox02
Foundation PassportQR codes, SD card
KeystoneQR codes
SeedSignerQR codes
Keycard / Keycard ShellNFC readersmartcardpartial
Tapsigner / SatscardNFC readersmartcardpartial
Cobo Vault (deprecated)QR codespartial

12 / 12 devices shown

Source: sparrowwallet.com — FAQ, hardware wallet support

The real decision

USB or airgapped, and how to choose between them

Both modes keep your private key inside the signing device. Neither one hands the key to your laptop. What differs is the number of ways a compromised computer can interact with that device, and how much of the interaction you can see.

What a USB connection actually is

A cable is a two-way data path. Your computer speaks a protocol to the device, asks it for public keys, sends it a transaction to sign, and receives the signature back. That path is exactly what makes the experience pleasant — Sparrow can discover your accounts, read the extended public key and push a transaction across in one click. It is also a standing channel between an internet-connected machine and the thing holding your keys.

The threat this defends against is straightforward and it defends against it well: even a fully compromised computer cannot extract the key, because the device never sends it. What USB does not remove is everything that happens around the signature. Malware on the host can swap the destination address before you approve, can misreport an amount, or can keep asking for signatures on transactions you did not build. That is why the device screen exists, and why it is not optional.

What airgapping removes

An airgapped device never connects to the computer. Sparrow writes an unsigned transaction to an SD card, or renders it as QR codes on the screen; the device reads it, displays what it is about to sign, produces a signature and sends it back the same way. No driver, no protocol negotiation, no live session. The only thing crossing the gap is transaction data you could print out and read.

That closes an entire class of problem: firmware-level attacks delivered over the wire, vendor software you did not intend to install, a hostile USB controller, or a device that silently accepts a command you never issued. It also makes the boundary auditable. You can look at the SD card and know exactly what left the machine.

When the extra friction is worth it

Airgapped signing is slower. Every spend becomes a small ritual: export, walk the card or the QR stream over, verify on the device, walk the signature back, finalise, broadcast. For a wallet you spend from weekly, that friction is real and it makes people postpone things they should not postpone, like moving coins off an exchange.

So split the decision by how you use the money. A spending wallet with a balance you would be annoyed but not ruined to lose: USB is fine, provided you verify addresses on the device screen. A savings wallet you touch a few times a year, holding an amount that would change your life: airgap it, because the twenty extra minutes a year cost you nothing and the attack surface you remove is the one you cannot inspect. If you are running a 2-of-3 multisig, mixing the two is also reasonable — one signer connected, the others airgapped, so no single compromise path reaches a quorum.

EXPORT Online: Sparrow on your laptop AIR GAP unsigned PSBT → ← signed PSBT Offline: signing device keys stay here Private keys never cross the gap. Only transaction data does.
In airgapped mode only transaction data crosses the gap. The key stays on the offline device permanently, and the online machine never speaks to it directly.

Official setup guides

The project documents each transport separately: connected hardware wallet , airgapped with QR codes , airgapped with SD cards and airgapped smartcard .

The three transports, named precisely

Sparrow's signing support is not one feature with a switch. It is three genuinely different mechanisms, and knowing which one your device uses saves a lot of confused searching.

1. USB, connected signing

Sparrow talks to the device over a connected session in the HWI style — the same hardware-wallet-interface approach most desktop wallets use. It enumerates the device, imports the extended public key (the xpub, a public key from which all your receive addresses derive) and hands over a transaction for signature.

Since release 2.4.0 Sparrow can also perform wallet discovery over USB, so it looks for accounts that already have history instead of making you guess derivation paths.

2. SD card, PSBT files

The device stays offline. Sparrow saves a PSBT — a Partially Signed Bitcoin Transaction, the standard file format for a transaction that is built but not yet signed — onto a microSD card. You carry the card to the signer, approve on its screen, and carry back a file containing the signature.

This is the flow Coldcard was built around, and it is the most boring and inspectable of the three, which in security terms is a compliment.

3. QR fountain codes, UR standard

For devices with a camera and a screen, the PSBT travels as light. Sparrow displays the transaction as an animated stream of QR frames using the UR standard, the device's camera reads them, and the signature comes back the same way.

A fountain code is what makes that practical: a transaction too large for one QR is split into an animated stream of frames, and the reader keeps scanning until it has collected enough of them to reassemble the whole transaction.

Source: sparrowwallet.com — features, signing and QR fountain codes

Device notes that matter in practice

Coldcard

The SD-card-first device. A Coldcard can be set up, used and spent from without ever being plugged into a computer for data: you move PSBT files on a microSD card, and USB is optional rather than assumed. The Q model adds a screen and camera capable of QR transfer. It is also the device with the most mature multisig behaviour, including registering a multisig wallet configuration on the device itself so it can recognise the quorum it belongs to.

If your intent is long-term cold storage and you want the transport to be the airgapped one by default rather than by discipline, this is the straightforward pick.

Trezor

USB only. There is no airgapped mode for a Trezor — it has no camera, no SD slot for PSBTs and no offline transfer path, so it always signs over a cable. The current line is the Safe 3, Safe 5 and Safe 7, with the Safe 7 supported from Sparrow 2.4.0; the older Model T and Model One still work.

On the specific question people search — Trezor taproot and message signing in Sparrow — separate the two halves. Taproot receive addresses and taproot spending are supported, and the newer Safe devices handle taproot cleanly; the older Model One is the one to be careful with. Message signing is a different feature: signing a message with a taproot key requires BIP-322, not the legacy signing scheme that hardware wallets have implemented for years. Whether your device will produce that signature depends on its firmware version, not on Sparrow, and the honest answer is to test it with a zero-value wallet before you rely on it. If a taproot message signature is refused, a segwit or legacy address in the same wallet will usually sign, which is enough for the common case of proving control of an address.

Ledger

USB only, and reliable for single-signature use across the Nano S+, Nano X and the Nano Gen5 added in 2.4.0. Single-sig signing is unremarkable in the good sense: connect, confirm on the device, done.

Multisig is the weak spot, and it is worth being precise about where. A Ledger will not blindly sign for a multisig wallet it does not know about. The wallet policy — the script type, the derivation paths and the full set of co-signer extended public keys — has to be registered on the device first, and then confirmed on the device's small display, which means scrolling through key material you are supposed to actually check. That registration step is where setups stall: a policy that does not match, a keystore imported with the wrong derivation, or a device that has forgotten the registration after an app update. It works, and people run it in production, but it demands more patience than the same setup with a Coldcard or a Jade.

Blockstream Jade

One of the few devices that does both: USB for convenience, and QR code signing when you want the gap. Full multisig and taproot support. That flexibility makes it a sensible first hardware wallet for someone who is not yet sure how paranoid they intend to become, because you can start connected and move to airgapped later without buying anything new.

BitBox02

USB only, no airgapped mode, with full multisig and taproot support. Unfussy, well documented and a good choice for someone who wants a connected device that does not fight them. Treat the absence of an airgap option as a real constraint if you expect to build a cold savings wallet later.

QR-native signers: Passport, Keystone, SeedSigner

These three have no USB data path at all. Foundation Passport signs over QR codes and SD cards, Keystone over QR codes, and SeedSigner — a build-it-yourself device that stores no keys at all between uses — over QR codes. All three handle multisig and taproot, and all three pair naturally with Sparrow's UR-standard fountain code flow.

SeedSigner deserves a specific note: because it is stateless, your seed is loaded each time you use it, which shifts the entire burden onto your backup. That is elegant and also unforgiving.

NFC smartcards: Keycard, Keycard Shell, Tapsigner, Satscard

These are cards, not screens. They are used through an NFC reader connected to your computer, and support for Keycard and Keycard Shell arrived in Sparrow 2.4.0. The trade-off is inherent to the form factor: with no display of its own, a card cannot show you the transaction it is signing, so verification has to happen elsewhere. Treat them as convenient single-signature signers or backup-key holders rather than as general-purpose multisig co-signers, and note that Tapsigner and Satscard in particular are not designed for multisig at all.

Cobo Vault

Deprecated. It appears in Sparrow's documented list for historical reasons and signs over QR codes, but it is not a device to buy today. If you hold one, plan a migration to a current signer rather than treating it as a long-term home for savings.

How to choose, with an actual recommendation

Most comparison pages refuse to commit. Here is a commitment, by use case, on the assumption you are pairing the device with Sparrow rather than the vendor's own app.

If you are buying one device for savings you rarely touch

Buy a Coldcard and run it airgapped over SD card. The transport is the default rather than something you have to remember to do, the multisig behaviour is the most mature of the set, and nothing about the workflow depends on your computer trusting a driver.

First hardware wallet, still learning
Blockstream Jade or BitBox02. Both are forgiving over USB; Jade lets you switch to QR signing later without replacing hardware.
You want an airgap but hate SD cards
Keystone or Foundation Passport. Camera-and-screen signing over QR fountain codes, no cable ever, and both work as multisig co-signers.
You already own a Ledger or Trezor
Keep using it for single-sig. It is a genuinely secure device and swapping is not urgent. Add a second device from a different vendor before you attempt multisig.
Minimum trust in any single manufacturer
A 2-of-3 quorum with three different vendors, ideally including a SeedSigner you built yourself. Then no one company's supply chain is a single point of failure.
Smallest sensible balance for a hardware wallet
Roughly: more than you would carry as cash. Below that, an encrypted software keystore with a tested backup is not unreasonable — see seed and passphrase setup.

What a hardware wallet does not protect you from

A signing device solves exactly one problem: it stops your private key from ever existing on an internet-connected computer. It is remarkably good at that, and it is worth being clear that everything below is still entirely your responsibility.

  • A bad backup. The device is replaceable; the seed is not. Losing or mangling your recovery words destroys the wallet just as thoroughly as a thief would, and this is the failure mode we see most often by a wide margin.
  • An address you did not verify. If malware on your computer swaps the destination address and you approve the transaction without reading the device screen, the hardware wallet has done its job perfectly and your coins are still gone.
  • Coercion. No device protects you from being made to unlock it. That is a problem for geographic distribution, a passphrase you can plausibly withhold, or a multisig quorum whose keys are not all in one building — not for firmware.
  • A tampered device. A signer bought from a marketplace reseller, a third-party seller on a large e-commerce site, or second-hand can arrive with a pre-generated seed or modified firmware. Buy from the manufacturer. If a device ever presents you with a seed phrase it already knows, it is not your wallet.
  • Your own carelessness with the watching wallet. The public keys on your computer reveal your entire transaction history to whichever server Sparrow queries. That is a privacy problem, not a theft problem, and it is fixed by connecting your own node.

The verification habit that saves people

Every single time you receive, generate the address in Sparrow and then confirm the same address on the signing device's own screen before you give it to anyone. Every single time you send, read the destination and the amount off the device screen, not the computer display. Address-swapping malware and clipboard hijackers exist precisely because most people skip this.

The device screen is the only display in the chain that a compromised computer cannot rewrite. If a device has no screen — an NFC card, for instance — you have no independent confirmation at all, which is the real reason those cards are not suited to large balances. More on the wider threat model in is Sparrow safe.

Hardware wallet questions people actually ask

Which hardware wallets does Sparrow Wallet support?

The project states that Sparrow works with all common hardware wallets in both USB and airgapped modes. The devices named in its own documentation are Trezor, Ledger, Blockstream Jade, BitBox02, Coldcard, Foundation Passport, Keystone, SeedSigner, Keycard and Keycard Shell, Tapsigner and Satscard over an NFC reader, and the deprecated Cobo Vault. Support for Trezor Safe 7, Ledger Nano Gen5, Keycard and Keycard Shell arrived in release 2.4.0.

Does Sparrow support Trezor, and can a Trezor sign taproot messages?

Yes, Trezor works over USB — the Safe 3, Safe 5 and Safe 7 line as well as the older Model T and Model One. Taproot receive addresses and taproot spending are handled by Sparrow on the software side. Message signing is the messier part: signing a message with a taproot key uses BIP-322 rather than the old legacy scheme, and whether your particular Trezor will produce that signature depends on its firmware, not on Sparrow. If a message-signing attempt is refused for a taproot address, check the device firmware and try a legacy or segwit address from the same wallet instead.

Does Sparrow support Ledger, including multisig?

Ledger connects over USB and signs single-signature transactions without drama. Multisig is where people hit friction: a Ledger will only sign for a multisig wallet whose policy it has registered on the device, and that registration step — plus re-confirming the policy on the small screen — is the part that fails or confuses first-time users. It is workable, but if multisig is your main goal, a device with a broader multisig track record makes for a calmer setup.

Can I use Sparrow as a cold wallet without ever plugging anything in?

Yes, and that is one of the reasons to choose it. Sparrow reads an unsigned transaction out to an SD card as a PSBT file, or shows it on screen as an animated stream of QR codes. The signing device stays offline permanently. See the official airgapped guides for QR codes and SD cards.

What is a QR fountain code and why does Sparrow use one?

A single QR code cannot hold a large transaction. A fountain code splits the data into many frames that are displayed as an animated loop; the reader keeps scanning until it has collected enough frames to reassemble the whole thing, in any order. Sparrow implements this using the UR standard, which is why airgapped QR signing works for transactions with many inputs rather than only tiny ones.

Is an airgapped setup actually safer than USB?

It removes one category of risk — anything that travels over a USB data connection — at the cost of slower, fiddlier signing. For a wallet you touch weekly with a moderate balance, a reputable USB device with on-screen address verification is a sensible, defensible choice. For long-term savings you rarely move, airgapped signing is worth the friction because the extra minutes cost you nothing you care about.

Where should I buy a hardware wallet?

From the manufacturer directly, or from a reseller the manufacturer names on its own site. Never from a general marketplace listing, never second-hand, and never a device that arrives with a seed phrase already written down for you. A pre-seeded device is not a shortcut, it is a wallet somebody else already has the keys to.