You probably saw some chatter about Silent Payments floating around the forums. It's basically this thing where you can send someone bitcoin to their static address, but every single transaction lands on a completely different address. The cool part is neither the sender nor receiver needs to talk beforehand or exchange keys like with PayNyms. Both sides just calculate the same one-time address independently using ECDH math.
Anyway, I wanted to map out where this tech actually is right now. BIP352 is the foundation obviously, but there's still a lot of ground to cover before it's everywhere.
Where does Silent Payments stand right now?
2 replies 458 views
Sparrow's got it working, sure, but that doesn't solve the real problem. We need a proper CLI scanner that runs as a daemon so people can actually use this without being locked into one specific wallet. Otherwise it's just a neat feature in a single app, not something that actually scales to real use.
What I'm really waiting for is Foundation to jump in. My whole setup is Sparrow + Passport, and the moment they support Silent Payments I'm moving my main stack through an SP address to break the on-chain history. Could do it a bunch of different ways with one or two addresses, but the end goal is the same fresh start without the baggage.
Related topics
- Issues with ripemd160 on Ubuntu 22 9
- New Bitcoin Improvement Proposal with $100 Reward 9
- Clipboard Vulnerabilities in Cryptocurrency Transactions 8
- Understanding the Differences Between Traditional and Simplified Chinese Mnemonics 6
- Running Bitcoin Core on a Laptop with Limited Storage 20
- Exploring Blockstream's Satellite Tech and Its Potential 22