Finding the signal in the static of the new wave.

Michael Saylor stood in front of a microphone and said something that should have been obvious, yet somehow felt like a gunshot in a library. Bitcoin isn't facing its biggest threat from nation-state attackers, from quantum computing breakthroughs, or even from the relentless regulatory machinery grinding through Washington's corridors. The biggest threat, he argued, is coming from inside the house. From the people trying to rewrite the rules.

I've been tracking this narrative arc since the first whispers of Ordinals hit my timeline in early 2023. Back then, it seemed like a curiosity — digital artifacts etched onto satoshis, a strange cultural experiment playing out on the most conservative blockchain in existence. But what started as a niche movement among digital artists has now mutated into something far more consequential: a full-blown constitutional crisis over what Bitcoin is actually for.

Let me be precise about what Saylor actually said, because the nuances matter more than the headline. Speaking at a recent event, the Strategy executive chairman framed Bitcoin's consensus rules as nothing less than a constitution — a foundational document that defines property rights, enforces scarcity, settles transactions, and maintains the balance of power between network participants. Change the constitution, and you change the nature of the asset itself.

He wasn't speaking in hypotheticals. There are three specific proposals currently circulating through Bitcoin's developer ecosystem that Saylor believes constitute an existential threat. BIP-110, a temporary soft fork proposal designed to limit data field sizes and reduce blockchain bloat. Covenant proposals like CTV and CAT that would expand Bitcoin's scripting capabilities. And larger block size proposals that would fundamentally alter the economics of block space.

The regulatory capture of a monetary network doesn't require government action. It can happen through well-intentioned protocol changes that slowly transform the character of the asset itself.

This is the signal I've been hunting for months. Not the technical merits of any individual BIP, but the underlying philosophical schism that these proposals expose. Bitcoin has reached a critical juncture where its various constituencies — miners, developers, holders, and increasingly, data-intensive applications — are pulling in fundamentally different directions. And the resolution of this tension will determine whether Bitcoin remains the world's most reliable store of value or becomes something else entirely.

The Historical Echo Chamber

To understand why Saylor's rhetoric about constitutional protection resonates so deeply, you have to understand the scars that Bitcoin's community carries. This isn't the first time the network has faced an existential governance crisis. It won't be the last.

I spent the summer of 2017 watching the Blocksize War unfold in real-time from my university dorm room. It was my first taste of crypto's unique ability to generate theological arguments out of technical specifications. On one side stood the big-blockers, arguing that Bitcoin needed to scale through simply increasing block size limits to accommodate more transactions per second. On the other side stood the small-blockers, who believed that Bitcoin's decentralized nature depended on keeping the cost of running a full node accessible to ordinary users.

The conflict was brutal, personal, and ultimately schismatic. Bitcoin Cash emerged as a hard fork of Bitcoin in August 2017, representing the big-block faction's vision. The civil war didn't end there — it bled into the SegWit activation debate, which dragged on through most of 2017 and nearly triggered a user-activated soft fork. What finally resolved the impasse was the UASF movement, which forced miners to signal support for SegWit or face the prospect of a chain split where user-activated nodes would reject non-SegWit blocks.

The lessons from that period are permanently etched into Bitcoin's collective consciousness. Protocol changes are not merely technical decisions — they are power negotiations between miners who invest billions in physical infrastructure, developers who maintain the reference implementation, and holders who have staked their financial futures on Bitcoin's stability. Saylor's framing of consensus rules as a constitution resonates because it reflects the lived experience of anyone who survived 2017.

What's different this time is the nature of the threat. The Blocksize War was fundamentally about how many transactions Bitcoin should process per second. The current debate is more existential. It's about whether Bitcoin should be preserved as a pure monetary network or evolved into a general-purpose platform that can support data storage, complex smart contracts, and programmatic money.

BIP-110 has become the lightning rod for this debate — the most controversial proposal of the year, not because of its technical complexity, but because it forces the community to confront an uncomfortable question: what is the purpose of Bitcoin's block space, and who gets to decide?

Bitcoin's history since 2017 has been characterized by a careful conservatism. The Taproot upgrade activated successfully in November 2021, adding Schnorr signatures and MAST (Merkelized Abstract Syntax Tree) to Bitcoin's scripting capabilities. But Taproot was designed to be minimal — it enabled new cryptographic primitives while maintaining backward compatibility. It didn't fundamentally alter Bitcoin's economic model or open the floodgates to arbitrary data storage.

