Is Lightning Still the Whole Scaling Story?
Lightning is still important. But recent sources suggest it's no longer sufficient — or the only answer worth taking seriously.
For a long time, "Bitcoin scaling" had a default answer: Lightning. That answer is still important, but recent sources suggest it is no longer sufficient. The discussion in early 2026 increasingly treats scaling as a family of approaches with different strengths: Lightning, Ark-style VTXO systems, bridge-heavy designs, covenant-assisted constructions, and other forms of liquidity organization.
That does not mean Lightning is obsolete. It means Lightning is no longer the whole map.
What changed in the conversation
The change is not that Lightning stopped mattering. It is that recent protocol design discussions are more comfortable naming multiple distinct bottlenecks: payment routing, liquidity management, trust minimization, batch coordination, and user-experience friction.
Once those bottlenecks are named separately, it becomes harder to pretend one architecture solves all of them equally well.
David Seroy (@david_seroy) of Alpen Labs, who is speaking at the 2026 MIT Bitcoin Expo, commented in this March 9 reply that certain Lightning ambitions remain unrealistic at scale, contributing to the growing view of Bitcoin scaling as a multi-approach portfolio:
"Many Lightning features that people want are very unrealistic at scale."
What recent sources are pointing to
Bitcoin Optech #395 is useful because it surfaces recent work around Ark-style VTXO verification. That is not "anti-Lightning" material. It is evidence that serious builders are working on adjacent or complementary structures.
The Delving Bitcoin channel-factory discussion around Ark shows why: not every scaling pain is fundamentally about routing payments faster. Some pains are about how liquidity is arranged and shared.
Even browsing the active Delving protocol-design category inside the window gives the same impression. Bitcoin scaling is now a portfolio of active ideas, not a one-word answer.
A better way to phrase the question
Instead of asking "what is the scaling solution?" it may be better to ask: which system best handles everyday payments? Which best handles shared liquidity? Which minimizes trust most effectively? Which stays legible enough for users and builders to adopt?
Where do you think our speakers each fall on the issue this year?