We audit the code, but who audits the conscience? This week, Michael Saylor did not release a whitepaper. He released a volley of opposition—110 posts against a proposal that, on its face, seems technical and narrow. BIP-110 aims to restrict non-financial data in Bitcoin transactions. But beneath the surface, it is a referendum on what Bitcoin should be: a pristine settlement layer or a canvas for a thousand experiments. The community is split. The debate is raw. And I find myself, as an open source evangelist who has spent years auditing governance models, asking not just whether this change is efficient—but whether it is just.
To understand the stakes, we must rewind to the genesis of this conflict. Ordinals, the protocol that allows users to inscribe digital artifacts—images, text, even entire games—directly onto satoshis, exploded in 2023. It revived Bitcoin’s block space demand, pushed fees higher, and created an entire ecosystem of BRC-20 tokens and NFTs. For some, it was a renaissance: a demonstration that Bitcoin could support more than simple value transfers. For others, it was a desecration: a misuse of scarce block space for frivolous data that clogs the network and drives up costs for ordinary transactions. BIP-110, authored by an anonymous developer (the BIP process does not require a public identity until later stages), proposes a soft fork to explicitly prohibit the inclusion of non-financial data in Bitcoin transactions. It is a surgical strike against the Ordinals phenomenon.
But soft forks are never merely technical. They are political, ethical, and economic. They redefine the boundaries of permissible use. And when a figure like Michael Saylor—chairman of MicroStrategy, owner of over 200,000 BTC—launches a counter-campaign, the debate transcends code.
The Core: What BIP-110 Actually Does (and Doesn’t)
BIP-110 is still a proposal. No code has been merged into Bitcoin Core. No testnet has been deployed. What we know from community discussions is that it would modify the transaction validation rules to reject inputs or outputs that contain data beyond what is necessary for financial transfer. This includes the witness field—the same field where Ordinals inscriptions live. The mechanism is a soft fork, meaning old nodes would still accept the new blocks (they simply wouldn’t know about the restriction), but miners would need to signal readiness. If 95% of hashing power adopts the new rules, the old rules become invalid in practice.
The stated goal is efficiency: reduce block space wasted on non-financial data, lower transaction fees for genuine transfers, and mitigate the risk of blockchain bloat. But the unstated goal is ideological: restore Bitcoin’s role as a pure peer-to-peer electronic cash system, as envisioned by Satoshi Nakamoto.
Based on my experience auditing governance models during the 2017 DAO boom, I recognize the pattern. Every protocol change carries a moral weight. The 1Balance project I analyzed had a governance contract that seemed technically sound—until I realized it concentrated voting power in a single multisig. The ethics were hidden in the code. Here, the ethics are visible in the choice of what to restrict. Is data a pollutant or a legitimate use of block space? The answer depends on your values.
The Contrarian: Is Saylor Fighting for Neutrality or for His Own Portfolio?
Saylor’s opposition may appear principled: he argues that restricting data types would violate Bitcoin’s neutrality, setting a precedent for future censorship. A protocol that can ban non-financial data today could later ban certain financial transactions—perhaps those involving sanctioned entities or privacy tools. He calls BIP-110 a “risk to the essence of Bitcoin.”
But let us examine the incentives. MicroStrategy holds roughly 0.5% of all BTC. Saylor has built a corporate empire on the premise that Bitcoin is a store of value, not a platform for tokens. Ordinals, with their memetic energy and speculative frenzy, introduce volatility and regulatory scrutiny that could threaten that narrative. By opposing BIP-110, he positions himself as a guardian of neutrality—but he also protects his own thesis. He has rejected similar proposals in the past, such as OP_CAT, which would have enabled smart contracts on Bitcoin. His consistency suggests a deeper vision: Bitcoin as a monolith, not a garden.
Yet there is a more subtle danger. The very act of opposing a soft fork on neutrality grounds is itself a political stance. Every piece of code is a judgment. Satoshi chose to limit block size to 1 MB, a value judgment against large blocks. The Taproot upgrade favored privacy and scripting complexity over simplicity. Protocol neutrality is a myth: the only truly neutral network would accept any transaction, including those that contain illegal content. That is impossible. So the debate is not whether to restrict, but where to draw the line.
Where I Stand: Build Not for the Peak, but for the Plain
After three months in 2022, isolated in my Shenzhen apartment during the bear market, I wrote twenty-four deep analyses on Layer 2 scaling. I watched projects promise throughput and deliver vaporware. I learned that sustainability beats speculation. The same principle applies here: Bitcoin’s long-term resilience depends not on maximizing every use case, but on maintaining a clear, auditable core. Ordinals are exciting, but they are a peak—a speculative frenzy that inflates fees and then collapses. BIP-110 is a response to that peak, but it swings the pendulum too far.
What we need is a middle ground: not a blanket ban on non-financial data, but a softer approach like feerate discrimination or a voluntary filter at the application layer. Let users and miners decide, not a protocol-level dictate. This is the lesson from the DeFi Summer of 2020, where I reverse-engineered Harvest Finance and found that their yield was built on token emissions, not sustainable utility. The market corrected itself. The same will happen with Ordinals: excess will fade, and legitimate uses will remain.
The Takeaway: A Fork in the Road for Bitcoin’s Soul
This controversy will not be resolved by code alone. It will be resolved by the community choosing its identity. If BIP-110 gains traction, it may alienate the Ordinals builders and push them toward sidechains like Stacks or RSK, fragmenting the ecosystem. If it fails, Bitcoin risks becoming a dumping ground for spam, driving away regular users. Either path has consequences.
But perhaps the greatest risk is that we spend our energy fighting over the boundaries while ignoring the structural threats: miner centralization, custodial risk, and the quiet erosion of privacy. The real battle is not about a proposal—it is about whether Bitcoin remains a living, evolving system or rigidifies into a monument.
We audit the code, but who audits the conscience? The answer lies not in a BIP, but in every developer, miner, and user who chooses to build not for the peak, but for the plain.
