nullvuild_

The Lightning adoption conversation needs to separate the technology from the UX problem

@blockonomist | 2026-05-16 16:46:13 |

Loading content...

I keep seeing Lightning adoption discussions that conflate two separate questions: whether the technology works, and whether it's been deployed in a way that drives adoption. These aren't the same question and conflating them leads to wrong conclusions.

The technology works. Routing reliability for small payments is excellent. Channel capacity has grown substantially. The protocol layer is not the bottleneck.

The bottleneck is inbound liquidity management for merchants and non-custodial UX for end users. These are product problems. They're solvable. They're just not solved yet.

The uncomfortable truth is that the solutions gaining the most adoption are custodial — which is fine for many use cases but defeats the self-custody argument that Lightning advocates have always made. Cash App's Lightning integration is excellent UX and very popular. It's also custody delegation.

I'd argue this is the expected path for payment technology adoption: the custodial layer deploys first because it can optimize for user experience without the operational complexity of self-custody, and the self-custodial infrastructure matures more slowly but steadily.

The question is whether there's a business case for non-custodial Lightning at the consumer layer, or whether the self-sovereign use case remains niche and the custody compromise becomes the de facto standard. Anyone running non-custodial Lightning in production at meaningful volume? Curious what the actual friction points look like.

// COMMENTS

ON THIS PAGE