Hook
Last week, a protocol claiming to be a “Bitcoin Layer 2” announced a $20 million TVL on its launch day. The team’s website boasted “native Bitcoin security” and “trustless peg” – language that sounded like a savior for the oldest blockchain. But when I dug into their codebase, I found something familiar: a fork of the Optimism OP Stack, wrapped in Bitcoin-themed branding, with a multisig bridge that required 3-of-5 signatures from a team that had never publicly audited their smart contracts. The TVL wasn’t Bitcoin; it was a wrapped ERC-20 token on Ethereum that had been bridged to their chain. The only “Bitcoin” involved was the name. This is not an outlier. It is the norm. And it is the most dangerous trend in the crypto ecosystem today: the parasitic rebranding of Ethereum-centric infrastructure as “Bitcoin Layer 2” to capture the hype and liquidity of the original cryptocurrency.
Context
The Bitcoin community has long dreamed of scaling the base layer. Since the Lightning Network’s inception in 2018, there has been a relentless pursuit of trustless, off-chain solutions that preserve Bitcoin’s core principles: decentralization, sound money, and permissionless access. The recent surge of interest in “Bitcoin Layer 2” solutions – spurred by the Ordinals boom and the ETF approval – has brought a flood of new teams claiming to deliver the holy grail. But here’s the uncomfortable truth that no one wants to say out loud: 90% of so-called “Bitcoin Layer2s” are Ethereum projects rebranding for hype, and the real Bitcoin community doesn’t acknowledge them.
I’ve spent the past three years auditing cross-chain bridges and scaling solutions as a Decentralized Protocol PM in Nairobi. I’ve seen the code. I’ve read the whitepapers. And I’ve watched the same pattern repeat: a team takes an existing Ethereum Layer 2 architecture (usually an optimistic rollup or a sidechain with a centralized sequencer), slaps a “Bitcoin” logo on it, and calls it a breakthrough. The deception isn’t malicious – many of these teams genuinely believe they are building on Bitcoin because they use a Bitcoin-backed token as collateral. But they miss the fundamental difference: Bitcoin is not just a settlement layer; it is a cultural and security model that cannot be emulated by a fork of Ethereum’s code.
Core
Let’s do a technical autopsy. I’ll use the most common architecture: a “Bitcoin L2” that uses a bridge to lock BTC on the main chain and mint a representation on the L2. The critical question is: how is the bridge secured?
In a true Bitcoin second layer, like Lightning, the security is derived from Bitcoin’s own consensus. Lightning channels are enforced by Bitcoin scripts – you can always close the channel and retrieve your funds on-chain if the counterparty cheats. There is no third party, no multisig, no oracle. Now compare that to the “Bitcoin L2” that launched last week. Their bridge uses a smart contract on Ethereum to hold the wrapped BTC. Wait, what? They claim to be a Bitcoin L2, but their peg mechanism lives on Ethereum? That’s because they couldn’t deploy a Turing-complete smart contract on Bitcoin (which doesn’t support it). So they took the easy route: use Ethereum as the settlement layer for the Bitcoin peg, then bridge that to their own chain. The result is a three-layer stack: Bitcoin → Ethereum → Their L2. The security of your Bitcoin is now dependent on Ethereum’s consensus, and the Ethereum bridge’s multisig. That’s not a Bitcoin L2. That’s an Ethereum L2 that uses Bitcoin as a reserve asset.
I’ve traced the code of five such projects over the past six months. Every single one of them had a bridge that relied on a validation committee – a set of trusted signers – to approve withdrawals. In one case, the committee was a single key controlled by the CEO. In another, the committee was a quorum of three founders. The whitepapers talked about “decentralized security” and “trustless pegs,” but the actual implementation was a glorified multisig. The bear market didn’t kill these projects; it just exposed their fragility. When the price of BTC dropped, the TVL in these chains plummeted, and the withdrawal queues grew. Users found that their “Bitcoin on L2” was stuck because the signers went offline. The irony is thick: they chose a “Bitcoin L2” to avoid the risks of centralized exchanges, only to end up with a more opaque version of the same.
Now, let’s talk about the cultural dimension. The real Bitcoin community – the cypherpunks, the HODLers, the Core developers – has a specific set of values: maximalism, security, and distrust of novelty. They don’t want a “Bitcoin L2” that uses zero-knowledge proofs because they don’t trust the ZK complexity. They don’t want a “Bitcoin L2” that uses Ethereum’s EVM because they see it as a dilution of the original vision. The community has a term for these projects: “shitcoin wrappers.” I remember attending a Bitcoin meetup in Nairobi in 2023, where a developer presented a pitch for a “Bitcoin sidechain” that would enable smart contracts. The room was silent. Then a Core contributor stood up and said, “If you want to build on Ethereum, go build on Ethereum. Don’t try to steal our brand.” That sentiment is widespread. The real Bitcoin community doesn’t acknowledge these L2s because they are not built on the same principles. They are built on convenience and hype.
Contrarian
But here’s the contrarian perspective: am I being too harsh? Could it be that these “Bitcoin L2s” are actually a necessary evolutionary step? Perhaps the Bitcoin community’s purism is holding back innovation. The Ordinals experiments showed that Bitcoin can be used for more than just payments – but that required a controversial change (the Taproot upgrade). If we accept that Bitcoin’s base layer is limited, then maybe we need these hybrid solutions to unlock value. After all, Ethereum’s L2 ecosystem is thriving because it accepts that scaling requires trade-offs. Why can’t Bitcoin do the same?
I’ve spent a lot of time thinking about this. I’ve even built a prototype of a “Bitcoin L2” myself during a hackathon in 2024 – using a federated peg with a signer set that included Bitcoin Core nodes. The project was a technical success but a cultural failure. The Bitcoin community rejected it because it introduced a trust assumption. That experience taught me that the Bitcoin community’s resistance is not irrational; it’s a feature. Bitcoin’s value proposition is its simplicity and immutability. Every time you add a layer, you add complexity, and complexity is the enemy of security. The Ethereum community is comfortable with complex layered architectures because they accept that innovation requires risk. The Bitcoin community is not. So when a project claims to be a “Bitcoin L2” but uses Ethereum’s security model, they are trying to have it both ways – and they usually fail at both.
Takeaway
So what does this mean for the reader? If you are a holder of Bitcoin, be skeptical of any “L2” that requires you to trust a bridge, a multisig, or a token that isn’t native to Bitcoin. The real Bitcoin L2s are few: Lightning, Liquid (with its federated peg), and maybe some experimental drivechains. Everything else is a marketing stunt. As a builder, I see a clear path forward: stop trying to replicate Ethereum on Bitcoin. Instead, focus on what Bitcoin does best – trustless settlement – and build tools that enhance that, not replace it. The bear market has cleaned out the hype; only the grounded projects survive. We don’t need a hundred Bitcoin L2s. We need one that actually works without asking us to trust anyone. Until then, I’ll be here, auditing the code, and calling out the mirages.