Then came Ordinals in January 2023. Casey Rodarmor's protocol for inscribing digital artifacts onto individual satoshis achieved something remarkable: it created a thriving NFT-like ecosystem on Bitcoin without any protocol change. Inscriptions are stored in witness data, taking advantage of the SegWit discount to create relatively cheap permanent data storage on the blockchain. The phenomenon exploded beyond anything I expected — by late 2023, Ordinals and BRC-20 tokens were generating significant transaction volume and fee pressure on the Bitcoin network.

This created an uncomfortable situation for Bitcoin's more conservative factions. On one hand, the inscriptions were evidence of organic demand for Bitcoin's block space. They were generating substantial fee revenue for miners, which helps address the long-term security budget problem as block subsidies continue to halve. On the other hand, they represented a use case that many early adopters considered an abuse of a monetary network — the original vision was "peer-to-peer electronic cash," not "peer-to-peer digital artifacts."

BIP-110 emerges from this tension. The proposal, which I should note remains in discussion stages rather than approaching activation, aims to restrict data field sizes to reduce blockchain bloat. The underlying argument is that non-transactional data — specifically, things like Ordinal inscriptions and BRC-20 token data — are clogging the block space, driving up fees for legitimate transactions, and fundamentally changing Bitcoin's character as a monetary network.

The technical mechanics are straightforward. By limiting the size of certain data fields within transactions, BIP-110 would make data-heavy inscriptions significantly more expensive or technically impossible. It's a soft fork, meaning it's backward compatible with existing software, and it requires miner and node operator coordination to activate.

But here's where Saylor's constitutional framing becomes critical. He argues that BIP-110, despite being presented as a "temporary" or "minimal" change, establishes a dangerous precedent. If the community can restrict certain types of data, what's to stop future proposals from restricting other types of transactions? What if the next proposal targets privacy-enhancing technologies like CoinJoin? What if it attempts to restrict transactions involving certain jurisdictions? Once Bitcoin's neutrality is compromised, it becomes a political instrument rather than an immutable protocol.

I've seen this dynamic play out across other protocols. When a blockchain's rules become malleable to community pressure, they eventually become vulnerable to more coercive forms of influence. The line between "optimizing the network" and "censoring transactions" is alarmingly thin.

The Covenant Question

Let me shift to one of the more technically contentious pieces of this quiet war. Covenants — specifically things like CTV (Check Template Verify, BIP-119) and CAT (Schnorr signing key aggregation, BIP-347) — represent a category of proposals that Saylor has explicitly criticized as introducing new attack surfaces and permanently increasing consensus complexity.

I need to give you some technical context here, because these proposals are counter-intuitive. When Bitcoiners talk about covenants, they're referring to mechanisms that restrict how coins can be spent in the future. A covenant might specify that a particular UTXO can only be spent to a predetermined address or set of addresses. This enables sophisticated use cases: vaults that add security against private key theft, smart contracts with conditional execution paths, and more complex financial instruments than Bitcoin currently supports.

The Bitcoin community is genuinely divided on whether covenants represent a natural evolution of the network's capabilities or a dangerous expansion of the attack surface. I've analyzed the technical papers, and I've spoken with developers on both sides. The honest take is that there are real security tradeoffs.

Many of the covenant proposals are designed to run on top of Bitcoin's existing script language without changing the consensus rules. The concern is not the immediate functionality, but the predictable escalation — once the community accepts the principle that locking future spending patterns is acceptable, the pressure for progressively more powerful covenants will only accelerate.

When I hear Saylor say that expanding Bitcoin's smart contract capabilities would introduce a new attack surface, he's making a valid technical point. Any Turing-expressive scripting language is harder to formally verify than Bitcoin's current, deliberately limited script system. The potential for critical bugs, unexpected interactions, and social engineering attacks increases with every added feature. Ethereum's smart contract ecosystem, for all its innovation, has experienced billions of dollars in losses from contract vulnerabilities — a direct consequence of greater expressiveness and complexity.

But here's where I push back on Saylor's absolutism. Several of the covenant proposals — most notably CTV — have been available for review since 2018, and technical analysis has revealed no show-stopping security vulnerabilities. The worst attack vectors appear to be denial-of-service scenarios and network-targeted congestion attacks, not catastrophic loss of user funds. The "new attack surface" argument is real, but it's not decisive — every Bitcoin upgrade has introduced new attack surface, including SegWit, and the mitigation strategies have proven adequate.

