Bitcoin’s privacy problem has always had the same workaround: never reuse addresses. Generate a fresh one every time. Treat each receive like a one-time-use token. It works, but it is clunky, easy to mess up, and falls apart the moment you put an address on a tip jar, a donation page, or a business invoice.

Last week, that rule got rewritten.

On May 21st, Sparrow Wallet released v2.5.0. The headline feature: Silent Payments receiving, including support for airgapped hardware wallet signers. Sparrow had supported sending to Silent Payment addresses since v2.3.0 last October, but sending was the easy half. Receiving is the hard part, and Sparrow shipping it changes what’s actually possible for normal Bitcoin users who care about privacy.

What is a Silent Payment?

Think of it like a PO Box.

You give the same PO Box address to a hundred people. They all send you letters. But when those letters arrive, they get sorted into a hundred different locked boxes that only you have the key to. From the outside, no one can tell those hundred letters all went to the same person.

That is what a Silent Payment address does for Bitcoin. You share one address, forever, with as many people as you want. Every payment that comes in lands at a different, unique Bitcoin address that only your wallet knows how to find. Anyone watching the blockchain sees a bunch of unrelated Taproot outputs. They don’t see a pattern. They can’t group your payments or estimate your stack.

Why this is a big deal

Until now, the rule has been “never reuse a Bitcoin address.” Reuse one and you hand chain analysis firms everything they need to follow your spending, estimate your holdings, and map your network. That is why every wallet you have ever used generates a new address each time you tap receive.

It works, but it breaks down constantly. Putting an address on a website, a donation page, an invoice, or a business card means people will reuse it whether you want them to or not. And the moment they do, your privacy is gone.

Silent Payments fix this without changing Bitcoin itself. No fork. No consensus change. Just clever cryptography that lets the sender derive a unique output address from your single static identifier plus their own transaction inputs. The receiver scans the blockchain looking for outputs that were crafted to be sent to them.

One address. Reuse forever. No privacy loss.

This is the closest Bitcoin has ever come to “give out your address like you give out an email.”

Why receiving was the hard part

Sending is straightforward. The sender knows who they’re paying, their wallet does some math, derives the unique output address, and broadcasts the transaction. Nothing exotic from a wallet-engineering perspective.

Receiving is brutal. Your wallet has to scan every eligible Taproot transaction in every block and run a cryptographic check to see whether it was crafted to be sent to you. That is computationally expensive. A full node can chew through it in 8 to 12 hours from genesis. Light wallets, the kind most people actually use, can’t realistically do this work themselves.

This is why almost every wallet that has added Silent Payments support over the past two years has only added the sending half. Receiving requires either running a full node or trusting a third-party server to do the scanning for you.

What Sparrow shipped

Sparrow v2.5.0 solves this by integrating with frigate.2140.dev, a public Electrum server that does the heavy scanning work for you. You point your wallet at the server, hand over your scan key (which can only see incoming payments, not spend them), and incoming Silent Payments just appear. Like any other receive.

The brilliant part is that the scan key and the spend key are separate. Your spend key never leaves your hardware wallet. The scan key is a watching-only credential that lets a third-party server identify your incoming payments without being able to touch your funds.

This means you can receive Silent Payments to cold storage. Your private keys stay airgapped. Your hardware wallet stays cold. The server does the work of finding your incoming payments, but it can never spend them. Self custody and privacy, together, with no compromise.

Last December I sat down with the Dana Wallet team in Taipei to dig into how Silent Payments work under the hood. Dana is one of the first mobile wallets built specifically around this protocol, and the devs walked me through both the cryptography and the design decisions. If you want a deeper technical understanding of why this is such a meaningful upgrade, that conversation is the place to start.

Watch the Dana Wallet interview here

The bigger picture

For more than a decade, the standard advice has been “don’t reuse addresses or you’ll dox yourself.” It is confusing for beginners, easy to forget, and impossible to enforce when you publish an address publicly. Silent Payments rewrite that rule entirely.

Self custody is not just about holding your own keys. It is about being able to transact without leaking your entire financial life to chain analysis firms. Holding your own keys is step one. Step two is making sure no one knows what those keys are holding.

Sparrow shipping Silent Payments receiving, with hardware wallet support and airgapped signing, is one of the most important privacy upgrades Bitcoin has had in years. It puts proper privacy within reach of normal users, not just those willing to run their own indexer or read source code.

If you have already started experimenting with Silent Payments, I would be curious to hear how you are using them? Drop a comment down below.