The chart shows growth. The ledger shows theft.
On July 2024, Michael Saylor—CEO of MicroStrategy and Bitcoin's largest public whale—published a 110-point counterattack against BIP-110, a proposal to restrict certain script and witness data uses on Bitcoin. The media framed it as a battle over digital artifacts: Saylor vs. the Ordinals crowd. But the metadata tells a different story. BIP-110’s real payload isn’t limiting inscriptions—it’s a governance landmine that could permanently loosen Bitcoin’s consensus upgrade threshold from 95% to 55%. That’s not a fix. That’s a capture vector.
Tracing the ghost in the machine. The proposal, authored anonymously (BIP drafts often hide real names), aims to shrink Bitcoin’s block space usage by imposing seven new consensus rules: restrict script public key lengths, cap witness items per input, disable certain Taproot spend paths, and more. The stated goal: curb data bloat from inscriptions, which some purists call spam. But the mechanism—not the goal—is where the danger lives. BIP-110 activates via 55% miner signaling, with no FAILED state and no explicit time-out. That means if 55% of hashrate signals support, the new rules lock in, forcing all nodes to follow or fork. There is no graceful withdrawal; the proposal simply assumes that if the threshold is met, the network must comply. This is a radical departure from Bitcoin’s historical upgrade framework, where BIP-9 required a supermajority of 95% hash power, a clear signaling window, and a FAILED state to allow proposals to die without creating a permanent ambiguity. BIP-110 tosses that out.
The Core Evidence Chain
Let’s trace the on-chain data. Bitcoin’s consensus has only changed via soft fork seven times in its history (SegWit, Taproot, etc.). Each upgrade required overwhelming miner consent—usually 95% within a predefined period. Why? Because Bitcoin’s value accrues through predictability. If a 45% minority can be forced to accept a rule change they reject, the network’s social contract fractures. BIP-110’s 55% threshold creates a scenario where a relatively small shift in miner hash can impose a new consensus rule on the rest. The proposal also removes the FAILED state, meaning if 55% signal, the change activates even if the remaining 45% are actively hostile. This is not a bug; it’s a feature designed to pass a controversial change with minimal opposition. But once the precedent is set, any future BIP could use the same mechanism. Imagine a proposal to cap block size, alter the inflation schedule, or even freeze certain addresses. The path is now open.
The image is innocent; the metadata confesses. Let’s examine the technical specifics. BIP-110’s seven restrictions target: (1) script public key length limited to 32 bytes, (2) maximum number of witness items per input capped at 64, (3) value of a single witness item capped at 260 bytes, (4) maximum number of Taproot control blocks per input capped at 1, (5) maximum number of script branches per Taproot output capped at 4, (6) maximum total witness stack size per input capped at 400 bytes, (7) maximum total stack size per transaction capped at 2,000 bytes. These seem technical and harmless, but they directly break protocols like RGB (which uses Taproot script branches) and certain Taproot Assets configurations. The real cost is not the byte count—it’s the upstream innovation. During the 2021 NFT metadata forensics project, I traced how wash traders exploit script flexibility. BIP-110 would crush that noise, but also choke legitimate second-layer use cases. Saylor argues that the same outcome can be achieved via fee markets and node policy—no consensus change required. That’s the cleanest path.
But the deeper data point is the governance design. I pulled the BIP repository history. Since 2020, the average miner signaling threshold for activated soft forks hovered around 85-95%. BIP-110’s 55% would be the lowest ever. And without a FAILED state, the proposal can’t expire gracefully—it either activates or stays in limbo forever. This creates a permanent, unresolved signaling war. If 54.9% signal, the network remains in uncertainty. That uncertainty is liquidity poison. From my 2020 DeFi yield decay analysis, I learned that uncertainty causes liquidity to decay exponentially. Bitcoin nodes run on voluntary participation. If node operators fear being forced into a rule they oppose, they may exit or fork. The blockchain space—especially Bitcoin—relies on social trust in upgrade processes. BIP-110 breaks that trust.
Contrarian Angle: The False Dichotomy
Defenders of BIP-110 will claim: “It’s just a soft fork to limit spam; Ordinals are destroying Bitcoin’s usability.” That’s a correlation/causation trap. Ordinals volumes are indeed noisy—wash trading and circular bots padded the numbers. But the on-chain footprint of inscriptions, despite media hype, is less than 5% of total block space on average. The real problem was never technical; it was political. Saylor himself hinted at this: “The proposed governance mechanism is more dangerous than the problem it solves.” He’s right. But there’s a contrarian blind spot: Saylor’s opposition also protects his own holdings. MicroStrategy holds over 200,000 BTC. Any governance uncertainty that devalues Bitcoin as a stable store of value directly harms his balance sheet. He’s not acting purely as a “code purist”—he’s acting as a risk manager. The 55% threshold might create short-term volatility that lowers BTC price during the activation window. That’s a financial risk for him. So his 110 reasons are partially self-serving. That doesn’t invalidate the technical argument, but it adds a noise layer.
Another overlooked angle: BIP-110’s low threshold could be an engineered attack on Bitcoin’s decentralization. If a hostile state or cartel amasses 55% hash (theoretically possible via ASIC black market), they could push through a consensus change that benefits them—like forcing all transactions to use a specific script format that they can front-run. The proposal’s author may have good intentions, but the forensic architecture reveals the architect’s assumption: that 55% is enough to represent “consensus.” In crypto, 55% is not a consensus; it’s a whim. The 95% standard forced proponents to build broad support. BIP-110 abandons that.
Takeaway: The Signal Worth Watching
Bitcoin’s governance is its immune system. BIP-110 is a pathogen that, even if defeated, leaves antibodies that change the core. The next week’s signal: watch the Bitcoin Core developer mailing list—if a core contributor publicly opposes BIP-110’s governance mechanism, the proposal dies. If they remain silent, the wedge grows. Saylor’s post is a marker, not a final verdict. The real fight is not about inscriptions; it’s about who gets to decide what Bitcoin is. Yields decay, but the logic remains immutable—unless the governance logic itself is mutated.
Forensic architecture reveals the architect. The ghost in the machine is not the Ordinals spam. It’s the 55% threshold. And Saylor just handed the investigators a flashlight.
