It’s…. Complicated, but basically the way they’re working around needing CTV is to do a big multisig with everyone. That requires a decent amount of “being online at the right time”, which maybe you can get lucky with on mobile but probably not.

LSP integration and closing the loop on things like 0FC, splicing, and async payments (all of which are in LDK 0.2, but gotta get broad support for some of them).

As the only person to have ever implemented both spillman channels and lightning, I can state confidently that adapting spillman channels to support HTLCs will result in something equally as complicated as lightning. You aren’t getting away from the challenges of lightning with spillman channels, sorry.

Oh of course also worth pointing out that for a mobile client to use an Ark it’s never going to be trustless without a soft fork as well. You can join a huge multisig if you’re a server and always-online, though (but you still need channels to make it scalable!)

> You do hodl your own keys with Ark, and those keys can exit unilaterally after one block (comparable to onchain levels of sovereignty, pluse state-chain security before that moment, which is less than a DryjaPoon channel but more than you can say onchain). Worth pointing out that Ark doesn’t materially “scale” without adding payment channels on top (ie Timeout Trees). Until that point, you’re really stuck with the statechain model, which has a highly-trusted third party, as you note. > In very high fee scenarios, unilateral exit is economically feasible for most amounts in Ark, but only for very high amounts in DryjaPoon channels. Huh? Ark is strictly more expensive to unilaterally exit than classic lightning. > Running your node is a bit orthogonal. It's just that an Ark client node on top of a L1 node is a trivial thing, unlike a node to manage DryjaPoon channels. Also huh? You’re comparing apples and oranges. Yes running a full routing node is complicated to manage, but having DryjaPoon channels in a wallet is not fundamentally complicated (see eg Phoenix). The second model (“client” to an LSP) is more comparable to Ark, and of course as mentioned above if you want scalable, trustless Ark you need payment channels anyway, so it’s strictly more complicated!

Only lightning. L1 isn’t practical in retail.

3% doesn’t sound like a lot, but at a 2x normal retail margin that’s a 6% increase in margin. With high retail costs that’s easily a 10-20% increase in profit! 3% on the retail price on everything you sell is *huge*! Talk to merchants. They’ll use it.

If you work on a project (like Bitcoin, but really any) and don’t use it, you’re missing out on the most valuable product feedback - experiencing it for yourself. I get it, Bitcoin often isn’t super easy to pay with everywhere so it seems like a low priority task to get yourself set up to only use infrequently, but even infrequent use is incredibly valuable feedback!

The annoying thing is Intel literally has logic in their memory controllers to fetch/store multiple pages for a single page load/write - embedded Alder Lake can use it to do ECC with normal memory. Yet they didn’t bother to use that here, instead opting for weak encryption to avoid the 10-20% performance overhead in most applications.

Sure, hyperbole :)

Bitcoin is going to zero if this fork activates. A few devs deciding it’s okay to seize people’s money just because they use the same feature as some spammers use isn’t even remotely bitcoin.

Yea sure, more competition in that space would be great, but i don’t think the issue is “more people need to run lightning nodes” or that that is hard, it’s trivial!

Have you tried Phoenix? “Running an LN node” is as easy as opening a mobile app these days.

😭😭😭

To my knowledge card purchase data (on an individualized level) isn’t sold to data brokers or even reported to credit bureaus. Aggregated and (barely) anonymized? Sure. The ability to request a full list of transactions someone does with just their social? This is a totally different level of crazy.

TIL in the US banks often share every transaction you make with third party credit reporting services (not the big three, ones dedicated to checking/savings account credit risk). You can view the report under the FCRA, but anyone can access your report (as long as they promise it’s to “provide services to you”).

It’s a Liquid wallet but they call it “self-custody”. Yes it has an option to withdraw to chain but come on… https://x.com/bullbitcoin_/status/1979202192075616348

Why on earth would you use or promote a wallet that lies to its users about how their funds are stored?