pull down to refresh
100 sats \ 28 replies \ @rizful_com 18h
Before using centralized APIs like Breez, please consider decentralized & private alternatives like Alby Hub. It's better for Bitcoin.
reply
50 sats \ 27 replies \ @roy 17h
Which use a centralized API to your LSP lol. Breez is decentralizing by connecting multiple sub-networks. A new LDK-based SDK is also coming soon.
reply
0 sats \ 26 replies \ @rizful_com 16h
Uh, the LSP standard is open -- and there are dozens of LSPs following the same public standard-- anyone can run an LSP. To switch to another LSP, literally just change an endpoint and open a new channel.
If your users want to switch out of Breez, to another company, is it that easy??
By marketing Breez's centralized API, you are getting users into a service that they can't easily switch out of. Great business for Breez, bad deal for the future of Bitcoin.
Also, of course, now you are also subjecting your users to surveillance by LightSpark -- the same company whose main purpose was "compliance", just 12 months ago. It's gross.
Also "multiple sub-networks". Huh?
Why did you go from supporting open standards to just running another centralized API?
reply
0 sats \ 4 replies \ @roy 16h
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.
reply
0 sats \ 3 replies \ @rizful_com 16h
"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
0 sats \ 2 replies \ @roy 16h
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
0 sats \ 1 reply \ @rizful_com 16h
"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...
And on github... https://github.com/breez/spark-sdk/blob/main/crates/internal/src/config.rs
reply
27 sats \ 0 replies \ @roy 15h
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 on another page
0 sats \ 20 replies \ @rizful_com 16h
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?
reply
0 sats \ 19 replies \ @roy 16h
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
0 sats \ 18 replies \ @rizful_com 16h
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
0 sats \ 2 replies \ @roy 16h
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
0 sats \ 1 reply \ @rizful_com 8h
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.
view all 1 replies
0 sats \ 14 replies \ @rizful_com 16h
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
0 sats \ 13 replies \ @roy 16h
No, they will switch to a different sub network or native Lightning.
view all 13 replies