pull down to refresh
0 sats \ 20 replies \ @rizful_com 3 Nov \ parent \ on: Breez MCP for AI agents ⚡️ lightning
If anyone wants to read Roy's defense of his buddies at LightSpark -- here is the "X" thread: https://x.com/MegalithicBTC/status/1970491694580932723
Why is the "inventor of the LSP" now spending his time shitting on open standards and trying to get everybody to use a dangerous, centralized, proprietary API like Spark? Is it just as simple as a financial interest?
I'm not "shitting" on open standards... I'm saying that LSPs are also a centralizing factor, very similar to sub networks. The SSP interface in Spark in actually public, the implementation is the only closed source in Spark. But, you can run your own Spark and implement your own SSP today if you want to. If you run your own Spark, we'll support it as well ootb. Same goes for Arkade.
reply
This is the heart of the misinformation you are spreading, which for some reason is being repeated widely.
As you well know, nobody but LightSpark can run the server-side code of Spark.
LightSpark has not released the server-side code -- likely because it would show that their "self-custody" claims are a sham.
LightSpark might at some point "invite" other companies to run it, but that seems unlikely -- and anyway -- this is Bitcoin. This is not Solana or PayPal. In Bitcoin, we want OPEN standards which are PERMISSIONLESS.
We do not want millions of users tied to one web server in Los Angeles or Tel Aviv that gets their IP address AND all of their transactions.
And: If I have to set up a meeting with David Marcus or Roy in order to participate in this closed ecosystem... that is really bad, and really dangerous.
There are DOZENS of LSPs currently implementing an open standard, and ANYONE can run an LSP, without permission.
Comparing the Breez API or the Spark API to LSPs, or the Lightning Network -- you're taking advantage of the naivete of certain influencers. It's bad & it's dangerous and you should stop doing it, please.
reply
They did release the server side code: https://github.com/buildonspark/spark/tree/main/spark
I don't control Spark... And yes, they are in control on the Spark operators.
There aren't many LSPs with enough liquidity... See how many Alby is actually using. You know how I know? Because I am the one on-boarding them... I'm the one getting calls asking which LSPs to use (and yes, I am sending them your way).
reply
Looks like that is SOME of the necessary code, but since there is no public specification for the Spark server.... it's mostly useless. Anyway, as you say, it's a closed system, David Marcus is going to decide who can run it. Again, similar to like Solana or Tron or something, totally on-point for that kind of top-down ecosystem -- perfect for building the gambling solutions that LightSpark is working on, but totally uncool for serious Bitcoin/Lightning apps.
Another good test. What happens if Megalith LSP goes down or disappears?
I can tell you exactly what happens --- several other 100% compatible LSPs are available -- Olympus, among others. A user takes 5 minutes to switch LSPs, and that's that.
What happens when the Breez API or the Spark API goes down?
Your users are fucked! Your system is totally centralized, so it's not only not private, but it's not fault-tolerant at all!
reply
No, they will switch to a different sub network or native Lightning.
reply
How would a user switch from LightSpark's API to native lightning? By withdrawing their funds and putting it back on the Lightning Network, right?
reply
Same when an LSP goes down...
reply
Can you show me where in your code a user who has been hooked up to the Spark API could easily switch to using an LSP or another open standard with decentralized participants?
reply
We have partners bundling Liquid and Spark in their apps. You just need one on-chain transaction to switch between them (https://github.com/breez/spark-sdk/blob/87b856a97b4b94cf2c1d7960aa7dca3dce62e121/crates/spark/src/services/unilateral_exit.rs#L59). Same would be to move to Arkade, LDK, etc.