pull down to refresh
0 sats \ 4 replies \ @roy 3 Nov \ parent \ on: Breez MCP for AI agents ⚡️ lightning
Yes, it's that easy. As switching to another LSP. We actually make it very easy...
You continue to spread FUD and demonstrate a complete lack of understanding on the underlying implementations.
Multiple sub-networks: Liquid, Spark, soon Arkade and any other L2 with unilateral exit. You feel comfortable bashing Spark, I don't see you do the same for Arkade. I wonder why.
You also keep ignoring we're investing in native Lightning. We had to deprecate Greenlight (not because we didn't try), but we're not giving up and will release an LDK implementation very soon (months of work already invested).
But what do you care... You keep FUDing us because you don't like Spark. Grow up.
"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?
reply
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...