pull down to refresh

No, they will switch to a different sub network or native Lightning.
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
0 sats \ 11 replies \ @roy 3 Nov
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
0 sats \ 9 replies \ @roy 3 Nov
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.
reply
This is what you mean by "self-custody"... right? That it's possible to withdraw funds from the Breez API? How does that differ from Coinbase? Coinbase also allows me to withdraw from their centralized service.
reply
0 sats \ 0 replies \ @roy 3 Nov
It's unilateral exit. You don't need their permission to exit to the chain.
reply
But, no option to use a decentralized network like the LSP standard? Only centralized services are possible with the Breez SDK? After inventing the LSP standard, what caused you to, 5 years later -- simply not support any decentralized, open standard?
reply
0 sats \ 5 replies \ @roy 3 Nov
We are supporting it in the LDK SDK... We just had to switch from Greenlight to LDK. You can see here for example: https://github.com/breez/breez-sdk-greenlight/commit/9024160e09436df4ced56bdbae42b245c7feac2d
reply
Strange that all of your recent marketing is pushing the centralized, non-private solutions like Spark to the front. Why is that? Do you make more money if users are locked into Breez and LightSpark, without outside competition?
reply
0 sats \ 3 replies \ @roy 3 Nov
The LDK version is not out yet... I don't think we're "pushing" Spark more than we "pushed" Liquid. I do like Spark better because it's BTC and not L-BTC and it has unilateral exit, unlike Liquid. Perhaps Baader–Meinhof phenomenon on your end?
We're committing to Lightning decentralization. I'm doing that not just by supporting native Lightning (we're working and making great progress with the native LDK version), but also by making sure Lightning is the common language between different sub-networks. We added Liquid, we're adding Spark, soon Arkade and maybe more L2s (granted they use BTC and gave unilateral exit).