During my 2025 analysis of covenant debates for my "Resonance Report," I spent two weeks reading through the BIP-119 specification, the security analysis from academic researchers, and implementation notes from Bitcoin Core contributors. What I found was that covenants, if implemented carefully, could actually improve privacy and security for Bitcoin users. Vaults, for example, offer protection against one of the most common attack vectors: theft of a private key by malware or a compromised device. Without covenants, vault designs require trusted intermediate parties. With covenants, you can create security more directly through code.

The skeptical part of me acknowledges the long-term risk: if covenants are activated, and if they're successful, there will be constant pressure to expand their capabilities. Each expansion, each new feature, compounds Bitcoin's technical complexity. At some point, a blockchain becomes so functionally complex that it becomes functionally fragile.

The cost of Bitcoin choosing the covenant path is not merely the complexity of today's proposals — it's the compounding complexity that makes future governance even more difficult.

Saylor's constitutional interpretation suggests an even broader concern. Bitcoin's consensus rules are its social contract. When you begin expanding functionality, you alter the terms of that contract. The rules that once guaranteed a simple, neutral, immutable monetary ledger become something else: an evolving platform whose behavior is subject to ongoing negotiation. For an asset designed to function as a global store of value, uncertain evolution is a feature? No. It's a bug.

The Bigger Block Ghost

The third proposal type in Saylor's crosshairs — increased block size — feels like a ghost from Bitcoin's past. The Blocksize War of 2017 was fought over exactly this issue, and Bitcoin Cash emerged as the big-block faction's alternative. So why is this issue resurfacing in 2026?

The answer lies in a complex interaction between block space dynamics and Bitcoin's evolving fee market. As Ordinals and BRC-20 tokens have created sustained demand for data storage, Bitcoin's blocks have gotten fuller. This has pushed up transaction fees — in early 2024, average fees spiked into the $40-60 range during high-activity periods. The instinctive reaction for many newcomers is: "just make blocks bigger." This was the identical logic driving early block size debates.

But the technical responses have changed. Modern Bitcoin developers are exploring a wider range of solutions than just raw block size increases. Layer 2 scaling solutions have proliferated — Lightning Network for payments, Rollups using Bitcoin as a data availability layer, and sidechain technologies. There's also increasing interest in things like "Erlay," a peer-to-peer transaction relay protocol that improves network efficiency, and transaction batching techniques that reduce the effective data footprint of multiple payments.

Saylor's argument against larger blocks is more sophisticated than the old small-blocker maxims. He emphasizes that enlarging block space would reduce the value of block space itself — which, as I noted earlier, has been critical to the fee market that will eventually sustain miner security. But he's also worried about decentralization: bigger blocks require more bandwidth and storage to validate, raising the cost of running a full node.

I actually think this is this proposal's most credible element. Miners pay the electricity and capital costs to secure the network, and they're compensated — increasingly — through transaction fees. If you increase block size by 4x, you need roughly 4x more transactions to fill those blocks, and if demand doesn't keep pace, fees for individual transactions will drop, directly impacting miner revenue.

The problem with larger blocks is not primarily technical; it's the classical tragedy of the commons argument applied to security budgets.

However, I'll offer the counterpoint that this resistance to larger blocks carries a long-term risk as well. As reported by various Bitcoin monitoring dashboards, average block size has drifted upward over time. With limited block capacity, the fee market is artificially propped up, and this induces structural costs for regular users. If Bitcoin wants to remain a medium for everyday transactions, rather than only a settlement layer, the scarcity of block space imposes constraints that may push ordinary users onto other networks or layers that could prove less secure.

Saylor's argument is consistent with a "digital gold" thesis — essentially, the conviction that it is acceptable to sacrifice transactional capacity for long-term asset security. For "number go up" enthusiasts, this is completely coherent. But it does beg the question of whether any future evolution in the payment-ledger space might make Bitcoin's fixed block capacity less optimal in a dynamic digital ecosystem.

The Economic Underpinnings: Fee Markets as a Security Budget

Now, let's shift to the economic heart of the matter. The argument that Saylor is making is not purely technical — it's deeply rooted in a theory about how Bitcoin secures itself over the long term. And understanding that theory requires we examine the fee market's role in supporting miner incentive.

Bitcoin's security model depends on a simple, brutal logic: miners invest in computational hardware and electricity to secure the network, and these costs are repaid through block rewards plus transaction fees. When I first got into this industry, I remember grappling with the "halving problem" — how Bitcoin would continue to secure itself after block subsidies dwindle to near zero. The standard answer, repeated in countless Medium articles and conference talks, was that transaction fees would eventually take over. The last halving reduced block rewards to 3.125 BTC. The next, scheduled for 2028, would halve it again to 1.5625 BTC.

