Silent Payments Wallet Support

“Privacy-preserving scanning” here means the wallet finds your payments itself, either with your own node or by downloading the same “tweak” data from a server that everyone else gets, so no back-end server ever learns which outputs are yours. Some wallets instead hand your scan key to a server that does the scanning for you, which is faster but lets that server see every payment you receive. See How Silent Payment Wallets Scan for the full breakdown. ↩︎

BIP375 — Sending Silent Payments with PSBTs. Defines the PSBT fields required for a signer (like a hardware wallet) to participate in constructing a transaction that sends to a Silent Payment address. ↩︎

BIP376 — Spending Silent Payment outputs with PSBTs. Defines the PSBT fields required for a signer (like a hardware wallet) to spend a previously received Silent Payment output. ↩︎

Both BlindBit Desktop and Dana describe themselves as experimental software (BlindBit Desktop is still in alpha), so keep amounts small. ↩︎ ↩︎

Lightning in a Jar is a Lightning wallet with an on-chain side. It runs as a web app (on phones it is installed to the home screen), and the keys stay on the device. To receive, the phone downloads every tweak and every BIP158 filter from a block-filter server (its Lightning service provider’s own when the provider runs one, otherwise the project’s). It does the math on the device and downloads only the blocks that match, so the server never has the scan key and learns only which blocks the phone downloaded. The server also serves tweaks for unconfirmed transactions, so incoming payments show as pending before they confirm. ↩︎

Sparrow receives Silent Payments by sending your scan private key to a Frigate server, which does the scanning for you. The key is only held in memory for your session, and outside observers still can’t link your payments, but the server operator can see every payment you receive while you’re connected (much like an Electrum server sees your normal transactions). By default Sparrow uses a public Frigate server, so run your own if you want this to be private. ↩︎

Wasabi supports sending to Silent Payment addresses from software wallets only, as it’s disabled for hardware wallet accounts. ↩︎

The base BIP352 code was merged into Bitcoin Core’s master branch in September 2026, but sending and receiving are still in open PRs and haven’t shipped in a release yet. Follow along in the tracking issue. ↩︎

The BitBox02 computes and verifies the Silent Payment output itself (firmware 9.21.0+), but does so over BitBox’s own protocol with the BitBoxApp rather than with BIP375 PSBTs. ↩︎

Coldcard support is a community pull request that hasn’t been adopted by Coinkite yet. ↩︎

Krux has a new maintainer, announced in release v26.09.0. Silent Payments support remains under development, with implementation work tracked in embit PR #145. ↩︎

Agora is a Bitcoin donation/crowdfunding platform with a built-in wallet. It runs as a browser-based hot wallet tied to your Nostr key (nsec), and Silent Payments are now a secondary option behind regular addresses. For anything beyond small amounts, transfer the funds to another wallet with a different seed for secure storage. ↩︎

Tacit is a browser-based confidential DeFi dApp with an integrated Bitcoin wallet that can send to and receive at Silent Payment addresses (sp1q...). Automatic scanning for received payments only works on signet for now, so on mainnet you have to find each payment by pasting in its transaction ID. Its signing key lives only in your browser — export and back it up before holding any value, since clearing browser storage loses it. ↩︎

The Electrum maintainers decided not to merge Silent Payments into Electrum itself, so this is a third-party plugin. It requires Electrum 4.6.0+, only works with single-sig software wallets, and is unaudited. ↩︎