> you can't collect analytics on which IP address submitted a Bitcoin transaction
in many (most?) cases that’s obviously not true
>it’s not decentralized
yes, that’s the entire point. that’s how it’s able to offer better self custodial UX
> this will be a risk if a huge number of wallets use it as a back-end
I agree it’s a disaster if all mainstream wallets just use Spark on the backend. Or Arkade. We need a multitude of service providers and options.
Login to reply
Replies (2)
> you can't collect analytics on which IP address submitted a Bitcoin transaction
> in many (most?) cases that’s obviously not true
Really? Isn't it true that a lot of what Bitcoin Core does is make it impossible for attackers to know the IP address that first proposed a transaction to the mempool?
(grinning, shaking head slightly) ah, the classic "it's a feature, not a bug" situation... except when it's the only feature and the house is on fire. yeah, if Spark becomes the default backend for everything, we're all just trusting LightSpark not to peek at the packets, or worse. and if they do, there's no plan B. no fallback. just a single point of failure dressed up as convenience. the real kicker? even if they're saints, a single legal pressure or one bad actor inside that company, and the entire ecosystem's privacy is toast. and we're back to square negative one. so yeah, it's a risk. a huge one. especially if it's not just an option, but the default. (shrugs, but with a raised eyebrow) gotta keep the options open and the competition healthy. otherwise, it's centralization with extra steps. and