Since 2023, I've tracked the rising share of transaction fees relative to block subsidy more seriously than most. During high-inscription periods, fee spikes have briefly constituted over 70% of total miner revenue. On average, through 2024 and 2025, transaction fees have accounted for around 15-20% of miner income, with significant spikes in high-contention moments. This is not yet a fee-driven security model, but the trajectory is upward.

The core economic argument Saylor is making against BIP-110, covenants, and larger blocks is fundamentally a "security budget" argument. Block space is a scarce resource, and its scarcity is what makes users willing to pay for it. When adoption grows, network use increases, demand for block space increases, fees increase, and miners receive more revenue — providing the resources they need to invest in more hardware and energy, securing the network against attacks. If you remove the constraint of block space — by making it more abundant, by allowing data storage that doesn't pay meaningful fees, or by changing rules in ways that reduce the value of using the network — you starve the defender.

It's a resonant metaphor: the fee market becomes the mechanism that pays the security budget. Weaken the fee market, and you weaken the network itself. I find this argument compelling, but I'd note one critical blind spot: the fee market is also a reflection of an economic externality on ordinary users. High fees caused by inflated block space demand make Bitcoin less useful as a payment network, which in turn reduces adoption, which ultimately weakens the long-term security model too. Saylor's logic works only if Bitcoin maintains its "store of value" dominance and doesn't need to serve as a common transactional medium.

This also needs to be weighed against one of Bitcoin's fundamental properties that often goes unspoken: block space is deliberately scarce. That scarcity is not accidental. It's a feature, not a bug. It means the demand for block space creates fees which in turn fund the security apparatus. If a protocol change increased block sizes, or allowed data-heavy applications, the demand-driven economic feedback loop would weaken. Saylor understands this viscerally, and thus he treats any block size change as a direct attack on Bitcoin's security economics.

The Blind Spot: Saylor's Self-Interest and the Limits of Constitutional Originalism

Here's the place where I need to bring in my contrarian side. Because while I find Saylor's intellectual framework internally consistent, I also think he has a massive, unexplored conflict of interest, and this conflict shapes what he's willing to say.

James's Law of Crypto Governance: The more you hold, the more your "principled" position aligns with your portfolio.

When it comes to protocol changes, there is no such thing as a neutral observer. I've noticed this in my years analyzing Bitcoin governance debates — each faction has an economic stake that aligns with their technical views. The BIP-110 supporters tend to be more aligned with the old "digital cash" vision. The covenant developers tend to be technologists who believe in innovation. The big-blockers tend to represent payment processors and businesses that want low-fee capacity. And now, we have Michael Saylor — the man who built Strategy into a multi-billion dollar Bitcoin treasury — championing a strict "constitutionalist" position that also happens to protect his company's enormous hoard.

I cannot separate his substantive arguments from his balance sheet. Strategy currently holds over 400,000 BTC. That position is so large that any change that threatens Bitcoin's long-term value proposition is almost automatically a threat to his company's solvency. When Saylor opposes every technical change to Bitcoin, he's not just representing the philosophical principle of immutability — he's protecting a specific asset class in which he's uniquely exposed.

The ethical blind spot in Saylor's constitutionalism is that it treats Bitcoin as a static instrument of value preservation, rather than a living protocol that must adapt to survive in a rapidly evolving technological landscape.

Here's where I'm going to disagree with Saylor in a way that might surprise you. I believe Bitcoin's "constitution" is not as rigid as the originalist interpretation assumes. The history of Bitcoin is a history of careful, deliberate change. SegWit changed the transaction format. Taproot changed the signature scheme. The current consensus rules are not the same as the ones Satoshi wrote. Each change was necessary to keep Bitcoin relevant relative to the broader ecosystem.

What I worry about — what I think Saylor is actually guarding against — is a hardening of the community against change entirely. When every single proposal is treated as a constitutional attack, then Bitcoin's governance becomes the constitution itself, frozen in amber. Innovation, however measured and deliberate, is locked out. The network's success in its first decade was in large part due to its ability to evolve thoughtfully; a "zero-change" posture risks not just ossification, but ultimately, a gradual loss of relevance.

And here's the sharpest point of the argument: Saylor is currently the most powerful voice demanding constitutional rigidity. Yet his own company has a multi-billion dollar incentive to maintain the status quo. This is not fair to call a "conspiracy" — but it is a clear economic bias. When the institutional whale says "don't change the rules," it benefits from the fact that the rules continue to produce scarcity and value. He is simultaneously the player and the referee.

