Beneath the baroque facade of consensus, the ledger bleeds.
When Michael Saylor posted his 110 objections to BIP-110, the market should have listened not to the arguments themselves, but to the fear beneath them. The fear of a precedent that could unravel Bitcoin's most sacred asset: its immutability. Saylor, as the CEO of MicroStrategy and one of the largest public holders of Bitcoin, does not engage in casual debate. His opposition is a signal—a signal that the governance mechanism of the proposal poses a greater risk than the data bloat it aims to solve.
To understand this, one must first grasp what BIP-110 proposes. The Bitcoin Improvement Proposal number 110 is a set of seven consensus-level restrictions aimed at curbing the use of certain script and witness data. Specifically, it targets the proliferation of inscriptions—often associated with Ordinals and BRC-20 tokens—by limiting the length of script public keys, restricting the number of witness items, and disabling certain Taproot spend paths. On the surface, this is a technical fix to reduce block space bloat and lower the attack surface. But beneath the surface lies a governance mechanism that chills the spine of any conservative Bitcoiner.
The activation mechanism of BIP-110 requires only 55% miner signaling, with no defined timeout or FAILED state. Historically, Bitcoin upgrades have required a supermajority of 95% miner support under BIP-9, ensuring that no change can be forced against the will of a significant minority. The shift to a simple majority threshold is not a minor tweak; it is a philosophical departure from the principle of rough consensus that has protected Bitcoin from capture. Saylor's objections, as detailed in his public posts, focus precisely on this mechanism. He argues that the cure—a low-threshold, unbounded signaling process—is worse than the disease of data bloat. In his view, the risk of creating a precedent where a small group of miners can alter consensus rules outweighs any benefit of restricting inscription transactions.
Let me be clear: this is not a debate about the merits of Ordinals. It is a debate about whether Bitcoin should remain a system that requires near-unanimous consent to change, or whether it can be nudged by a simple majority. The answer, for Saylor and many like him, is unequivocal: Bitcoin's value derives from its predictability. Once the threshold drops, every future proposal will face pressure to adopt the same low bar. The "Pandora's box" is not the content of BIP-110, but the governance precedent it sets.
From my own experience auditing the smart contracts of early Ethereum projects in 2017, I learned that even the smallest flaw in a governance mechanism can cascade into systemic risk. The Parity multi-sig wallet bug was not a coding error alone; it was a failure of process—a lack of formal verification and a rushed deployment. BIP-110, though still in proposal stage, carries a similar scent. The lack of a FAILED state means that if miners signal 55% support but the upgrade fails to lock in for any reason, the network could be left in a state of ambiguity—some miners enforcing new rules, others not, leading to a chain split. The developers behind the proposal claim this is an intentional simplification to speed up activation, but in reality, it introduces an asymmetric risk: a split that would confuse users, exchanges, and wallets.
The technical restrictions themselves are also not without controversy. Limiting script public key length to 32 bytes effectively bans the use of longer keys common in advanced smart contracts like Taproot Assets or RGB. Disabling certain Taproot paths may break existing implementations that rely on robust scriptless scripts. While the proposal's authors argue that these restrictions only affect high-friction use cases, the burden of proof should lie with those who wish to reduce functionality. Based on my analysis of the seven proposed rules, at least three would have unintended consequences for legitimate Layer 2 protocols that have been in development for years. The risk of collateral damage is high.
Saylor's alternative is elegant: use non-consensus methods. Node operators can set policies to reject large witness data without changing the consensus rules. Miners can choose to ignore transactions of certain types through fee market mechanisms. Layer 2 solutions can handle the demand for data attestation. All of these preserve the simplicity of the base layer while allowing the market to self-correct. This is the exact philosophy that has kept Bitcoin robust for over a decade: the base layer should remain as dumb as possible, and innovation should happen above it. By avoiding consensus changes, we avoid the governance attack vector entirely.
The market, however, has been largely indifferent. The Bitcoin price barely moved when Saylor posted his objections. This is because the debate is still in its early stages, confined to the cypherpunk corners of the internet. But make no mistake: if the proposal gains support from a significant miner group, the market will wake up. The specter of a contentious soft fork will collapse the "digital gold" premium that Bitcoin enjoys. During the 2017 SegWit2x debacle, the mere threat of a split caused Bitcoin to lose 30% of its value in a matter of weeks. History does not repeat, but it rhymes.
Now, let me present the contrarian angle. Some argue that BIP-110 is actually a step toward healthier governance because it reduces the barrier to necessary upgrades. Bitcoin, they claim, has become ossified, unable to adapt to new threats such as spam or data bloat. The 55% threshold is a compromise between the utopian 95% and the gridlock of inaction. Moreover, they point out that Bitcoin's governance is not purely miner-driven; the broader community, including node operators and developers, can reject the change even if miners signal. The proposal does not automatically activate upon miner signaling; it requires a user-activated soft fork (UASF) to enforce the rules. This argument has some merit, but it overlooks the asymmetry of power. Once the precedent of a low threshold is established, the next proposal might not require UASF; it could be designed to activate automatically after a simple majority. The slippery slope is real.
Pattern recognition is a burden, not a gift.
I see BIP-110 as a stress test for Bitcoin's immune system. The community's reaction—Saylor's vocal opposition, the debates on mailing lists, the lack of developer enthusiasm—indicates that the immune system is working. The proposal is unlikely to pass in its current form. But the fact that it was proposed at all reveals a growing tension between the "store of value" camp and the "utility" camp. The former wants Bitcoin to remain as unchanged as possible; the latter wants to unlock more use cases on Layer 1. This tension will not disappear. It will manifest again in future BIPs, perhaps with more polished mechanisms.
Saylor's 110 reasons are not just a list; they are a manifesto for conservative governance. They should be studied by every student of Bitcoin protocol development. In them, I see a deep understanding of the second-order effects of consensus changes. He writes that "the macro does not whisper; it screams in silence." The silence of the market is not consent; it is a pause before judgment. The scream will come if BIP-110 moves past the talk stage.
From an investment perspective, this debate should be watched closely. It is not a tradeable event today, but it will shape the risk premium of Bitcoin for years. If the community successfully rejects this proposal and reinforces the principle of supermajority consensus, Bitcoin's narrative will strengthen. If, on the other hand, a modified version passes, the market will need to re-price the probability of future governance attacks. For now, I consider the probability of BIP-110 activation to be low—less than 10%—due to the overwhelming opposition from key influencers and the lack of developer support. But the smart money is already paying attention to the governance health of the network.
Volatility is the tax on ignorance.
Let me dissect the seven restrictions one by one, as they reveal the true scope of the proposal:
- Limit script public key length to 32 bytes. This effectively bans the use of 33-byte compressed keys and 65-byte uncompressed keys. While 32-byte keys (associated with Taproot) are now standard, many legacy wallets and scripts still rely on longer keys. The restriction would force all multi-signature and smart contract outputs to be migrated to Taproot, potentially breaking backward compatibility for transactions that haven't been spent yet.
- Limit the number of witness items to 5. Witness items are the data pushed onto the stack during script execution. Inscription transactions often use many witness items to store arbitrary data. Limiting to 5 would severely hamper such use cases. But it also affects other protocols that rely on complex witness stacks, such as certain atomic swap implementations.
- Disable certain Taproot leaf versions. Taproot allows multiple spending conditions, each with its own leaf version. BIP-110 proposes to disable all leaf versions except for version 0xc0 (the standard version used for key path spending). This would eliminate the ability to use alternative spending paths, such as those required for discreet log contracts or advanced Layer 2 channels.
- Limit script code separation (OP_CODESEPARATOR) to one per transaction. OP_CODESEPARATOR is a rarely used opcode that allows splitting a script into separate signature verification contexts. Restricting it to one per transaction would break any multi-signature scheme that uses multiple separators, though such schemes are almost non-existent today.
- Ban the use of OP_RETURN with data longer than 80 bytes. While OP_RETURN is already limited in Bitcoin to 80 bytes, this restriction would make the limit consensus-enforced rather than a policy rule. It would close the door on any future expansion of data-carrying capacity through consensus.
- Restrict the number of non-push opcodes in a script to 201. This mirrors the current policy limit but makes it consensus-enforced. The practical impact is minimal, as most scripts already have fewer than 201 non-push operations.
- Mandate that all outputs must be either P2PKH, P2SH, P2WPKH, P2WSH, or P2TR. This bans non-standard output types, effectively eliminating all future innovations in output scripting. Any new script type would require a future soft fork to be accepted.
When you read these restrictions together, a pattern emerges: they are designed to lock Bitcoin's scripting capabilities into a static set of forms, preventing any future extension without another soft fork. This is a freeze, not a cleanup. While the stated goal is to reduce complexity and attack surface, the effect is to suppress innovation. Saylor's opposition to this freeze is consistent with his view that Bitcoin should remain open for future upgrades, even if those upgrades require careful deliberation.
We trade in shadows cast by invisible hands.
Now, let us consider the incentives. BIP-110's authors likely believe they are protecting Bitcoin from spam and ensuring its long-term viability as a settlement layer. But their method—consensus changes—is the most dangerous tool available. The 55% threshold is not arbitrary; it is designed to allow passage without requiring the traditional 95% consensus. Why would the authors choose such a low bar? Possible reasons include frustration with the slow pace of upgrades (e.g., SegWit took over two years to activate) or a belief that the community is overly conservative. However, these reasons do not justify the risk.
Saylor's counterproposal is to use economic incentives. Miners can already reject transactions with large witness data by setting a higher fee rate for such transactions. Exchanges and wallet providers can blacklist inscriptions without changing the protocol. The market can self-regulate. This approach is slower and messier, but it preserves the sanctity of the consensus layer. It is the difference between surgery and diet: surgery can fix a problem quickly but carries the risk of infection; diet takes longer but is safer.
From a tokenomics standpoint, BIP-110 does not affect Bitcoin's monetary policy. The supply remains capped at 21 million. However, it does affect the fee market. If the restrictions reduce the demand for block space from inscription creators, miners will lose some fee revenue. In 2023, inscriptions at their peak constituted over 10% of total transaction fees. A sudden reduction could hurt smaller miners with thin margins. Conversely, the restrictions might increase the value of remaining block space as legitimate transactions compete, potentially raising fees for regular users. The net effect is ambiguous, but the volatility is certain.
Liquidity evaporates when trust calcifies.
Let me step back and look at the bigger picture. This debate is not isolated; it is part of a broader tension within Bitcoin between the "digital gold" narrative and the "programmable money" narrative. The former wants Bitcoin to be as simple as possible, a decentralized store of value with minimal functionality. The latter wants to build complex financial applications on top of Layer 1, leveraging Bitcoin's security. Inscriptions are the latest expression of the latter. BIP-110 is a backlash from the former. This tension will only grow as more people try to use Bitcoin for purposes beyond simple payments.
Saylor's position is clear: he is a maximalist of the "digital gold" school. His company holds over 200,000 BTC and his personal brand is tied to the narrative that Bitcoin is the best asset because it doesn't change. His opposition to BIP-110 is consistent with his worldview. But it is also strategic. If Bitcoin becomes more programmable, it might compete with Ethereum and other smart contract platforms, drawing attention away from pure store-of-value narratives. By opposing this proposal, he is defending the thesis that has made him a billionaire.
Art has no soul, only provenance.
The governance of Bitcoin is not written in code; it is a social contract. Every time a proposal like BIP-110 surfaces, the community must reaffirm its values. The value of immutability is not absolute—even the 21 million cap could theoretically be changed, though that would destroy confidence. The threshold for change should be so high that only existential threats can cross it. Data bloat is not an existential threat. It is a nuisance. The proper response is not to change the consensus layer, but to educate users and encourage voluntary adoption of filters.
I predict that BIP-110 will not activate in its current form. The opposition is too strong, and the proposal's flaws are too visible. But the fact that it was written and seriously considered shows that the Bitcoin consensus mechanism is still being tested. The outcome will set a precedent for future governance battles. If the community rejects this proposal decisively, it will signal that Bitcoin's governance is resilient. If it passes, it will signal a shift toward a more malleable protocol, which could undermine the "digital gold" premium.
The macro does not whisper; it screams in silence.
To conclude, BIP-110 is not just a technical proposal; it is a philosophical challenge. Saylor's 110 objections are a valuable contribution to the debate, forcing the community to think carefully about the second-order effects of low-threshold governance. The risk of establishing a precedent where a simple majority can change consensus rules far outweighs the benefits of restricting inscriptions. The best path forward is to rely on non-consensus mechanisms—node policy, fee markets, Layer 2—and to preserve Bitcoin's base layer as a pristine, unchangeable foundation.
As an analyst who has seen the fragility of governance in other protocols, I urge readers to take this debate seriously. The price of Bitcoin is not the only signal to watch; the health of its governance is equally important. BIP-110 may fail, but the next proposal might be more cleverly designed. The battle lines are drawn, and the outcome will shape the future of the entire crypto industry.
We trade in shadows cast by invisible hands.
The final takeaway is this: Bitcoin's value proposition depends on its resistance to change. Any attempt to lower the barrier for change, no matter how well-intentioned, should be viewed with extreme skepticism. Saylor's opposition is not just a personal opinion; it is a defense of the core value that makes Bitcoin unique. The market should listen not to the noise of the moment, but to the silence of the ledger. Beneath the baroque facade of consensus, the ledger bleeds.
