We mined liquidity while the code slept. Now, Michael Saylor wants to keep it that way.
In his latest thread, the MicroStrategy chairman didn't just reject BIP-110 or covenants—he drew a line in the sand against all base-layer changes. Larger blocks, smart contract capabilities, even security-enhancing covenants: all are "constitutional offenses." All attacks on our "economic rights."
I've watched Bitcoin governance debates for nearly a decade. But this? This is different. Saylor isn't a developer. He's a capital allocator with billions in Bitcoin. His words carry weight. And his message is simple: change is theft.
Context: The Battle for Bitcoin's Soul
Bitcoin's governance is chaotic by design. No formal voting. No benevolent dictator. Just rough consensus and running code. The BIP process is our closest thing to legislation—proposals debated by core developers, signaled by miners, adopted by users.
For years, the debate centered on scaling: small blocks vs. large blocks. The Blocksize War ended with SegWit and a tacit agreement: keep base-layer minimal, push complexity to layers (Lightning, Liquid).
But Saylor's new thread goes further. It explicitly names covenants (complex scripts that could enable vaults, insurance, and anti-MEV protections) as threats. It attacks the very idea of upgrading post-genesis.
He argues that Bitcoin's value proposition is immutability itself. That any change—even a soft fork—dilutes the certainty that your 21 millionth coin will remain exactly that. In his view, Bitcoin is not a platform to be iterated upon. It's a monetary monument.
Core: The Data Behind the Dogma
I've audited enough code to know: immutability has a cost.
In 2017, I watched the Parity multi-sig hack drain 150,000 ETH. The vulnerability wasn't in a new feature—it was a call dependency exploit in the EVM. I spent two weeks reverse-engineering it, realizing that even "stable" contracts can hide fatal flaws.
But Bitcoin is different—or so we tell ourselves. Its codebase is battle-hardened. Yet every developer knows: there is no perfect software. Only well-tested software.
Here's what Saylor's analysis misses: security evolves. Threats evolve. Quantum computing, zero-day exploits in SHA-256, or even a viral bug in a widely-used wallet—these aren't hypothetical. They're eventual.
And when they happen, what happens if our governance is frozen by dogma?
The Data Points
- Saylor's thread has been viewed over 500k times, retweeted by major Bitcoin influencers.
- MicroStrategy holds 214,400 BTC (~$11B). His incentive is clear: maintain the narrative that Bitcoin is an unchangeable asset.
- Covenants, specifically BIP-119 (CTV), have been under review since 2019. They'd enable vaults to prevent theft, safer multi-sig, and even more efficient Lightning channels.
- Core developers remain divided. Some see covenants as safe and necessary. Others echo Saylor's fear: any new opcode creates attack surface.
But here's the contrarian truth: the lack of change is itself a risk.
Contrarian: The Immutability Trap
We rode the wave until it broke our boards. In 2022, I watched Terra's algorithmic stablecoin collapse in 72 hours. My portfolio lost 85%. Why? Because the code held—but the market didn't. The design assumed rational actors and infinite liquidity. No circuit breaker. No emergency stop.
Bitcoin doesn't have those problems—yet. But the principle stands: rigidity can kill.
Saylor's stance turns Bitcoin into a museum piece. Beautiful, yes. Priceless, yes. But unable to adapt. And in a world where Ethereum, Solana, and new L1s iterate weekly, stagnation is a competitive disadvantage.
Is that a bad thing? For digital gold, perhaps not. You don't need to upgrade gold. But gold doesn't have bugs.
What if a critical vulnerability is found in the Bitcoin Core client? A hostile state actor could exploit it before a fix is deployed. With Saylor's "no change" culture, a controversial fix might be stalled for months—enough time for chaos.
The real battle isn't between "change everything" and "change nothing." It's between smart, careful upgrades and reckless dogma.
Takeaway: The Fork Ahead
Saylor's words will rally the maxis. They'll attract institutional capital seeking a stable store of value. Price may rise. But the developer community is signaling:
We cannot work under a vow of stagnation.
If Bitcoin refuses to evolve—even to patch known risks—it may face a fork. Not a hard fork of protocol, but a fork in philosophy. One path leads to a living network. The other leads to a shrine.
Liquidity is just trust, digitized and leveraged. And trust requires that the code can breathe.
The market will decide. But I've learned one thing from 28 years in this industry: the one constant is change.
We traded hope for efficiency, then lost both. Let's not lose Bitcoin to its own purity test.
Let the code sleep no longer.