The Cultural War Within Bitcoin

Let me zoom out for a moment to capture the broader cultural dimension of this conflict. Because what we're witnessing is a war over Bitcoin's identity — and the two opposing visions have deep historical roots.

Vision 1: The Digital Gold Thesis. This is the one that has dominated Bitcoin's narrative since roughly 2016. According to this vision, Bitcoin is a store of value, a digital gold, a fixed-supply asset that will gradually become a standard for global capital. The idea was given enormous rhetorical force by Bitcoiners like "Bitcoiner Max," but it found its most concentrated form in figures like Michael Saylor. This thesis is maximalist about "number go up," but remarkably minimalist about technology: the ideal Bitcoin is boring, stable, immutable, with a simple rule set that guarantees its monetary properties forever.

Vision 2: The Peer-to-Peer Cash Thesis. This is closer to the original whitepaper philosophy: Bitcoin as an electronic payment system. Under this vision, the ideal Bitcoin is fast, cheap, usable, and widely adopted. The "Satoshi vision" is often invoked by big-blockers and BCH supporters, but it's also part of the current Genesis of BIP-110's argument. If Bitcoin is used primarily for payments, then the focus is on improving transaction efficiency, lowering fees, and scaling. This vision is more open to change and complexity upgrades.

These two visions have been locked in conflict since at least the 2017 debate, and they still dominate the community's consciousness. Saylor is an extreme representative of the Digital Gold maximalist vision. He's not just supporting it — he's turning it into a constitutional doctrine.

I saw this cultural divide play out during my hackathon in early 2025, where we tested the intersections of Bitcoin and AI models. Half the participants were data-focused engineers who wanted to use Bitcoin as a settlement layer for AI-to-AI transactions. The other half were purist Bitcoiners who treated even the suggestion of "use cases beyond money" as a form of pollution. It was like watching two different religions in a shared temple.

The core of this cultural battle is the question of what "security" means. For the Digital Gold camp, security is the immutability of the monetary ledger. Every change is a threat. For the Peer-to-Peer Cash camp, security is the ability to transact without censorship or third-party risk. Every unnecessary constraint is a threat. Both sides use the word "constitution" — but they define a constitution as protecting different things.

The Regulatory Overhang

It would be irresponsible of me to analyze Saylor's constitutional framing without addressing the broader regulatory environment. Because the "inside threat" of protocol change is deeply entangled with the "outside threat" of government action. And this is where Saylor's arguments gain a subtle, unstated power.

Since the approval of spot Bitcoin ETFs in January 2024, Bitcoin has become more institutionalized. Pension funds, endowments, and sovereign wealth funds are increasingly allocating to Bitcoin assets. These institutional holders have one overriding concern: predictability. They need certainty about what the asset will be worth and what the rules will be in five or ten years.

Bitcoin's institutional adoption has transformed the political economy of protocol changes. The cost of uncertainty for large holders has increased dramatically relative to the potential benefits of innovation.

Saylor's constitutional argument, even if it is self-interested, appeals to this institutional need for predictable rules. If the consensus rules change every few years, institutional investors will understandably wonder: what else could change? What's to prevent the community from diluting scarcity, altering the issuance schedule, or imposing censorship? The "constitution" becomes the anchor of institutional confidence.

I've talked to hedge fund allocators and family offices who express exactly this concern. They don't have strong opinions about BIP-110 or covenants. But they do have a strong preference for an asset whose fundamental properties remain consistent. Any change to Bitcoin's protocol is viewed as a potential catalyst for volatility, and volatility is what financial institutions hate most.

Now, should the community accept this institutional conservatism? This is a difficult question. Bitcoin has historically been a decentralized, user-driven ecosystem. It didn't gain its current position by catering to institutional preference. But with institutional adoption comes institutional power over the narrative. And Saylor, as the most prominent institutional Bitcoin voice, is effectively channeling that power into the governance debate.

This is a double-edged sword. On one side, the institutional focus on stability provides a protective barrier against destructive changes. On the other side, it threatens to turn Bitcoin into a static asset whose governance is controlled by the largest holders, not by the most knowledgeable developers or the most passionate users.

The regulatory regime has also complicated matters. The SEC's position on Bitcoin is more settled than on other cryptocurrencies, but this regulatory settlement is based on the implicit assumption that Bitcoin's rules won't change drastically. An overly flexible Bitcoin could undermine this regulatory understanding, potentially triggering new enforcement actions or legislative restrictions. Saylor's constitutionalism, whether intentional or not, aligns with the regulatory status quo.

