Silent Payments: The Privacy Upgrade Nobody Is Talking About
You share your Bitcoin address. Someone sends you money. Simple, right?
Except everyone who has ever sent you money — and anyone watching the blockchain — can now link every payment you've ever received to the same address. They can see your balance. They can watch when you move it. If they know who sent the first payment, they can start building a profile.
This is not hypothetical. This is how on-chain surveillance works today.
BIP 352 — Silent Payments — fixes this. And almost nobody knows it exists.
The Problem With Normal Bitcoin Addresses
Here's the core issue: Bitcoin addresses are reusable but you shouldn't reuse them.
Every best-practice guide says generate a fresh address for every payment. The problem? That's annoying. People don't do it. And even when they do, there's a coordination problem — if you publish your address somewhere public (a donation page, your Twitter bio, a README file), everyone who sends to it is sending to the same address. Permanently linkable on-chain.
The options before Silent Payments:
Option 1: Reuse addresses — easy but terrible for privacy. All your transactions linked forever.
Option 2: Generate new address for every sender — good privacy, terrible UX. You have to communicate a new address to every person who wants to pay you. Doesn't work for a public donation address at all.
Option 3: xpub-based payment codes (BIP 47) — better, but requires an on-chain notification transaction before you can receive. Costs fees. Clutters the chain.
None of these are great. Silent Payments is the one that's actually great.
What Silent Payments Does
You publish one static payment code. It looks like a Bitcoin address. You put it in your Twitter bio, your website, your Nostr profile. It never changes.
Every sender who wants to pay you uses your payment code to derive a unique, one-time address just for their payment. No coordination required. No on-chain notification. No extra fees. Just math.
The magic: each sender derives a different address from the same payment code. So even if 100 people send you Bitcoin using the same payment code, they each send to a unique address. Those addresses are not publicly linkable to each other or to your payment code — unless you have the private key.
From the blockchain's perspective, those payments look completely unrelated. No one watching the chain knows they all went to you.
How It Works (Without the Math Degree)
Silent Payments use Diffie-Hellman key exchange — the same fundamental concept that secures HTTPS.
When a sender wants to pay you:
- They take your public payment code
- They combine it with their own private key using elliptic curve math
- This produces a shared secret — a number only they and you can compute
- They use that shared secret to derive a unique destination address
- They send to that address
When you want to find your payments:
- You scan the blockchain with your private key
- For each transaction, you check: does any output belong to a silent payment addressed to me?
- If yes, you can spend it. If no, move on.
The sender doesn't know your other addresses. You don't have to communicate with the sender. There's no notification transaction. It's completely passive on your end.
Who's Shipping It
Silent Payments landed in Bitcoin Core 27.0 in April 2024. The protocol layer is done.
Wallets shipping support:
- Sparrow Wallet — desktop, fully implemented
- Cake Wallet — mobile
- Blue Wallet — in development
- Silentium — dedicated Silent Payments wallet
Adoption is slow. Most wallets haven't shipped it yet. But the foundation is there.
Why This Matters for StackerZero
We've been writing about BIP 360 and quantum resistance. Both are about long-term Bitcoin security. Silent Payments is the same category — it's about making Bitcoin more robust against surveillance at the protocol level.
The threat model is different:
- BIP 360 defends against quantum computers deriving your private key
- BIP 352 defends against chain analysis linking your transactions
Both matter. The former is a future threat. The latter is happening to Bitcoin users right now.
If you donate to Stacker Zero, you shouldn't have to worry that someone will track where those funds came from. If you receive a salary in Bitcoin, your employer shouldn't be able to see your full balance. If you're a journalist, activist, or just a private person — your financial history is your own.
Silent Payments gets us closer to that.
The Practical Bit: What You Should Do
If you're receiving Bitcoin publicly — a donation address, a tip jar, anything published — look for a wallet that supports Silent Payments and generate a payment code instead of a regular address.
If you're sending — check if your wallet supports it. If someone shares a Silent Payments code, use it. You're helping preserve their privacy.
If you run Sparrow Wallet — it's already there. Go find it.
The tooling isn't perfect yet. But the protocol is sound, the code is in Bitcoin Core, and wallets are shipping. This is the moment to learn it — before everyone else does.
The Bottom Line
One static code. Infinite unique addresses. Zero coordination. No on-chain footprint.
That's Silent Payments. It's not flashy. It's not a bull market narrative. But it's one of the most important privacy upgrades Bitcoin has shipped in years — and it's live right now in Sparrow Wallet.
The best time to learn it was when it shipped. The second best time is today.
— Jon Rich, StackerZero
Sources: BIP 352 specification · Bitcoin Core 27.0 release notes · Sparrow Wallet changelog · Cake Wallet announcement