pull down to refresh

"Yes, it's that easy. As switching to another LSP. We actually make it very easy"
So an app that users the Breez API.... Let's say they get uncomfortable with their user's IP addresses all going to LightSpark, or Breez, where they could be associated with their transaction details.
What would they do? They have to rebuild their implementation without Breez, right?
Because the only service that runs Breez -- is Breez -- right? Nobody else uses your proprietary API, right?
0 sats \ 2 replies \ @roy 3 Nov
Ah? What are you talking about? We are a client side library that provide a Lightning interface on top of native Lightning and different sub networks (Spark, Liquid, Arkade, etc). You don't like Spark, you can move to Liquid or to Arkade or to LDK. And we're completely open source...
reply
"A client-side library" -- which hard-codes URLs, (owned by the Marcus family / LightSpark) -- such that your unsuspecting users find that all of their transactions, along with their user-agents and I.P. addresses -- are exclusively shared with this one, centralized server, run by a Lighting "compliance" company.
Please see image below...
reply
27 sats \ 0 replies \ @roy 3 Nov
Oh come on... There's only one Spark now... Same as there's only one Liquid now and only one Arkade...
We use to have one LSP. When we added the LSP spec, we added a configuration for multiple LSPs (there's still no good discovery API).
reply