correct me if I’m wrong but this is an issue with every single centralized services, wallet or client-server protocol. of course there are mitigations against it that can be taken both on the server as well as client side. the protocol can be reinforced as well on the privacy side. we are definitely looking at all available options. not sure what you mean by “run a service”

Replies (3)

Got it. One reason Bitcoin and the Lightning Network are so powerful, is that they don't required centralized service providers. I think there is some general confusion going on with Spark (and others) saying they are "non-custodial" -- which seems great, but, if they are logging all your transactions anyway, that's really a different flavor of "non-custodial" then you get from, for example, the Lightning Network, or a Bitcoin transaction.
By "run a service" -- I mean, like the Ark or Arkade service, whatever the service that users have to hit in order to make a transaction. That's it. Obviously if a user is using Strike or Coinbase or PayPal, then that is the centralized "service" the user has to communicate with. I guess these L2s -- Spark, Ark, don't really "fix that issue either. They're not a privacy-preserving L2 like the Lightning Network. They can still aggregate your transaction data, IP address, user-agent, stuff like that, and then they have to turn it over, if, say, a certain government wanted to look at it. Maybe this is all expected, I'm still learning here.