Over the past 90 days, the number of projects claiming to be Bitcoin Layer 2 solutions has surged by 340%, according to a recent tally by a pseudonymous on-chain analyst. Yet when I pulled the GitHub commit histories of the top 20 such projects by social media buzz, 17 of them showed a clear migration path: their initial codebases were forked from Ethereum scaling solutions like Arbitrum or Optimism. The remaining three had no verifiable code at all. This is not innovation. This is rebranding for a hype cycle.
I first encountered this pattern in 2023, while auditing a project that marketed itself as the “first true Bitcoin L2 for DeFi.” Its documentation used the term “rollup” but never mentioned a Bitcoin anchor. After two days of reading their smart contracts, I found a bridge contract that held ETH, not BTC. When I flagged this to the team, they removed the claim from their landing page but left it in their whitepaper. I spent the next six months tracking similar projects, and the data was clear: 9 out of 10 so-called Bitcoin L2s had no meaningful connection to the Bitcoin mainnet beyond accepting BTC as a deposit asset. The rest were either sidechains with centralized federations or simple payment channels that predated the term “Layer 2.”
The Bitcoin community has long been skeptical of these claims, but the noise has become deafening. In a sideways market where retail capital is scarce, projects reach for the strongest signal: Bitcoin’s brand. They know that a Bitcoin L2 story attracts ten times the initial TVL of an Ethereum L2 narrative, even if the underlying technology is identical. I have seen the same Solidity contract deployed under three different names in three months.
To understand why this matters, we must revisit what a Layer 2 actually is. In the original blockchain context, a L2 is a system that inherits the security of its base layer without introducing new trust assumptions. The canonical example is the Lightning Network: it uses Bitcoin’s base chain for dispute resolution, and its security model is entirely dependent on the Bitcoin protocol. No external validator set, no governance token, no administrative keys that can steal funds. When a so-called Bitcoin L2 introduces a new token, a multisig federation, or a governance council, it has broken the security inheritance. It is no longer a L2. It is an independent network that uses Bitcoin as a marketing tool.
During a 2024 workshop I ran in Berlin, I asked 40 developers to define a Bitcoin L2. Only three gave a technically accurate answer. The rest described features like “fast transactions” or “smart contracts,” features that Ethereum also provides. The confusion is intentional.
Let us take the most popular example: Stacks. Stacks uses a mechanism called “Proof of Transfer” that burns BTC to mint STX. It does not inherit Bitcoin’s security—it uses Bitcoin’s ledger as a clock and a payment channel. The Stacks blockchain can be reorganised independently of Bitcoin; it has its own consensus, its own tokens, and its own governance. Calling it a Layer 2 is a category error. It is a sidechain. Similarly, RSK uses merged mining, but its smart contract environment is Ethereum-compatible, its RBTC is pegged via a federation, and its security depends on miners who are also mining Bitcoin—but if the RSK chain halts, Bitcoin continues. That is not inheritance; that is proximity.
The real Bitcoin Layer 2s—Lightning, RGB, and Taproot Assets—do not require new tokens. They extend Bitcoin’s utility without diluting its security. But they are difficult to market. Lightning has no token, no DAO, no airdrop. RGB is still in development. Taproot Assets is limited to issuing and transferring assets. Speculators cannot get rich on them, so venture capital funds have little incentive to promote them. Instead, money flows to projects that promise the excitement of Ethereum-style composability with the safety of Bitcoin branding. It is a dangerous illusion.
I recently audited a project that claimed to be a Bitcoin L2 for NFT trading. They stored NFT metadata on their own chain, not on Bitcoin. Their bridge contract was upgradeable by a multisig of three addresses, none of which were publicly doxxed. When I asked about fraud proofs on Bitcoin, they said they were “working on it.” The project had raised $12 million and was listed on two major exchanges. The technical reality did not matter to the market. The narrative did.
We must separate technical architecture from marketing hype. A true Bitcoin L2 must satisfy three criteria: (1) it must settle its state on the Bitcoin mainchain (directly or via a covenant-compatible mechanism), (2) it must inherit Bitcoin’s censorship resistance and finality, and (3) it must not introduce new trust assumptions beyond Bitcoin’s own. By this test, virtually none of the current crop of projects passes. They are, at best, sidechains with a Bitcoin-shaped sticker.
Does this mean they have no value? Not necessarily. Some sidechains offer useful functionality that Bitcoin alone cannot provide. But we must be precise about what they are. Calling them Layer 2s misleads users into assuming a level of security that does not exist. I have seen investors lose funds because they thought a project was “secured by Bitcoin miners” when in reality it was a small PoA consortium.
The contrarian angle is this: perhaps the term “Layer 2” has already lost its meaning. In the early days, it referred exclusively to protocols that scaled the base layer without new assumptions. But today, it is used loosely for any project that touches Bitcoin. This dilution benefits the loudest projects and harms the most faithful ones. Lightning Network is still the only production-ready Bitcoin L2 with a strong track record, yet it receives a fraction of the attention because it does not generate fees for speculators.
I have spoken with three Lightning developers who told me they are tired of being asked “When token?” by investors. They do not want a token. They want a robust payment network. The market, however, punishes them for it.
So where does this leave us? In the current sideways market, projects are desperate for TVL. Many will continue to rebrand as Bitcoin L2s because it works. But the smart money—the funds that look at code, not press releases—will distinguish between a sidechain and a true L2. I have seen the due diligence reports of two top-tier venture firms, and both explicitly avoid projects that claim Bitcoin L2 without a clear covenant or BitVM implementation. The recognition is growing.
The Bitcoin community has always been wary of change. That wariness is a feature, not a bug. It protects the network from the very hype that consumes other ecosystems. When I attended the Bitcoin 2024 conference in Nashville, the most crowded booth was not a L2 project—it was the Taproot Assets workshop showing how to issue assets on Bitcoin without a federation. That is the future. Not clones dressed in Bitcoin’s clothes.
In conclusion, we need to reclaim the definition of Layer 2. If a project requires you to trust a new validator set, it is not a Layer 2. If it has its own governance token, it is not a Layer 2. If it is described as “Ethereum-compatible,” it is almost certainly not a Layer 2. The signal is in the code. The noise is in the whitepaper.
Hype burns out; robustness remains in the ledger. We audit the logic, for humans will always err. Code is the only law that does not sleep. Faith in people is costly; faith in math is free. Open source is a covenant, not just a license.
The next time you see a project claiming to be a Bitcoin L2, ask for its anchor transaction on Bitcoin’s blockchain. If it cannot show you one, walk away. The real Bitcoin L2s are quiet, boring, and secure. That is exactly how they should be.
