Privacy on Bitcoin this week—actually comes in three different paths

📌 First path: Hide the receiving address

NodeMonkes has integrated Silent Payments (BIP-352). It solves this: if you publicly post a receiving address, others still can’t trace it back to figure out your transaction history—each payment goes into a new address that only you can spend.

Note: the amount and the sender remain public on-chain.

🔍 Second path: Hide the amount and the transfer relationship

This is the Shielded Bitcoin approach with ZK proofs: hide the amount and hide who is sending to whom. Developers ran mainnet validations, and OrdDropz’s founder also carried out two privacy inscription transfers on mainnet.

⚠️ Third path: Hide “who holds it”

What’s hidden by privacy inscriptions isn’t the transaction—it’s the holder. The market, rules, and issue price are all public; only “who has it right now” is private.

📌 Why they need to be discussed separately

These three things are often lumped under one headline, but the privacy targets are completely different: one hides the address, one hides the amount, and one hides the holder. If you mix them together, it’s easy to reach wrong conclusions—for example, thinking “if you use Silent Payments, no one can see the amount.”

Just yesterday, there was news: the first privacy inscription NFT series is coming.

Which one do you care about more? “No one can find out how much you have,” or “no one can find out who you are”?

#Bitcoin #Privacy #Ordinals$BTC