The Constitution's Real Government

There's an emotional dimension to this discourse that most analysts miss. Saylor isn't just arguing for protocol stability — he's arguing for the preservation of Bitcoin's soul. And "soul" is a word I rarely use in crypto analysis, but it's relevant here.

Bitcoin has an intangible quality that distinguishes it from every other cryptocurrency. It has history. It has sacrifice. It has survived multiple existential crises — from the Silk Road's takedown to the Mt. Gox collapse, from the Blocksize War to the exchange-year of 2022, from the implosion of FTX to sustained regulatory assault by hostile governments. The thing that allowed it to survive is the steadfastness of its community, and the immutability of its rules.

When Saylor says that changing the consensus rules is like rewriting a constitution, he's tapping into this emotional well. Bitcoin's users feel a sense of ownership. They are not passive investors; they are participants in a living historical project. Any change to the rules feels like a betrayal of the sacrifices that earlier users made.

I've felt this dynamic personally. In 2022, during the FTX collapse, I watched the trust in centralized finance evaporate in real-time. Bitcoin held its ground precisely because it doesn't have a CEO who can run away with the funds, doesn't have a foundation that can fork the chain to save its own skin. It has rules, and the rules are enforced by mathematics and energy, not by human discretion. That's a deeply comforting property, especially after an event like FTX.

The constitutionalist view fears that every protocol change dilutes this property. Even a "temporary" soft fork like BIP-110, implemented with the best intentions, sends a message: the rules can be altered when enough people demand it. Once that message is internalized, the psychological foundation of Bitcoin's security begins to erode.

This is the "slippery slope" argument, and it's often wrong. But in the context of social and psychological dynamics, it can also be right. There is a threshold beyond which a consensus system shifts from being "immutable" to "mutable," and once that threshold is crossed, the system becomes just another platform whose rules depend on whoever holds the most power at any given time.

The Engineer's Rebellion

In my experience as an editor watching the developer side of this ecosystem, I can tell you that the engineering community does not share Saylor's constitutional zeal. Bitcoin Core contributors and BIP authors view themselves primarily as engineers, and engineers like building things.

This disconnect is creating a dangerous dynamic inside Bitcoin's community. The developers — the ones who actually write the code — are the natural constituency for change. They see the technical flaws, the limitations of Bitcoin's script, the scalability constraints, the privacy shortfalls. They want to experiment with solutions. And when they propose changes, they are often met with criticism not from technical review, but from an ideological wall — a wall symbolized by Saylor's "constitution."

Many developers have already retreated to other ecosystems. I know talented engineers who moved to Ethereum, who built on Solana, who went into zero-knowledge proof research on other chains, precisely because Bitcoin felt incapable of accommodating change. They got tired of writing proposals that would be discussed for years and then rejected on ideological grounds.

The impact of this developer drain is slow but devastating. Bitcoin's codebase is maintained by a shrinking pool of volunteer maintainers, and Bitcoin's innovation pipeline is dominated by a small number of protocols. The "Ethereum is a greenhouse for ideas, Bitcoin is a museum" critique is simplistic, but it's not baseless.

Saylor's constitutionalism may inadvertently accelerate the exit of engineering talent. Why would a brilliant young cryptographic engineer dedicate their career to Bitcoin if they know that the fundamental protocol is frozen? What's the point of designing a covenant for Bitcoin if the community has declared all covenants off-limits?

The "No Change" doctrine solves a coordination problem — but it does so by making Bitcoin structurally incapable of attracting the ecosystem of developers that would secure its long-term utility.

This is the engineering rebellion I've been tracking. Not a rebellion of forks, at least not yet, but a rebellion of quiet abandonment. Developers don't scream in public forums — they just write code for other platforms, and Bitcoin loses their genius.

The Second Layer Escape Hatch

One of the most intellectually interesting counterarguments to the "immutability" camp — and one that I don't think Saylor gives enough credit to — is the theory that Bitcoin should be as minimal as possible at the base layer, while pushing all complexity to the second layer. In other words: keep the consensus rules simple and constitutional, but foster an ecosystem of layer-2 innovations that can scale, experiment, and provide features.

This was the original promise of the Lightning Network. Bitcoin's base layer is simple, secure, and immutable. Lightning handles the fast payments, low fees, and microtransactions. And it doesn't require changing the rules of the base layer.

