somewhat recently cake wallet added silent payment support to their bitcoin wallet. I don't ever use bitcoin so I was unaware of the tech until then. it seems to work similarly to monero's remote node scanning & is said to enhance privacy.

im wondering how it weighs against moneros privacy protections & what this development may or may not mean for the project in the future. im worried about the way it may overshadow XMR due to bitcoins reach & possible consequences if it is inferior tech (being based on a transparent L1 & all). however it is also a big step towards closing the gap between the privacy coin community & the BTC maxis (which is probably only good for eveyone involved). so im feeling split & figured i would ask the community what they think of the development.

it seems to be more like hiding coins in different addresses while obscuring it on chain & using some clever math to make the UX better. aswl as not giving over ur key to the remote node. although Ill admit the technical stuff is slightly about my head so please correct my explanation as needed haha.

im more so wondering about the practical use/implications when it comes to privacy & was struggling to find a good comparison online.

you are viewing a single comment's thread
view the rest of the comments

[–] kenkenken@sh.itjust.works 2 points 4 months ago (1 children)

Silent Payments are just stealth addresses for Bitcoin. There already be some earlier implementations, for example PayNim in Samourai Wallet. But the new thing is finally a general standard proposed for wallets.

It allows to create new Silent Payment address which never appear on the blockchain. Instead, the sender of a transaction will derive an unique regular address controlled by the recipient. Similar to Monero yes. The only thing it gives: one cannot naively check the balance or the transaction history of a SP address.

If it will be adopted it can improve privacy on Bitcoin slightly, but... It's a completely client-side feature which does not require protocol changes and could be implemented like from the day one of Bitcoin. Silent Payments are new only because it uses Taproot, and the previous thing was BIP 47: Reusable Payment Codes, which has about zero usage. Just because bitcoiners don't care much about privacy. There is only a small minority of users who cares.

For more serious privacy hidden amounts are a must have feauture. And in the past at least bitcoiners were strongly against it, because they care about transparency, audibility and trust to the system more than about privacy. Potentially, some privacy protocol can be implemented on L2, but L2s are often centralized and cannot withstand governmental pressure. But in theory yes, they could have strong private payments on L2, but this rather won't happened on L1 in near decades. Even on Ethereum where such protocols are possible for few years now, projects are still in development.

In short: the problem with privacy in Bitcoin is not technical, it is more about culture and a lack of demand from the Bitcoin community. Imagine that bitcoiners will promote some strong privacy improvement for which Binance and other exchanges could delist BTC, or the protocol will become more complex for understanding by an average human.

[–] makeasnek@lemmy.ml 1 points 4 months ago* (last edited 4 months ago)

This is a good overview of how silent payment work, thank you for posting it. I learned some new things!

but L2s are often centralized and cannot withstand governmental pressure

This is true on other networks but not true of Bitcoin (lightning). Lightning is even more decentralized than L1 is, you can run a lightning node on an android phone.

it is more about culture and a lack of demand from the Bitcoin community.

Absolutely agree with this, but the culture has been changing. Auditability of supply of coin has been the major hurdle privacy wise, but even with keeping that there are some major changes that can be made to improve privacy. It's a common topic at Bitcoin conferences now, everybody knows this is the direction Bitcoin needs to move in (and has been moving in).