Not convinced these solve much of anything, generating new addresses from an xpub is not hard

Where people dox their stack is in consolidation which they'll still do with silent payments if they weren't sophisticated enough to generate new addresses in the first place.

Privacy is and will always be a practice, not a tool, product or protocol.

This rings true yet again:

> "privacy" apps spread through virtue signaling, not substance

justin_shocknet

Every time you share a Bitcoin address, you leave a thread someone can pull (forever).

Share the same address twice and a chain analyst can link those two payments together. Do it a hundred times — like most people do when they paste their address into a profile, a donation page, or a checkout form — and you’ve handed over a near-complete financial map of your on-chain activity.

generate a new address for every transaction.

Silent Payments, formalized in BIP-0352, solve this at the cryptographical level. One static address, published once. Every payment that hits it lands at a fresh, unique on-chain address — automatically, without any coordination between you and the sender.

This is what privacy-preserving Bitcoin receiving actually looks like.

bitcoin

bitcoin_beginners

> ## The problem
>
> Every time you share a Bitcoin address, you leave a thread someone can pull (forever).
>
> Share the same address twice and a chain analyst can link those two payments together. Do it a hundred times — like most people do when they paste their address into a profile, a donation page, or a checkout form — and you’ve handed over a near-complete financial map of your on-chain activity.
>
> The standard advice has always been: *generate a new address for every transaction.* Good advice. Bad UX.
>
> Silent Payments, formalized in BIP-0352, solve this at the cryptographical level. One static address, published once. Every payment that hits it lands at a fresh, unique on-chain address — automatically, without any coordination between you and the sender.
>
> This is what privacy-preserving Bitcoin receiving actually looks like.
>
> ## What Are Silent Payments?
>
> ### How It Works Under the Hood
>
> ### The Dual-Key System: Scan and Spend
>
> ### What Does It Look Like On-Chain?
>
> ### Labels: One Address, Multiple Contexts
>
> ### Wallet Support Right Now
>
> ### The Light Client Problem
>
> ### Should You Use Silent Payments Today?
>
> ## So what?
>
> [**...read more at massmux.org**](https://massmux.org/p/silent-payments-a-nice-bitcoin-privacy)