The Privacy Problem Bitcoin Never Solved
When Satoshi wrote the Bitcoin whitepaper, Section 10 was dedicated to privacy. The solution? Use a different address for every transaction. This worked… until on-chain sleuths arrived.The Good
Low mental overhead - One master secret recovers all your funds
The Bad
Traceable payments - Anyone can link your transactions together
Previous Solutions (And Why They Failed)
BIP 47: Payment Codes
Used by Samourai Wallet (#FREESAMOURAI), this approach required a notification transaction before sending funds.What We Actually Need
Silent Payments delivers all three.
How Silent Payments Work
Math notation:
- Lowercase (a, b, p) = private keys
- Uppercase (A, B, P) = public keys
G= generator point on secp256k1 curve·= scalar multiplication
The Magic Formula
- Simple Version
- With Input Hash (Recommended)
- Spending & Viewing Keys
Alice publishes: Public key
Bob computes:
Alice scans:
ABob computes:
A + hash(b · A) · G = P (destination address)Alice scans:
A + hash(a · B) · G = P ✓Where b is Bob’s UTXO private key.Why this works
Why this works
Thanks to ECDH, both compute the same shared secret:
b · A == a · BSo they both derive the same address P, but only Alice can spend from it.The Result
One Address
Share a static silent payment address forever
Zero Extra Fees
Same cost as a regular Bitcoin transaction
Perfect Privacy
Charles has no idea Alice received Bitcoin from Bob
Ready to Integrate?
Start Building with Silent Payments
Follow our integration guide to implement Bitcoin privacy in your app
Learn More
BIP-352 Standard
Read the official Bitcoin Improvement Proposal
Silent Payments Explained
Deep dive into the protocol mechanics