When you decide to talk tech, I'll start to listen. Incentives is what the make the world go round, it doesn't mean anything.

Do your own due diligence, don't give into the FUD

100%

I have a long discussion with Justin in another thread. Weak.

Not more powerful than code

You result to ad hominem when you have nothing serious to say.

Stick to your memes.

You're saying something I didn't say ("best L2"?) then calls me a lier?

My definition of L2:

Your definition of L2:

Lightning, like Spark or Ark, can also end up as a KYC network, so stop the BS. I don't see this risk. If you want to have serious technical discussion, I'm here. If you want to keep waving your hands - feel free.

Where's the lying?

I said you can run your own Spark. Their Spark has closed set of SOs, like Liquid has a closed set of operators and Arkade has one.

That's why I'm pushing everyone (Spark and Arkade) to implement confidential transactions (Spark has it in its roadmap). Liquid has it and we support it. That's why we'll keep pushing Lightning, bolt12, trampoline nodes and PTLCs. You're highly exaggerating the current privacy properties. Pure Lightning privacy isn't great to say the list...

Btw, you, Alby or Zeus could also provide a spreadsheet... A full one from rizful (custodial service) that contains amounts and destinations, and partial one from Megalith (forward history). The government doesn't need to send many emails to get the full picture... You don't like David Marcus, I get it, but you're not calling out pure Lightning players like Phoenix or other sub-networks like Arkade.

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).

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

It's unilateral exit. You don't need their permission to exit to the chain.

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.

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).

Same when an LSP goes down...

No, they will switch to a different sub network or native Lightning.

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).

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...