Saylor's 110-Point Attack on the Plan to Clean Up Bitcoin's Blockchain

On 20 July 2026, Michael Saylor, the chairman of the enterprise-treasury company Strategy, opened his laptop and spent roughly 110 points dismantling a Bitcoin improvement proposal that has been on the table for weeks. The proposal, BIP-110, would temporarily block non-monetary data from new blocks. Saylor's verdict, delivered across a roughly hour-long video posted the same day, was that the idea is bad for Bitcoin. Specifically, he argued, it would solve a narrow nuisance at the cost of breaking the network's defining political commitment to neutrality.

The fight inside this story is not really about memos on a chain. It is about who gets to decide what Bitcoin is.

BIP-110, written up by Proposing Body bitlight, would let full node operators signal a temporary block on transactions carrying so-called "spam" payloads: ordinal-style inscriptions, witness-only data stamps, and other non-payment records that have filled blocks since the 2023 boom. Proponents say it is a sanitation measure, a way to keep the base layer fit for value transfer. Critics, and Saylor now sits squarely among them, say filtering by content type is the first step toward filtering by sender. The argument has gone from technical to constitutional in under a fortnight.

What Saylor actually said

Saylor set up his case in layered and orderly fashion. The thesis in his telling: every precedent a network sets under pressure becomes a lever for the next crisis. A temporary filter, once written into the validation rules, is not so temporary. Anyone running a node in 2027 will, by default, accept the logic of content-bearing transactions being undesirable. From there, the operational surface for the next sanction, subpoena, or state-level demand opens up.

He framed the dispute in governance terms rather than engineering ones. Bitcoin's pitch to the world, he argued, rests on a single sentence that any participant can read and audit: the rules treat all valid transactions equally. The moment node runners edit that sentence case by case, the network stops being a neutral settlement layer and starts being a private club with a bouncer. Saylor also pointed to regulatory exposure. If miners and node operators can be shown to have agreed on a content-based filter, the case for treating Bitcoin as a money-transmitter business, rather than a commodity protocol, gets measurably stronger in Washington, Brussels, and Beijing alike.

The softer edge of his case landed on timing. BIP-110 arrives in a year when Strategy itself is the largest single corporate holder of bitcoin, with its balance-sheet exposure tied to the network's brand as apolitical collateral. Anything that makes Bitcoin look like a curated club, Saylor warned, dents the asset's institutional case at exactly the wrong moment.

What BIP-110 supporters want

The proposal's defenders are not naive about the slippery-slope worry. They argue that Bitcoin blocks are not infinite warehouses. The 4-megabyte weight cap was set when the dominant use-case was peer-to-peer cash, not on-chain graffiti. Allowing every passing artist, memecoin launcher, and timestamping service to permanently inscribe data, at the expense of throughput for actual payments, produces a tragedy of the commons.

BIP-110 would not delete the historical record. It would simply tell the network, for a defined period, not to relay or mine blocks carrying new inscriptions. From the proposers' vantage, this is closer to a parking ordinance than a speech code. The slippery slope, they say, is the same scare-crow cited every time a protocol evolves, and the cure is good governance, not immobilism.

The strongest counter-reading sits across the aisle from Saylor's framing. The data-surfeit on the base layer is not a hypothetical; it is the lived experience of anyone who has tried to settle a non-trivial transaction in the past six months during peak demand. Defenders also point out that Bitcoin's neutrality principle was designed to protect transactions from being stopped, not to protect every conceivable use of block space from being discouraged. Filtering block-construction spam and filtering financial transfers are different categories of decision, made by different actors, under different incentive structures. Conflating them imports a political risk that does not actually exist.

The softer governance claim underneath

Look past the technical noise and the dispute is structural. Bitcoin's consensus rules are its constitution, and constitutions get amended, sometimes well, sometimes badly. The 110 points in Saylor's video are not all about mempool policy. A surprising number are about process: who gets to propose a soft fork, how a soft fork is socialised, what counts as sufficient consent from miners and node operators, and what happens when a deployment is rushed. In that sense, Saylor's intervention is a warning about the protocol's emerging governance class as much as it is an argument about filter design.

A soft fork, by definition, tightens the rules. Nodes that do not upgrade simply stop seeing themselves as part of the validation set on the affected path. Each successful soft fork narrows the ambient tolerance of the network for unusual transactions. Each one raises the marginal cost of dissent. Saylor's deeper worry is not that BIP-110 is wrong today; it is that a practice of editing the rules at the margin produces, over a decade, a network that defends politically comfortable outcomes by default. The chain that cannot censor in 2026 might find the muscle memory to do so in 2032, simply because the workflow has been rehearsed.

Who actually decides

The decision in front of the network this summer is unusually stark. BIP-110 is a soft fork in name but a precedent vote in practice. Adoption will turn on miner signalling and on whether node operators adopt the new validation logic on their own machines. Strategy does not mine. It runs a balance sheet. Saylor's lever here is reputational. He tells holders, analysts, and the institutional curious, who together set the price the network is asked to defend, that this is a path worth opposing. That is a kind of soft power in a system that has never had any other kind.

The plausible paths over the next two quarters look like this. BIP-110 either reaches the rough consensus required to deploy, in which case node operators either adopt or fork themselves off into a parallel chain; or the proposal stalls under activist pressure, in which case the inscription economy continues until native fee markets churn through the demand; or a compromise emerges that addresses the throughput complaint with a fee or witness-data accounting tweak that does not touch the content-neutrality rule. Saylor's intervention improves the odds of the second and third outcomes by making the cost of casual support visible.

What remains genuinely contested is whether the existing neutrality principle can survive the next capacity crunch without some operational form of prioritisation. The sources do not settle that. Neither does Saylor's video. The hard question, whether any content-bearing filter can be designed in a way that does not create the lever future censors would reach for, is the one the community will have to face whether or not BIP-110 ships. Saylor's 110 points do not so much answer that question as refuse to let it be answered quickly.

This article was researched against wire reporting at the time of publication and reflects the public positions named above; the debate inside the developer community is moving quickly and may have advanced by the time of reading.