
Jameson Lopp's BIP-110 Recap: Bitcoin Is Driven by Game Theory, Not Morality
Author: Liu Jiaolian
As summer draws to a close, BTC continues to oscillate in the $64k range. Volatility is so low it induces sleepiness, with both on-chain and off-chain activity quiet as a mouse, akin to the anxious waiting before a major production begins.
In recent months, a year-long saga within the Bitcoin community has finally reached its curtain call. On August 9, the mandatory signaling window for BIP-110 opened. By August 10, the fork had already fizzled out after two blocks. On August 11, the OCEAN mining pool announced the return of its hashing power, Luke Dashjr resigned, and the BIP-110 proposal was closed. Earlier, Jiaolian published an article titled "BIP-110 Fails, Luke Dashjr Resigns" to document the incident.
Now that dust has settled, Jameson Lopp, one of the opposing KOLs, has published a lengthy post-mortem on BIP-110. He methodically cross-references his prophecies from six months ago and meticulously archives the supporters' grand promises over the past year. The original text is too long; below is a condensed translation for readers to reference.
Prophecies Fulfilled
Six months ago, in February 2026, Lopp wrote an "Outsider's Guide to BIP-110" (see the condensed translation I posted on March 3, 2026, titled "Lopp Opposes BIP-110"), asserting that the proposal was reckless and doomed to fail. At that time, he made four specific prophecies. Now, let's review them:
First, radicals would inject child pornography into the blockchain to extort miners and node operators. This has not happened yet, but Lopp believes conditions are nearing maturity similar to how Luke Dashjr dubbed the un-upgraded Bitcoin chain "Bpedo" (pedophile coin): injecting prohibited content before a fork would taint both chains, whereas after a fork, there would be no such concern. (Author's note: Lopp might be stretching the interpretation here. Luke used the term Bpedo to attack the chain without BIP-110 support in a post on May 27, 2026, which predates the failure of the BIP-110 mandatory signal.)
Second, BIP-110 would never reach the 55% activation threshold. Once block height 961,632 arrived in early August, nodes running BIP-110 code would simply fork off the Bitcoin network. This proved entirely accurate.
Third, if OCEAN were the only mining pool supporting the fork, with its roughly 1% share of total network hash rate, it would only produce 1 to 2 blocks per day, requiring nearly three years to wait for the next difficulty adjustment. This also came to pass; OCEAN indeed set BIP-110 as the default stratum template, becoming the sole supporting pool.
Fourth, rational miners would not persist on a minority fork for long, as they could not practically cash in block rewards. This too proved correct. Across the entire BIP-110 forked chain, only a small self-styled group called the Roughnecks mined all 4 blocks before bowing to economic reality. They returned the next day, burning the cost of mining 2 blocks, and finally gave up completely. OCEAN later compensated the miners whose hash rate was diverted.
All four prophecies hit the mark. Lopp states that this requires no mystical foresight, nor does it imply membership in some conspiracy group as theorists claim. The reasoning is straightforward: it is simply the result of economic trade-offs on both sides.
Economic Weight
Every major Bitcoin split has come down to economic weight, not slogans.
In 2017, Bitcoin Cash had Roger Ver and Jihan Wu behind it, the largest ASIC manufacturers, and massive financial capital swapping positions. Despite such heavyweight capital alignment, it still failed to convince the ecosystem to follow. BSV had Calvin Ayre backing it, along with mining farms, hashing power, and endorsement from the supposed Satoshi Nakamoto figure (Craig Wright). Yet it only convinced a tiny fraction.
What did BIP-110 have behind it? Lopp summed it up as a pleb movement among the loudest supporters: few wealthy individuals and even fewer companies. Its biggest associated entity, OCEAN, is already one of the smallest pools in the industry. Moreover, OCEAN management distanced themselves afterward, stating this was merely the personal view of Luke Dashjr and Bitcoin Mechanic.
More critically, previous splits promised economic benefits: higher throughput, lower fees, and expanded functionality. What did BIP-110 promise? Purity, morality, feature removal, and reduced miner income.
Bitcoin is driven by incentives and game theory, not morality [1]. When reviewing the events in "BIP-110 Fails, Luke Dashjr Resigns," I wrote that the economic base determines the superstructure. We must acknowledge that morality can only grow within structures of interest, never the other way around.
Lopp further argues that the market provided the answer long ago. He publicly proposed a trustless futures contract bet on the fork outcome, but no one took the challenge; supporters only replied with moral preaching. The only operational BIP-110 prediction market saw total volume of merely 4.6 BTC, with win probabilities consistently languishing below 20%. Capital votes with its feet, proving more honest than any verbal sparring.
Historical Context
Lopp reviews the anti-spam debate, which dates back almost as far as Bitcoin itself.
In December 2010, Satoshi implemented standardness checks in version 0.3.18, accepting only known transaction types. In 2014, OP_RETURN was introduced as a pressure release valve, initially capped at 40 bytes, with Core's release notes explicitly stating that arbitrary data storage remained discouraged. Between 2014 and 2015, protocols like Counterparty circumvented these limits by encoding data into multi-signature structures, sowing seeds of philosophical division. In 2015, Core relaxed the OP_RETURN cap to 80 bytes, and later that same year, large-scale stress tests clogged the network.
From 2016 to 2021, a fragile equilibrium emerged: the consensus layer remained permissive, relay policies rejected or discouraged certain transactions, miners decided what went into blocks, and fees priced scarce block space. SegWit in 2017 and Taproot in 2021 altered the cost structure of data publishing. SegWit discounted witness data, while Taproot relaxed script size limits. This wasn't designed for NFTs, but objectively made arbitrary on-chain data cheaper.
In 2023, Inscriptions ignited fierce debate. Supporters framed it as permissioned payment for block space, while opponents dismissed it as spam exploiting loopholes. From 2023 to 2024, the discourse shifted to whether nodes should filter Inscriptions. Luke Dashjr advocated for stricter relay filtering, but Core refused a blanket ban, reasoning that those truly intent on publishing data could directly deliver transactions to miners or hide data within other compliant structures, making filtering inherently fragile.
In 2025, the original OP_RETURN logic underwent a reversal. Core developers observed that the ~83-byte policy limit forced protocols like Citrea to circumvent rules in worse ways, including creating permanently unspendable UTXOs. Consequently, Core 30 casually lifted the default OP_RETURN cap to 100,000 bytes. Lopp points out that this change was a reactive measure, not proactive innovation. It generated no new network activity; it merely acknowledged established facts.
Then came 2026, with BIP-110 stepping in to restrict arbitrary data encoding via consensus rules. As supporters' narratives grew increasingly desperate, they ultimately slipped into extreme rhetoric centered on child pornography.
A recurring pattern emerges here: block one data channel, and users find another. Developers then debate whether to tighten filters further or permit the least harmful pathway. Trying to stop the people's mouths is harder than damming a river. Data flows like water; it cannot be blocked.
Technical Failure
Lopp continues the review, noting that BIP-110's failure was not merely economic but technically disastrous.
The first release candidate (RC1) in December 2025 suffered failed functional tests, failed fuzz testing, skipped tests, and uploaded binaries prior to signing. Core maintainer Michael Ford advised waiting for subsequent versions, while developer Rob Hamilton bluntly warned that the client likely still contained consensus bugs—a prediction he unfortunately repeated multiple times. A script execution cache poisoning vulnerability was discovered in February. In June, incompatibility with Miniscript wallets was found; upon activation, certain addresses would become unspendable, triggered even by Knots' own wallet, potentially causing users to lose funds. Ironically, Knots degraded its own node sync performance due to mistakenly disabling script caching. It wasn't until two weeks before activation that anyone discovered an undocumented eighth consensus rule hidden within BIP-110's implementation.
The fundamental failure lies in the fact that BIP-110 could never block what it intended to block from day one. Just three hours after the proposal's release, Peter Todd embedded the entire BIP text into a fully compliant transaction. Since then, various experts took turns demonstrating workarounds. Some embedded continuous images using non-Taproot paths. Others proved that nearly 4MB of continuous data could be injected under BIP-110 rules. Another initiative, RIP 110, demonstrated that every Bitcoin transaction could essentially be a JPEG. Meanwhile, through the ADVENT series, daily updates featured GIFs, PDFs, MP4s, WASM executables, tar.gz archives, and even entire malware directories—all embedded on-chain in BIP-110-compliant formats, at costs a quarter of those using OP_RETURN.
Lopp writes that Greg Maxwell pierced this veil long ago: BIP-110 itself concedes that technically preventing arbitrary data is impossible, yet proponents' rallying cry aims to eradicate spam. Pushed to such contradictions, they pivoted to cultural arguments, claiming the goal was merely to send a signal that certain use cases are intolerable.
The Child Protection Card
Debates across both eras ultimately played the exact same card: protecting children.
During the scaling debates, Roger Ver's claims that babies were dying drew years of ridicule. In the BIP-110 era, this card was played even more extremely, with supporters labeling BIP-110 opponents as pedophile sympathizers.
Lopp comments on this: accusing someone of pedophilia because you deem combating arbitrary data on censorship-resistant protocols futile is as absurd as claiming gun rights advocates endorse school shootings. Forcing consensus by slapping labels on opponents has never been a sound strategy [1].
Reasonable people do not need moral high ground to win debates. Truth becomes clearer through discussion, relying on facts and logic, not accusations.
Proponents' Arguments
In the article, Lopp also catalogs the main arguments put forth by BIP-110 supporters over the past year, offering them for future reflection to trace their step-by-step slide into delusion.
On technical mechanisms, proponents emphasize that the activation code is designed to be infallible. BIP-110 adopts a modified BIP9 timeline with no timeout, a 55% miner signaling threshold, a maximum activation height, and a mandatory signaling phase. The specification explicitly states it will never enter a FAILED state, with mandatory signaling guaranteeing lock-in no later than the designated height. Once mandatory signaling begins, blocks lacking the signal are rejected by BIP-110 nodes, making silence a punishable act. Proponents also argue that the 55% threshold is significantly lower than the 90%–95% typically required for soft forks. Given the temporary nature of the proposal—which auto-expires after one year—it can be accepted as a reversible emergency measure.
From a game theory perspective, proponents argue that signaling costs are near zero, while failing to signal could cost an entire block reward. Once 55% of hash rate executes BIP-110, the silent 45% faces orphaned block risks in fork competition. Rational miners would not gamble trivial inscription fees, even if they verbally oppose now; they would defect as the deadline approaches. Regarding current low signal rates, supporters note signals are measured per 2016-block periods, making early declarations meaningless. The real action will occur in a last-minute cascade. Once signals approach 30%–40%, stragglers fear being left behind, causing signals to rapidly snowball toward 55%.
Pointing to historical precedents, supporters cite the 2017 SegWit/UASF case, claiming gridlock can flip rapidly under credible deadline pressure. Lopp finds this particularly laughable since the 2017 BIP-148 UASF never actually triggered; it was preempted by BIP-91. Supporters also invoke the notion that users, not miners, define Bitcoin, arguing that exchanges, custodians, wallets, merchants, and users decide which chain counts, forcing miners to follow value. Lopp remarks that while the statement itself isn't wrong, proponents consistently dodge one fact: BIP-110 has never received backing from any economically significant entity.
Narratively, supporters frame Inscriptions as exploiting a known vulnerability (CVE-2023-50428), positioning BIP-110 as patching rather than censoring. Citing simulation data, they claim it filters most non-financial transactions with zero collateral damage, dismissing objections as edge cases and theoretical exercises. They raise legal risk concerns, asserting that arbitrary on-chain data exposes every full-node operator to liability. Regarding node adoption, proponents highlight the ease of Knots' one-click installation and rising node market share. Lopp counters that node count is the easiest metric to inflate; charts showing growth are merely self-comforting illusions.
Finally, a supporter named Rene Cuard created a website modeling activation probabilities, which once indicated BIP-110's victory chances exceeded 50%. However, the site stumbled when attempting to list economically backed entities supporting the proposal, with many entries lacking any verifiable evidence.
Future Predictions
After reviewing the past, Lopp offers predictions for the future, asserting that:
First, everyone who staked their reputation on this spectacle will continue complaining and weeping, regardless of whether they follow the hard fork or sneakily retreat back to Bitcoin. A timeless theme of failed forks is that failure is never the fault of the forkers; it's always some conspiracy where others didn't fight fair.
Second, the puritans will not stop until they launch a network banning everything they despise. But they will eventually discover their warnings were accurate: whatever new network they launch, someone will inevitably fill it with arbitrarily encoded data, purely to annoy these nitpicking gatekeepers of block space.
Third, the most devout puritans will sell their Bitcoin. Luke has already stated he did so. (Author's note: That reads as a bit speculative, considering Luke Dashjr had the vast majority of his BTC stolen by hackers in late 2022. See my Dec 25, 2024 article "Lost Coins" for details.) Matthew Kratter and others claim they expect to sell. Lopp asserts this will be a poor financial decision, mirroring those who sold Bitcoin in favor of BCH or BSV back in the day.
Fourth, regardless of what Luke names that hard-forked chain, it will neither surpass BSV in exchange rates nor adoption, and will barely list on any major exchange. Exchanges list tokens based on expected trading volume or substantial listing fees—neither of which apply to these puritan fork coins.
Final Summary
Lopp's final summary consists of a few passages directed at the puritans:
"You dislike seeing people do foolish things with Bitcoin. Welcome to the party; hardly anyone interested in Bitcoin wants to see foolishness encoded into the safest permanent record on this planet. But the question is whether you allow yourselves to be provoked by it. When others do things you disagree with, do you continue living your life, or do you become the hated 'nitpickers' of the community, dedicating your lives to stopping others from acting in certain ways."
"Nearly everyone agrees this is not a war worth fighting, because the battlefield holds an asymmetric advantage for those wanting to shove data into the blockchain. You cannot force us into a war we don't want to fight, just as we cannot stop you from waging the crusade you desire. So enjoy your obsession, but do not drag us into the trenches."
Lopp also notes that California attorney Asaf Fulks released a project attempting to establish a legal and technical framework for Bitcoin consensus changes. Measured against his standards, why BIP-110 falls short of the threshold is immediately obvious.
As for the lessons learned, Lopp concludes that this spectacle validates all assertions regarding game theory and network dynamics. The false narratives fabricated by puritans should be tossed into the ashcan of history. A user-activated soft fork (UASF) with overall low support does not require a user-refused soft fork (URSF) to halt it; it will fail on its own. A UASF demands far more than the backing of a vocal fringe. And labeling every opponent a pedophile, CSAM defender, or Epstein accomplice has never been a sound strategy for building consensus.
Finally, Lopp closes with a sarcastic remark: "Congratulations, you Bitcoin puritans. You complained on social media for years, then complained for another year at conferences, and what did you achieve? In a delightfully ironic twist, you successfully manufactured a worthless shitcoin."