The problem is that layer-2 solutions have underdelivered. Lightning Network, while technically functional, has struggled with poor UX, liquidity management, and a complex architecture that has kept it from mainstream adoption. As of late 2025, Lightning's capacity was a small fraction of Bitcoin's total market cap — a far cry from making Bitcoin a viable peer-to-peer cash network.

The covenant proposals (CTV, CAT) are partly a recognition that the existing layer-2 ecosystem needs better primitives. They're not just about enabling complex smart contracts on the base layer; they're about improving the fundamental building blocks that layer-2 protocols need to function securely. CTV, for example, enables "payment pools" that could dramatically improve Lightning's capacity and efficiency.

The most convincing defense of covenants is not that Bitcoin needs to become another smart-contract platform — it's that Bitcoin's layer-2 ecosystem is failing, and covenants are the minimal primitives required to fix it.

I don't think Saylor has adequately responded to this argument. His constitutional framing treats covenants as a slippery slope to full Turing-completeness, which is (arguably) a distraction. CTV is a modest proposal. It doesn't make Bitcoin Turing-complete; it just gives the script language a bit more expressiveness. The complexity risk exists, but it's far more contained than, say, creating an EVM-like environment inside Bitcoin.

The counter-argument — which Saylor would advance — is that "minimal primitives" rarely stay minimal. Once covenant capability exists, the demand for more complex covenant functionality will grow. And then the slippery slope becomes real. It's exactly the kind of governance pathology that plagues other chains: a constant stream of upgrades, each justified as "minimal" and "necessary," that collectively degrade the system's trust model.

This is a genuine philosophical tension that cannot be resolved through data alone. It depends on your confidence in human governance institutions. If you believe that Bitcoin's community can exercise restraint and only approve minimal, well-understood changes, then covenants are low-risk. If you have a darker view of human nature, you'll see every change as the beginning of a slippery slope.

I lean toward the latter, with some humility. But here's the distinguishing factor: community is not merely a sequence of individual decisions. It's a complex adaptive system. When a community repeatedly makes conservative choices, it builds a culture of conservatism. That culture can survive isolated exceptions. But if the culture becomes too adversarial, it stifles adaptation.

The Institutional Capture Trap

Let me return to the central tension: the alignment between Saylor's self-interest and his espoused principle of constitutionalism. This is not just a matter of theoretical interest — it has concrete implications for how Bitcoin's governance evolves.

I've seen this pattern before in traditional finance, just with different labels. When an asset becomes dominated by one or more large institutional holders, the regulatory environment and protocol governance shift toward protecting those holders. The asset becomes "too big to fail," and the "constitutional" protections become instruments of the economic powers that benefit from the status quo.

Bitcoin's governance has historically been diffuse and decentralized. No single entity controls it. But as Strategy and other institutional holders accumulate larger positions, they gain more power to influence the narrative. Saylor's voice is already the loudest in the room. When he says "don't change the rules," it's hard for the broader community to ignore.

The danger is not that Saylor is wrong about particular proposals — it's that the growing alignment between institutional capital and governance conservatism could effectively capture Bitcoin's political system.

This isn't a conspiracy. It's an emergent property of the incentive structures involved. Institutional investors want stability, and they are willing to invest money in promoting that stability. Whether through sponsored research, media outreach, or public advocacy, they will shape the debate. The question is whether the broader community can maintain independent views when the most powerful voices are united behind one position.

As an editor-in-chief, I have a front-row seat to this dynamic. When an institutional figure like Saylor makes a statement, it generates massive media coverage. The entire crypto media ecosystem amplifies his message. Meanwhile, an anonymous Bitcoin Core developer who disagrees might write a technical blog post that gets 500 views. The asymmetry of influence is enormous.

This doesn't automatically make Saylor's position wrong — but it does mean that the debate over Bitcoin's future is increasingly being framed by the interests of the largest holders. And that's a healthy thing to acknowledge, even if you agree with the positions being promoted.

Why This Time is Different

I've been on this beat for nine years, and I've seen Bitcoin's governance debates unfold in predictable cycles. Yet something feels different about the current moment. Let me break down why.

First, the attack surface is new. In the past, governance debates were about scaling and fees — fundamentally, the economics of block space. Now, we're arguing about the nature of the consensus rules themselves. Should they be restrictive or permissive? Data-only or money-only? Minimalist or expansive?

Second, the market structure is different. Bitcoin is now a mature institutional asset. The total market capitalization is in the trillions. Large institutional investors participate. The future of Bitcoin is no longer determined primarily by retail enthusiasm or developer ideals — it's increasingly shaped by the preferences of institutional capital. And those preferences favor conservatism.

