Michael Saylor: Bitcoin Code Is a Constitution, Changes Are Attacks on 'Economic Rights'

Michael Saylor has officially entered his philosopher-king era. The MicroStrategy chairman recently took to social media to drop a heavy thesis: the Bitcoin code isn't just software anymore. It is a digital Constitution. In Saylor's view, any attempt to alter the base layer of the protocol is no longer a technical debate; it is a violation of human and economic rights. This is a massive shift in rhetoric that should give every builder in this space a reason to pause.

The Argument for Code as Law

Saylor’s logic is straightforward, if not a bit rigid. He frames the original Bitcoin protocol as a finished product—a discoverable law of nature rather than a work in progress. By treating the software as a set of constitutional rules, he is setting a high bar for any proposal that tries to touch the foundation. To him, the fixity of the code is what gives Bitcoin its value as money. If we can change it, we can break it. If we can break it, we can devalue it. Under this lens, developers suggesting upgrades are not just innovators; they are seen as potential subversives threatening the property rights of everyone holding the asset.

This is a powerful narrative for institutional investors who want predictability, but it creates a complicated reality for those of us trying to build the next generation of financial infrastructure. If the constitution is finished, what happens to the engineers who see flaws or missed opportunities in the design?

The Covenant Controversy

The specific target of this latest round of skepticism is BIP-110 and the broader push for covenants. For the uninitiated, covenants are essentially scripts that allow for more complex conditions on how Bitcoin can be spent. Think of them as a way to enhance security—like a vault system where you can claw back transactions if a key is stolen, or restricted spending paths that prevent a malicious actor from draining a wallet in one go.

To many builders, covenants are the holy grail of Bitcoin security. They make the network more functional without relying on centralized third parties. But Saylor sees this as a slippery slope. His argument is that by introducing these complex rules at the base layer, we are opening the door to the same kind of technical debt and attack vectors that plague other blockchains. He is lumping covenants into the same bucket as the block size wars of the past. In his eyes, any move away from simple, pure transaction logic is a move toward instability.

The Builder’s Dilemma

As someone who spends my time talking to founders and engineers, I find this "constitutional" stance both helpful and incredibly frustrating. On one hand, Saylor is right about one thing: Bitcoin’s greatest strength is its resistance to change. If Bitcoin were as easy to update as a mobile app, it wouldn't be the world's most secure store of value. The friction is a feature, not a bug.

However, framing technical upgrades as attacks on economic rights feels like a way to shut down necessary discourse. If we treat the code as a sacred text, we stop being engineers and start being acolytes. For builders trying to solve real-world problems—like how to onboard the billions of people who can't afford mainnet fees or how to make long-term custody safer—the “never change anything” approach feels like a dead end.

The Risks of Stagnation

• Security Decay: If we don't adapt to new cryptographic threats, the "constitution" becomes a suicide pact.
• User Friction: Without improvements like covenants, Bitcoin remains a somewhat clunky tool for complex institutional custody.
• Developer Brain Drain: If the base layer is closed for business, the best minds will move to layers or ecosystems where they can actually innovate.

A New Type of Governance

What Saylor is really doing is establishing a new form of social governance. He is using his massive platform to signal to nodes and miners that they should default to "no" on any change. This is a protective measure for MicroStrategy's balance sheet, certainly, but it also reflects a deep-seated fear that Bitcoin's purity is its only defense against the traditional financial system.

By invoking the language of rights, he is raising the stakes. He isn't arguing against the technical merits of BIP-110; he is arguing that even discussing it is a threat to your personal freedom. It’s a brilliant PR move, but it’s a dangerous precedent for a technical community. If we replace peer review with political posturing, we lose the very thing that made Bitcoin a credible alternative to the legacy system in the first place.

The Layer 2 Escape Hatch

The likely outcome of this rigid stance is that all the innovation—the stuff developers actually care about—will be pushed to Layer 2 and beyond. If the base layer is a constitution that can’t be amended, then sidechains and lightning networks become the "states" where the real experimentation happens.

This is probably what Saylor wants. He wants the base layer to be the slow, heavy, immovable foundation of global finance. But builders should be wary. Relying entirely on upper layers for security and functionality often introduces trust assumptions that the base layer was designed to eliminate. If we can't make Bitcoin better at its core, we are essentially building a skyscraper on a foundation that we are never allowed to inspect or reinforce.

What This Means for You

If you’re building in the Bitcoin ecosystem, the message from the loudest voices in the room is clear: don't touch the foundation. You are expected to work within the existing constraints, regardless of how much safer or more efficient a code change might make your product.

This means your competitive advantage will have to come from abstraction layers. You won't win by proposing BIPs; you'll win by building wallets, bridges, and protocols that make the “un-changeable” base layer work for normal people. It’s a harder path, but it’s the only one left open if the constitutionalists get their way.

The tension between innovation and preservation is the defining conflict of the decade for Bitcoin. One side wants a functional tool; the other wants an immutable monument.

My takeaway? Don't get distracted by the high-minded rhetoric. Saylor is protecting his investment, which is exactly what he’s supposed to do. But as builders, our job isn't just to protect value—it's to create it. If the base layer is staying static, then the pressure is on us to make the layers above it twice as robust. The "Constitution" might be written in stone, but the world we build on top of it is still up for grabs.

Read the original at Decrypt →