pull down to refresh
257 sats \ 9 replies \ @justin_shocknet 7 Dec \ on: Silent Payments? bitcoin
Silent payments are total nonsense in this context. Literally 0 reason for this merchant to use them.
Even if we ignore for a moment the fact that there's only one client and it's a shitcoin wallet...
It's the merchant's own website, so who's he getting privacy from? He doesn't need to protect his addresses from himself. Each buyer can already get a unique payment address from the site and he doesn't need to reveal an xpub or anything because he's serving the addresses directly.
Silent payments also doesn't obviate the need for him to conduct proper UTXO management with received funds if he wants to maintain privacy, which if he thinks silent payments are applicable to him and outsourcing setup it means he doesn't have the knowledge to do correctly anyway so it's all moot.
Case closed. I'll copy and paste your response. I was just reading zaprite faq. There is no need.
reply
reply
No. I didn't mean that zaprite mentions silent payments. I just meant that I don't think silent payments would provide a huge benefit. I also think as a practical matter that no one is going to blindly sent 500kUSD worth of bitcoin by clicking a web icon. I'm sure there will be back and forth communications, and a fresh address or two would be used.
reply
reply
Right. I think he is imagining a seamless web experience without much hands on. I'm certain that's not even a realistic fiat experience.
Silent payments are total nonsense in this context. Literally 0 reason for this merchant to use them
One reason might be limiting server-side complexity
Silent payments involve basically zero server configuration, you just post a piece of text on your website and you're done
If, instead, you want the website to serve a unique address for every user, the server needs to run something like btcpay or electrum and the company needs to pay a dev to learn what to install, how to use its api, and how to connect it to their website
Silent payments = easier = better
reply
the server needs to run something like btcpay or electrum
Not really, whatever database that's taking orders or serving the catalog can just as easily have thousands of HD addresses dumped into it. Heck, even a day to day wallet that used Nostr for comms could provide those addresses to completely static JS on a site...
Silent payments on the other need a service to actually find the payments, and the user profile shows it won't actually be more private. If we're to assume interactivity with the payment it gets even worse...
Privacy feature = no substance = pointless distraction = worser
reply