
Full recording, about 85 min. Plays from youtube-nocookie.com. Watch on YouTube
Jump to a chapter (13 chapters)
- Welcome and the plan for today
- Live demo: Cake Wallet to Shroud, then mempool.space
- Why some wallets see a payment sooner: scanning
- Address reuse, and what silent payments don't fix
- Spot the silent payment: Taproot outputs and round amounts
- Backends: Electrum servers vs BlindBit
- Gap limits, with a real wallet recovery story
- Razor's deep dive: history and the interactivity scale
- Sender vs receiver: why scanning is the hard part
- Building silent payments from scratch
- Quiz
- How to contribute: Dana, BlindBit, Frigate, Shroud
- Wrap-up and what's next
TL;DR
- A silent payment address starts with sp1 and can be posted anywhere. Every payment to it lands on a different, normal-looking Taproot output, so nobody can list your payments.
- It fixes address reuse, the baseline privacy leak. It does not stop chain analysis if you later merge those coins, so pair it with coin control, PayJoin and other tools.
- Sending is easy and needs no node. Receiving is the hard part: your wallet has to scan every transaction, and how it scans (full node, Electrum server, BlindBit) decides what you leak and how fast you see payments.
- The projects are run by very few people: Dana, BlindBit Oracle, Frigate and Shroud all welcome new contributors.
Try it before next time0 / 4
Mission board0 XP
Six badges to go silent
Four mini-games from the call, a try-it-yourself checklist and a final quiz. Each one lights up a badge. Progress stays on this device and adds XP to your builder passport.
Highlights
1One address, nothing to link
The session opened with a real payment. keypleb tapped Request in the Shroud wallet and got an address starting with sp1. keypleb pasted it into Cake Wallet and sent 20,000 sats. Then we looked the transaction up on mempool.space, and there was nothing special to see: two inputs, two outputs, one of them a plain Taproot (v1_p2tr) output. No sp anywhere. That is the trick: you can publish one address forever, and every payment lands somewhere new.
Why that matters. Our guest Sosthène, who builds the Dana wallet, pointed at donation pages that show a plain Bitcoin address. Razor did it live with a well-known privacy project’s page: paste its address into mempool.space and you see every donation since 2020, more than 17 BTC in total, and where the coins went next. Address reuse doesn’t only hurt the receiver. It hurts everyone who pays them, because now their coins are tied to a public address too.
“If you reuse addresses, you’re done. No matter what you do after that, there’s no way to have good privacy.”
Sosthène, Dana walletMini-game 1 · Donation box✓ badge earned
Run a donation page, then play the spy
Pick an address type, send a few donations, and watch what a stranger with a block explorer can see. Try both modes.
Your donation page
Spy pastes your address into an explorer
Send three donations in each mode.
What silent payments don’t fix. Sosthène was clear: they solve address reuse, the baseline, and nothing more. Collect many donations on separate outputs and then spend them together in one transaction, and you have just told chain analysis they all belong to the same person. Privacy is layered: silent payments, then coin control, PayJoin, CoinJoin, Lightning and ecash on top. And off-chain: cameras off, don’t talk about your stack, maybe skip the Bitcoin t-shirt at the airport. In France this year, home invasions targeting crypto holders made it painfully real.
2Spot the payment
keypleb asked the right question: how would chain analysis tell this apart from a PayJoin, which also has two inputs and two outputs? The Taproot output is a hint, not proof. The bigger giveaway was the amount. The payment was exactly 20,000 sats, a number a human typed. The change was 3,026 sats. Analysts also convert every output to dollars or euros at the time of the transaction and look for round numbers there. Sosthène’s tip: when you ask to be paid, add a few random sats.
Mini-game 2 · Be the chain analyst✓ badge earned
Which output is the payment?
Three transactions. Tap the output you think is the payment, or say you can’t tell. Get all three right.
Look at the amounts.
3Scanning is the hard part
Sending a silent payment is easy: no full node, just follow the protocol. Receiving is the work. The receiver’s wallet has to check every transaction to see if one is for them, and different wallets do that differently. That is why some wallets see your payment while it is still in the mempool and others only after it is mined.
- Full node. Scan the whole chain and the mempool yourself. Best privacy, most effort.
- Electrum-style server (Cake Wallet, and Frigate behind Sparrow). Fast, sees mempool payments, but the server learns which outputs are yours, so you trust it.
- BlindBit Oracle (Dana). Serves the same public data to everyone, so it learns little more than your IP and that you use silent payments. Today it can’t see mempool payments: you wait for a block.
Along the way Sosthène explained the gap limit: a normal wallet only checks so many unused addresses ahead. keypleb told the story of a client whose two wallets showed different balances from the same seed. Two days of troubleshooting later, raising the gap limit made the “missing” bitcoin appear. Silent payments don’t have that problem, but they trade it for scanning.
Mini-game 3 · Pick your scanner✓ badge earned
Three people, three setups
Tap a backend to see its trade-offs, then pick the right one for each person.
Tap a backend.
4Razor builds it from scratch
Razor started with history. Silent payments are BIP 352, by Ruben Somsen and Josie Baker. Before them came stealth addresses, BIP 47 reusable payment codes (Samourai), which need a notification transaction, and BIP 351, which uses OP_RETURN. Then his favourite slide, the interactivity scale:
The interactivity scale
How much do sender and receiver have to talk before a payment?
Then the deep dive: how would you invent silent payments yourself? Mini (the receiver) wants to be paid by Miki, without anyone else being able to tell. Razor walked through five versions, each fixing the last one’s problem. Play through them:
Mini-game 4 · Build it from scratch✓ badge earned
Five versions, five fixes
Here is where that lands, in one picture:
How a silent payment works
Shared secret from the sender’s input key and the receiver’s address. Only the receiver can redo it.
output key = A + t·G → spend with a + t
receiver scans: for every transaction, a·(input keys) → does any output match?
The real BIP adds more: what happens with many inputs, and a counter so two payments from the same key still give different outputs. If you follow the five steps above, the BIP reads easily. Razor’s tip: start at silentpayments.xyz.
5Where you can help
Sosthène dropped the projects in the chat, and was blunt: they are built by very few people and could definitely use help. Dana (donations wallet), BlindBit Oracle (privacy-friendly scanning server), Frigate (silent payments Electrum server behind Sparrow) and Shroud with its indexer. Razor’s way in: build and run the project, break the tests, do reviews. Want a recommendation to a grant giver later? Show proof of work first.
Key takeaways
- Never reuse an address. It leaks your history and everyone else’s. A silent payment address is the one you can safely post on a website.
- One layer, not the whole stack. Silent payments fix the baseline. Don’t merge those coins carelessly, avoid round amounts, and add PayJoin and coin control.
- Scanning is the frontier. How a wallet finds its payments decides speed and privacy, and it is exactly where the projects need developers.
Final level: the quiz
Razor ran a live quiz on the call (one question tripped up everyone). Here are five. Get them all right and the Silent badge lights up.
Test yourself
Resources shared
Reading
- BIP 352: Silent Payments, Josie Baker and Ruben Somsen: the spec. Builds the idea step by step, much like Razor's slides. You need a little Diffie-Hellman
- silentpayments.xyz: the best place to start: overview, wallet list, docs and the BIP, all well organised
- BIP 47: Reusable payment codes: an older reusable-address scheme (used by Samourai) that needs a notification transaction first
- BIP 351: Private Payments: another alternative mentioned on the call, which relies on OP_RETURN. Silent payments use no OP_RETURN
Wallets
- Dana wallet: mobile wallet for accepting donations with silent payments, built by our guest. Experimental, uses BlindBit, looking for contributors
- Cake Wallet: sends and receives silent payments; used for the live demo and sees payments while they are still in the mempool
- Sparrow Wallet: desktop wallet that recently added sending and receiving silent payments, through a Frigate server
Tools
- BlindBit Oracle: a silent payments indexing server that only serves public data, so it learns very little about you. Can't see mempool payments yet
- Frigate, Craig Raw: Electrum server for silent payments, the backend behind Sparrow. Scans for you, so you trade some privacy for speed
- Shroud indexer: the silent payments indexer behind the Shroud mobile wallet, shared in the chat
- mempool.space: we looked up the demo payment here: to an explorer it is just a v1_p2tr (Taproot) output
Code Orange
- Privacy Track: Silent Payments lab: our hands-on lab for this topic
- Privacy Track: all 12 sessions, every 1st and 3rd Tuesday
- Developer fellowship: paused for now, back in the pipeline. Build proof of work on these projects in the meantime
Also on the call: why you might skip the Bitcoin t-shirt at the airport, why France has seen home invasions targeting crypto holders this year, and a tip for asking to be paid: add a few random sats so the amount is not round. Guest speaker Anmol (Shroud wallet) could not make it this time.
These notes are also on GitHub: code-orange-dev/session-notes. Free to share and reuse (CC0).