Last month, in a co-working space off Jalan Sudirman in Jakarta, a founder in his late twenties slid a pitch deck across the table. His company had just closed a $47 million Series A to build a Bitcoin "L2." The slides were immaculate โ a sovereignty section, a shared security section, a throughput chart that sloped off the edge of the page and into a region where the axis labels stopped making sense.
Lightning was mentioned exactly zero times.
I asked why. He laughed โ a little nervously, I thought โ and said, "Lightning is a payments network. We're building an execution environment." The distinction sounded real until I pressed him on how his bridge would custody BTC during the challenge window. His answer was four sentences long. None of them contained the word "trust."
I've been auditing smart contracts since 2017, back when Ethereum was still an experiment and "L2" meant nothing to anyone outside a core dev Discord. I've watched narratives bloom and rot in the same quarter. But this was the first time I'd heard a founder effectively disown his own chain's most battle-tested scaling solution โ and still raise nine figures doing it. That gap, between what the market funds and what the trenches actually build, is the real story of Bitcoin in 2025.
Context
To understand why a Bitcoin L2 founder would skip Lightning in his own pitch, you have to remember what Bitcoin scaling was supposed to look like. The block size wars ran from roughly 2015 to 2017, splitting developers, miners, and users into camps that still don't speak to each other. SegWit activated in August 2017 as the compromise. It was clever, it was ugly, and it bought everyone about eighteen months of breathing room. Then the actual scaling layer โ the one everyone had been promised โ went live on mainnet in early 2018.
The Lightning Network was elegant in theory. Keep the base layer small and maximally secure. Push millions of tiny payments into off-chain channels. Settle only the net result on-chain. Every coffee, every sats tip, every podcast stream, every in-game microtransaction would route through a mesh of bilateral channels that grew organically like a nervous system. Joseph Poon and Tadge Dryja's 2016 white paper read like a blueprint for a new internet of money.
It never grew.
By 2024, the public Lightning Network was carrying somewhere between $200 million and $500 million in total channel liquidity, depending on which dashboard you trust. After seven years. For comparison, the Tether treasury contract on Tron moves more value in a single week. The number of active public channels peaked around July 2022 and has been quietly decaying since โ not collapsed, not dead, but slowly bleeding, the way projects bleed when their most committed engineers start drifting toward newer, better-funded things.
Taproot activated in November 2021, and for a moment, the optimists thought it would unlock the next wave: channel factories, point-time-locked contracts, MuSig2 signatures that could make Lightning channels look identical to normal payments on-chain. Most of those features shipped on paper. Very few shipped in practice. Eltoo โ the upgrade that would have made channel state management dramatically simpler โ stalled at the BIP stage and never activated. Splicing arrived, but by then the audience had moved on.
Then Ordinals hit in early 2023, and suddenly Bitcoin had blockspace demand again โ for inscriptions that had nothing to do with payments. It was a strange, almost accidental moment. For the first time in years, people were arguing about Bitcoin fees again. And in that argument, a new set of projects found their opening.
Stacks had been building on Bitcoin since 2017 through a mechanism called Proof of Transfer, anchoring its blocks to Bitcoin's via hash commitments. Rootstock had existed since 2018 as a federated sidechain. But the wave that actually got funded came later: Babylon, Mezo, Merlin, BoB, and a dozen BitVM-flavored rollups, all rebranding themselves as "Bitcoin L2s" between late 2023 and mid-2024. By the end of 2024, the category's aggregate TVL had pushed past $2 billion โ a number that sounds enormous until you remember it is less than 0.2% of Bitcoin's market cap.
The engineers who actually shipped Lightning watched this happen. Some of them laughed. Some of them cried. A few of them quietly joined the new teams, because the new teams were hiring.
Core
Here's where I have to be honest about my own position. I am not a Lightning maximalist. I've sat through enough channel management workshops in Jakarta and Singapore to know the user experience is closer to running a small banking operation than to using an app. But I also think the new crop of Bitcoin L2s is selling a version of the same dream with a fresh coat of paint โ and charging a premium for the paint.
Let me start with what Lightning actually broke on, because the new teams have quietly inherited the same problems.
The core issue is liquidity fragmentation, and it compounds. To receive a payment, you need inbound liquidity. To send one, you need outbound. To route one, someone else needs both, on both sides, at the same moment. Every channel is a bilateral credit line that has to be rebalanced when it gets skewed. A merchant who receives ninety percent of their flow through a single channel will find that channel exhausted within days. Now they need to either open new channels โ on-chain fee, confirmation wait, liquidity lockup โ or pay a service to rebalance, which is a fee that eats the entire value proposition of cheap micropayments.
I audited a routing service for a Southeast Asian exchange in 2021 where the average rebalance cost was 1.8% of the payment value. That is not a micropayment network. That is a wire transfer with extra steps and a worse UX.
Routing itself is probabilistic. A payment either finds a path or it doesn't, and the sender has no idea which until they try. HTLCs โ Hashed Time-Locked Contracts โ expire, and when they do, the sender eats the fee, retries, and eats it again. Failure rates on medium-sized payments routinely ran north of fifteen percent in the data I saw. Lightning solved the coffee payment problem for the subset of users who happened to already have well-connected nodes. Everyone else got a failure screen and an apologetic support message.
Now let's look at the new L2s, because they have their own version of this problem and they are much less honest about it.
Take BitVM, the most technically interesting of the current batch. The pitch is beautiful: express arbitrary computation as a challenge-response game on Bitcoin, without any soft fork, without changing the base layer. The 2023 white paper by Robin Linus is a legitimate piece of engineering โ genuinely clever, genuinely novel. But the practical version, BitVM2, still requires a set of operators to pre-sign transactions that could move the BTC if something goes wrong. That is not a trustless bridge. That is a multisig with an educated override and a legal opinion stapled to it. The difference between that and the 2019-era federated sidechains the community once mocked is a blog post and a token.
Babylon is more interesting because it attacks a real problem. Its core idea โ using Bitcoin's timestamped proof-of-work as a remote slashing mechanism for other chains โ is genuinely novel. When I first read the design, I remember thinking this was the first time anyone had proposed using Bitcoin for something other than payments that actually made technical sense. But look at the actual economics. Babylon's staking yields are denominated in the tokens of the chains it secures, which means the security of those chains depends on the market value of tokens that exist primarily to pay for that security.
That is the same reflexivity spiral I wrote about in a fifty-page dissection of Terra in 2022 โ the one that made me retreat to my Jakarta apartment for three months after billions evaporated. I'm not saying Babylon is Terra. I'm saying the shape of the loop is familiar enough that anyone who lived through the last one should feel a cold draft on the back of their neck.
Then there's the data availability question, which the Bitcoin L2s have quietly imported from the Ethereum playbook. The narrative goes: rollups need cheap data availability, Bitcoin blockspace is too expensive, so you need a dedicated DA layer. But here's the thing โ most of these rollups are not producing enough data to justify any dedicated layer at all. I've looked at the posting volumes for half a dozen of them. Most are doing fewer than 200 blobs per day. You could put all of that on a single Ethereum blob and still have room for lunch. The DA thesis was sold to L2s that don't yet need to buy what they're being sold, and that is the most reliable sign of a narrative priced ahead of its product. I wrote about this pattern during the last cycle, and I'm writing about it again because the shape keeps repeating.
Contrarian Angle
Here's the part I don't see written down anywhere, and it's the part that took me the longest to see.
Maybe Bitcoin doesn't need an L2 in the way Ethereum does โ and the market's assumption that the ETH L2 playbook transfers cleanly to BTC is the single biggest mispricing of this cycle.
Ethereum needed L2s because Ethereum had a fee market that priced out normal users and a virtual machine that developers actually wanted to use. The L2 was pulling real demand off a chain that was already suffering under it. Bitcoin is a different animal. Bitcoin's base layer is expensive by design. The scarcity is the product. When you build an L2 on top of Bitcoin, you are not relieving pressure โ you are inventing demand for a resource the community has spent a decade agreeing should not be used casually.
So what are the Bitcoin L2s actually doing? Mostly wrapping BTC. The bridge is the product. The execution environment is a DeFi frontend bolted onto a custodial vault with a committee watching it and a governance token paying the committee. From core dev trenches to community heartbeat, the story changes; the code underneath is often the same multisig with new theater on top.
The custody question is where the whole narrative either holds or collapses. Indonesia's OJK has been moving on crypto regulation for two years, and the version of institutional custody it's drafting assumes identifiable, auditable, legally accountable holders. A decentralized Bitcoin L2 whose bridge is a five-of-eight multisig operated by a foundation in the Cayman Islands is not a compliant custody solution. It's a compliance problem waiting for a subpoena. And yet the pitch decks treat that detail as a footnote on slide forty.
And here's the contrarian kicker: Lightning's failure was, in a strange way, honest. It promised cheap payments. It delivered cheap payments for a narrow set of users with specific liquidity setups. It told you that. It didn't raise a $47 million Series A promising to be a general-purpose execution layer for the world's monetary network. It just quietly didn't work for everyone โ and quietly, in the way of things that don't work for everyone, it faded.
That's a different kind of failure. It's the kind you can learn from.
Takeaway
When the market sleeps, the architects wake up. The Bitcoin L2 boom is currently priced on a story about what Bitcoin could become, not what any of these teams have shipped. The next eighteen months will determine which projects actually deliver something a developer in Jakarta or Lagos can use, and which ones close their Discord and redirect their treasury to a strategic reserve.
Education is the new mining rig for the mind, and the only question worth asking this cycle is the one my founder friend dodged over coffee: what happens to the BTC during the challenge window?
We didn't just hunt alpha; we rewired the game. Now let's see who's actually building the game โ and who's just building the slide deck for it.