The numbers surged, but the room felt empty. Over the past 6 months, 47 new projects have rebranded as "Bitcoin Layer 2" on their websites and pitch decks. TVL across these protocols hit $1.2B in March, according to DeFi Llama’s Bitcoin L2 category. But when I probed the smart contracts of the top 10 by TVL, I found something unsettling: 8 of them are EVM-compatible, with bridge implementations that rely on Ethereum-style multi-sig governance. The soul of Bitcoin—simplicity, self-custody, and proof-of-work finality—was replaced by a ghost of Ethereum.
When the graph spikes, the soul remains quiet.
Let me back up. In 2017, during the Gitcoin Grants days, I manually audited quadratic voting contracts for public goods. I believed then that code could enforce fairness. That belief is now battered by a wave of marketing tricks. The current narrative—"Bitcoin L2 will unlock DeFi for HODLers"—sounds beautiful. But the technical reality is ugly. These projects are not building on Bitcoin’s UTXO model or using its security. They are deploying Solidity contracts on centralized sidechains, slapping a BTC ticker, and calling it a Layer 2.
To understand why this matters, you need to see the difference between true Bitcoin scaling (like Lightning Network) and the impostors. Lightning is a real L2: it uses Layer 1 transactions only for channel open/close, preserves the base layer’s security model, and doesn’t introduce a new token. The impostors, on the other hand, rely on a bridge operator that holds custody of BTC. They then mint a pegged token (e.g., “BTC.b,” “tBTC,” “SBTC”) on an Ethereum-compatible chain. The peg is often a multi-sig with 3/5 or 4/6 signers. This is not trust-minimized; it’s a bank.
Based on my audit experience from the Uniswap v2 liquidity mining crisis, I learned that incentive structures determine behavior. When a project’s tokenomics reward speculation over utility, the outcome is bubbles and exit scams. The same pattern is playing out in these Bitcoin L2s. They attract TVL by promising 30%+ APY on “BTC deposits.” Where does the yield come from? Mostly from native tokens printed for the liquidity mining program, or from lending pools that lend to leveraged traders. When the market turns, the BTC deposits are stuck. I’ve seen this cycle in DeFi Summer 2020, in Terra/Luna 2022. The mechanics are identical, just wrapped in a Bitcoin narrative.
So let’s dissect the technical claims of the top three pretenders.
Project A: The “Bitcoin Rollup” that isn’t. It advertises a ZK-rollup that settles on Bitcoin. But a real ZK-rollup requires the L1 to verify the proof. Bitcoin’s script language cannot verify a Groth16 or Plonk proof today—the opcodes don’t exist. You can use BitVM, but that’s a computational trick that still needs a fraud proof challenge period, and only a few projects (like Bitlayer) are genuinely exploring it. Project A’s “ZK-rollup” is actually a proof that is posted on Bitcoin as data (via OP_RETURN), but the actual verification happens on a separate validator set that is off-chain. That’s a validity proof, but not a rollup—it’s a sidechain with a cosplay.
Project B: The “RGB+Taproot” rebrand. It claims to use client-side validation (RGB) and Taproot assets. In reality, the protocol stores asset state in an ORACLE database off-chain, and the Bitcoin transaction only commits a hash of the state. The official RGB specification does not support smart contracts, but Project B built a Solidity-like virtual machine on top. That’s fantastic engineering—but it’s not Bitcoin. It’s a custom consensus on a separate network that uses Bitcoin as a timestamp server. That’s no different from Ethereum’s Beacon chain checkpointing to Bitcoin? No, it’s not. Ethereum already does that without calling itself Bitcoin L2.
Project C: The “EVM-compatible Bitcoin sidechain.” This is the most honest in terms of technology—they admit it’s a sidechain. But their marketing says “Bitcoin L2.” The bridge is a federated 2-way peg with 15 validators. Historical examples of federated pegs (Liquid Network, RSK) show that they can work, but they are custodial. The real Bitcoin community (developers on bitcoin-dev, core mailing list) has consistently said:
“If you need smart contracts, use Ethereum. Bitcoin is for sound money.”
That quote is from a 2023 Bitcoin Core contributor. Yet the market is allocating billions to these pseudo-L2s.
Why does this happen? I think it’s due to a combination of desperation for yield and narrative capture. The Bitcoin ecosystem has long struggled to produce DeFi yields. HODLers want to “put their BTC to work.” Projects exploit this desire. Additionally, VCs are eager to fund “Bitcoin L2” because the ticker “BTC” brings instant liquidity on centralized exchanges. It’s the same playbook from the 2021 alt-L1 boom: wrap a new chain in a familiar name.
But there is a contrarian angle worth exploring: maybe some of these projects are genuinely useful even if they aren’t Bitcoin L2s. They could offer a sandbox for experimenting with DeFi on a secure (though not Bitcoin-level) asset. The question is: should they be allowed to call themselves “Layer 2”? I argue no. Misleading nomenclature harms the entire industry. It confuses regulators, inflates expectations, and eventually leads to a crash when people realize the security promise is fake. In 2025, after the Terra collapse, we promised to be more honest. Yet here we are again.
During the Nifty Gateway ethical stand, I learned that large companies will sacrifice creator rights for short-term profits. The same dynamic is at play here: projects sacrifice technical accuracy for fundraising.
So what should a real Bitcoin L2 look like? Let me give you a framework that I developed after months of introspection post-Terra. A true L2 must satisfy three conditions:
- Settlement on Bitcoin: The L2 state must be provable on Bitcoin’s base layer with full security (no trusted third party). This means either using Bitcoin’s script to verify a proof (via BitVM or a future OP_CAT upgrade) or using Lightning’s HTLC/PTLC for state transitions.
- No new trust assumptions: The bridge must be trustless—either using LN or a futuristic BitVM bridge that doesn’t require federated signers. The current federated pegs are bridges, not L2s.
- Native BTC as gas: The L2 must use BTC for fees, not a new token. If it has a new token for gas or governance, it’s a separate chain, not Bitcoin’s L2.
By this definition, only Lightning Network and a few experimental projects (like Bitlayer, which is building a BitVM-based rollup) qualify. The rest are “Bitcoin-tied sidechains” at best.
Here’s a hidden truth: many of these projects are actually Ethereum scaling projects that pivoted after Ethereum’s L2 space became overcrowded. I’ve spoken to developers from one of the top 10—off the record—who admitted: “We just changed the token from ETH to BTC in our white paper. The contract is the same.” If you inspect the bridge code, you’ll find references to IERC20 and WETH9 patterns. The Bitcoin community would never approve this.
I’m not against innovation. I’m against dishonesty. If you want to build a DeFi chain with a Bitcoin peg, call it a “Bitcoin peg zone” or a “sidechain.” Don’t steal the prestige of Bitcoin’s Layer 2 concept—a term that took years to build trust.
Looking forward, I expect regulatory pushback. The SEC has already signaled interest in classifying certain “Bitcoin L2” tokens as securities because they fail the Howey test when the bridge is custodial. That will trigger a wave of delistings in 2026. Meanwhile, the real Bitcoin L2 space will advance slowly through protocol upgrades (like OP_CAT) and incremental improvements to Lightning. The hype will fade. The quiet builders will remain.
The graph spikes. The soul stays quiet.
For builders reading this: before you add “Bitcoin L2” to your website, ask yourself whether you are honoring the principles of the only decentralized censorship-resistant base layer. Or are you just adding a label to raise money? The market will eventually uncover the truth. As I tell every team I consult for: “Trust, not code, is the final currency.”