Blockchain AcademicsBlockchain Academics
Michael Saylor Frames Bitcoin Code as Constitution, Warns Against Protocol Changes

Michael Saylor Frames Bitcoin Code as Constitution, Warns Against Protocol Changes

Michael Saylor, chairman of Strategy, has staked out an absolutist position on Bitcoin protocol governance: the code should be treated as a constitution, and any proposed changes constitute constitutional offenses and attacks on economic rights.

Hadi GhadbanEdited by Ibrahim RajabJuly 28, 20264 min read
Share

Michael Saylor Frames Bitcoin Code as Constitution, Warns Against Protocol Changes

Michael Saylor, chairman of Strategy and one of Bitcoin's most prominent institutional advocates, has staked out what may be his most absolutist position yet on protocol governance: Bitcoin's code should be treated as a constitution, and any proposed changes to the base layer, including BIP-110, covenant implementations, and larger block sizes, constitute "constitutional offenses" and attacks on economic rights.

The statement, made publicly this week, distills a worldview Saylor has been building toward for years. For him, Bitcoin's value proposition rests entirely on its immutability. Touch the code, and you undermine the property rights of every holder.

What Saylor Actually Said

The framing is precise and deliberate. Saylor did not single out one controversial proposal. He grouped covenants, larger blocks, and any base-layer change into a single category: constitutional offense. The logic follows from his "digital gold" thesis. If Bitcoin's scarcity and predictability are what make it sound money, then protocol changes introduce political risk into what should be an apolitical system. Every proposed amendment, however technically sound, opens a door that Saylor believes should stay permanently closed.

BIP-110 is a proposal aimed at modifying Bitcoin's scripting capabilities. Covenant proposals would allow Bitcoin transactions to carry forward spending conditions, enabling more sophisticated smart contract functionality at the base layer. Both have legitimate technical arguments behind them, advanced by credentialed developers with long track records in the Bitcoin codebase. Saylor's position does not engage with those arguments on their merits. It forecloses the conversation entirely.

The Immutability Argument Has Precedent, and Limits

Saylor is not inventing this position from whole cloth. The "Bitcoin is digital gold, not a programmable platform" camp has deep roots. Nick Szabo, whose work on smart contracts predates Ethereum by over a decade, has expressed similar skepticism about layering complexity onto Bitcoin's base protocol. The 2017 block size wars produced a genuine rupture: Bitcoin Cash forked off specifically because one faction believed larger blocks were necessary for Bitcoin to function as peer-to-peer electronic cash. That fork is now a cautionary tale cited by both sides, depending on the lesson you want to draw.

What makes Saylor's framing notable is the constitutional metaphor itself. Constitutions are not immutable. The U.S. Constitution has 27 amendments. What constitutions do provide is a high bar for change, requiring broad consensus rather than simple majority. Bitcoin's actual governance process, which runs through Bitcoin Improvement Proposals reviewed by developers and ultimately adopted only when node operators upgrade their software, already functions something like that. SegWit activated in 2017. Taproot followed in 2021. Neither broke Bitcoin. Neither triggered the kind of governance crisis Saylor's framing implies is inevitable.

That history cuts against the absolutist reading. Bitcoin has changed before, through a deliberate, slow, and contentious process that ultimately required near-universal consensus. Framing all future changes as attacks on economic rights does not describe how Bitcoin governance actually works. It prescribes a new, stricter standard that no prior version of the protocol has ever been held to.

Institutional Gravity and Its Distortions

Saylor's influence here matters more than his technical arguments. Strategy holds approximately 597,000 BTC as of its most recent disclosures, making it the largest known corporate holder of Bitcoin. When Saylor speaks about Bitcoin governance, he speaks with the weight of that position behind him. Institutional investors who followed Strategy's playbook are now exposed to his framing in ways that node operators and developers are not.

The risk is a subtle one. Bitcoin's governance has always derived legitimacy from the distributed consensus of developers, miners, and node operators, not from the preferences of large holders. Saylor's "economic rights" language implicitly reframes that: it suggests that those with the most Bitcoin at stake should have the most say in whether the protocol changes. That is not how Bitcoin governance works, and it is arguably the opposite of how it should work.

Developers building on Bitcoin's base layer, including those working on covenant proposals, argue that their changes would expand what Bitcoin can do without compromising its security model or its supply cap. Those are the terms on which the technical debate should be settled. Translating that debate into a constitutional rights framework does not clarify it. It raises the political temperature without adding analytical precision.

What This Signals for Governance

Bitcoin's protocol debates have always been ideological as much as technical. The block size wars proved that. What Saylor's intervention adds is the weight of institutional capital explicitly aligned with the conservative position, and a rhetorical frame, constitutional rights, designed to put protocol evolution on the defensive.

For market participants, the practical implication is that any serious proposal to modify Bitcoin's base layer now faces not just technical scrutiny but a well-funded, highly visible political opposition. That may slow the pace of change further, which is precisely what Saylor intends. Whether it is good for Bitcoin's long-term competitiveness against Layer 1 blockchains that iterate quickly is a separate question, and one the "digital gold" camp has a ready answer for: Bitcoin does not need to compete on features. It needs to compete on trust. Immutability, in that framing, is the product.

Discussion

Loading comments...