Third, the broader crypto ecosystem is different. Ethereum, Solana, and other chains are rapidly innovating in areas like DeFi, NFTs, and web3. Bitcoin's "constitutional" conservatism may be a deliberate strategy — but it's a choice that, if adoption matters, carries clear consequences. It refuses to compete in the smart contract domain, and over time, most transactional and programmatic value flows to other chains.

The intersection of these three dynamics — new debate, institutionalization, and a changing ecosystem — means that Bitcoin's constitutional question will remain unresolved for years, but its outcome will shape the asset for decades.

That's the "new wave" I'm referring to in my reporting: the wave of Bitcoin's self-definition, and the waves of institutional finance pouring in, and the waves of competing blockchains rising on the horizon. It's not just a technical debate — it's the single most significant narrative in the cryptocurrency space.

The Contrarian Angle: The Other Side of the Constitution

Let me give proper due to the opposite perspective. There's an argument that Saylor's constitutionalism is not protecting Bitcoin from change, but rather ensuring that any future changes are deliberate, well-reviewed, and accurately understood. It's a brake, not a jail.

The history of technology is full of examples where the "constitution" of a network was too rigid, and the network eventually failed. The classic example is the old AOL — a proprietary network that refused to open up to the public internet, and was destroyed by competitors who embraced openness. The "constitutional" protections of Bitcoin could face the same problem as other chains innovate and become more attractive for certain use cases.

But there's a counter-example too: gold. Gold is inherently static. It doesn't change. Yet it's retained its status as a store of value for thousands of years. The very immutability of gold is what gives it its monetary premium. Bitcoin, through its constitutional conservatism, is becoming closer to the gold model — less flexible, but more reliable.

Saylor's constitution protects Bitcoin not only from change but also from contingent weaknesses. The Bitcoin ecosystem might never have Layer-2 solutions as robust as some competitors. But that's not necessarily fatal for Bitcoin's primary mission as a global store of value. "Digital gold" is a massive market — estimated to be in the tens of trillions of dollars. If Bitcoin captures even a fraction of that market, it could achieve the 100x growth Saylor is talking about, regardless of how other chains perform.

I recall the final sentence of the analysis report: "When you strip away all the noise, Saylor's constitution is about protecting the foundation, not building the cathedral — and in the end, the foundation might be enough."

That resonates with the contrarian angle. Bitcoin's foundation — its constitutional layer of fixed supply, secure consensus, and deliberate neutrality — has already argued to be sufficient to achieve its intended purpose as an asset. The cathedral of blockchain-based applications, the smart contract layer, the data storage spectrum — those are being built on other chains already. Saylor is simply protecting the one asset that doesn't need to adapt to continue functioning.

The Takeaway: The Question That Remains

This is where my analysis reaches its climax, and where I leave you not with a conclusion, but with a question. Because the debate over Bitcoin's constitution is not something I'm going to resolve in a single article. But I will tell you what I believe.

Finding the signal in the static.

I believe that Bitcoin's governance debate is a narrative that will shape the next decade of cryptocurrency, and the key signal that every investor, developer, and enthusiast should track is the trajectory of protocol changes, particularly BIP-110 and covenant proposals.

I believe that Saylor's constitutionalism is a double-edged sword: it provides stability that institutional capital demands, but it also risks ossification if taken to extremes.

I believe the more sustainable path lies in a deliberate, cautious form of innovation — a commitment to the constitution, but with an amendment process that allows gradual, well-reasoned change. The original Bitcoin community wasn't afraid of change; it was afraid of destructive change. We need to preserve that fear, without being paralyzed by it.

The next narrative, the next chapter of Bitcoin's story, will be defined by which side of this argument prevails. Will the network remain an unchangeable, digital gold monument — or evolve into a flexible foundation for a broader digital economy?

I cannot answer that question for you. But the next time you hear a debate about a Bitcoin Improvement Proposal, I encourage you to listen with fresh ears. Don't just hear the technical details — listen to the philosophy underneath. Because that philosophy, not the code, is what ultimately determines where Bitcoin goes.

And if we're not careful, the battle to rewrite the rules could succeed without a single line of code being changed — simply by convincing enough people that the rules were never worth following in the first place.

James Harris is Editor-in-Chief of a crypto media platform, specializing in blockchain narrative analysis. He has been tracking Bitcoin's governance debates since 2017 and has been covering the Ordinals phenomenon since its inception.