Michael Saylor just drew a line in the sand. No more changes to Bitcoin. Ever. In a thread posted on April 23, 2025, the MicroStrategy chairman expanded his opposition from the BIP-110 block size debate to a blanket rejection of covenants, larger blocks, and any base-layer modification. He compared the Bitcoin codebase to a constitution—arguing that altering it is a 'constitutional offense' and an attack on holders' 'economic rights.'
The bytecode didn't lie. But Saylor did—by omission.
Let's examine the technical reality behind his absolutist stance. I've spent nine years dissecting Layer 1 protocols, including two deep audits of Bitcoin Core's script language for institutional compliance. Here's what Saylor doesn't tell you.
Context: Bitcoin's Governance Machine
Bitcoin has no formal voting. Governance happens through BIPs (Bitcoin Improvement Proposals), miner signaling, and node operators running specific clients. Since 2017's SegWit activation, the community has operated under an informal 'soft fork only' rule—backward-compatible changes that don't force upgrades.
Taproot (2021) was a soft fork that introduced Schnorr signatures and MAST. It didn't change Bitcoin's monetary policy or security model. It reduced transaction size and improved privacy. The network upgraded smoothly. No constitutional crisis.
But now Saylor is painting all future upgrades with the same brush—including covenants. Covenants are not block size increases. They are smart contract primitives that constrain how coins can be spent. Example: a covenant can require that funds only move to addresses with certain properties, enabling vaults that prevent theft if a key is compromised.
Core: Code-Level Deconstruction of Saylor's Argument
Saylor's thread conflates three distinct types of changes:
- Macro-parameter changes (block size, block time, supply cap). These affect Bitcoin's fundamental 'sound money' properties. I agree: altering the 21 million cap or doubling block size without community consensus would be dangerous.
- Security fixes (bug patches). Rare but necessary. In 2018, Bitcoin Core patched CVE-2018-17144—a denial-of-service vulnerability that could crash nodes. No one called that a constitutional violation.
- Script improvements (covenants, OP_CAT, opcode additions). These are what Saylor now opposes universally. He claims they introduce 'complexity' and 'attack surface'.
Let's examine covenants specifically. The BIP-119 (CTV) covenant proposal allows a transaction output to specify exactly how the coins can be spent. This enables trustless vaults, congestion-controlled channels (like improved Lightning), and more efficient Layer 2 constructions.
From a code audit perspective: - CTV requires only ~50 lines of consensus code addition. - It does not expand the scripting language's computational power. It adds a single opcode that checks a hash of spending conditions. - The security model is identical to the current Bitcoin script—no new attack vectors beyond what already exists for hash commitments.
During my audit of a Bitcoin L2 project last year, I traced a vulnerability directly to the absence of covenants. The team had to implement a multi-sig workaround that introduced centralization. Covenants would have solved the problem with atomic trustlessness. Saylor's blanket opposition effectively forces projects to use inferior, riskier alternatives.
He also ignores that Taproot itself was a base-layer change. Why was it acceptable? Because it didn't threaten the 'sound money' narrative? The inconsistency reveals that Saylor's position is not technical—it's ideological.
We didn't ask for this fork. But Saylor is declaring war on upgrade paths. And in doing so, he's creating a different risk: ossification.
Contrarian: The Blind Spots of Immutability
Saylor's 'constitution' analogy is compelling but flawed. Real constitutions have amendments. The US Constitution has 27. Bitcoin's 'constitution' is a set of functions in C++. It can be changed safely through soft forks that maintain backward compatibility.
The contrarian angle: Saylor's zero-change stance may be the biggest threat to Bitcoin's long-term viability.
Consider quantum computing. While large-scale quantum attacks on ECDSA are not imminent, they are a credible long-term threat. Bitcoin will eventually need to transition to quantum-resistant signatures. That requires a base-layer soft fork. If Saylor's dogma becomes community orthodoxy, the network may be unable to adapt—leading to a catastrophic loss of funds.
Second: the liquidity fragmentation in Layer 2s. Lightning Network adoption is plateauing. One reason is the limited ability to construct complex channels. Covenants would enable 'eltoo'—a simplified channel construction that eliminates the need for penalty mechanisms. Without covenants, Lightning remains fragile and channel liquidity is constrained.
Saylor's 'economic rights' framing is also self-serving. MicroStrategy holds ~226,000 BTC. Any change that broadens Bitcoin's utility could increase its market cap—but it could also dilute the 'store of value' narrative that props up the current valuation. Saylor has a massive position bias. He benefits from a frozen Bitcoin.
Third: he ignores the regulatory angle. The SEC has argued that Ethereum's transition to proof-of-stake was a 'centralizing upgrade' but did not declare it a security. Bitcoin's lack of ability to upgrade could actually become a regulatory liability—if the network cannot fix bugs or comply with future legal requirements, regulators might classify it as an 'incomplete product' rather than a mature asset.
Takeaway: Vulnerable to Its Own Success
Saylor's thread will not halt Bitcoin development. Core developers have already moved forward with OP_VAULT (another covenant proposal) and are testing BIP-119. But his influence on institutional sentiment is real.
The real vulnerability isn't technical—it's governance inertia. If every upgrade becomes a constitutional battle, Bitcoin will ossify. And in a world of fast-moving smart contract platforms, ossification may not be a feature. It may be a bug.
Volatility is noise. Architecture is the signal. But an architecture that cannot evolve is a brittleness, not a strength. The bytecode didn't lie, but Saylor's interpretation does.
We didn't ask for this ideological hard fork. We asked for upgrade paths that preserve what Bitcoin is while allowing it to become more secure and useful. That choice is still open—but only if the community looks past the throne-holder's fear and reads the actual code.
