Every objection raised against BIP-110 in the Fork Talk Telegram group—triaged against the data. Millions of spam transactions vs. hypothetical edge cases.
This article is a work in progress. More objections are being sought and the analysis is being refined.
Before evaluating any objection, understand the scale mismatch between the problem and the complaints about the solution.
Data sourced from Bitcoin Block Space Weekly (Renaud Cuny). 3.5 years of on-chain analysis.
1,250x increase — merged despite 4:1 community opposition
Non-financial txs fill 41% of block space for 0.08% of block reward (0.00262 BTC/block difference).
RC1 had functional and fuzz test failures. The code audit identifies gaps: off-by-one at the OP_RETURN 83-byte boundary, untested witness versions v3-v16, expiry test that logs but never asserts, untested mandatory signaling boundaries.
These are real bugs in development software. They are being fixed. v0.3 already addressed the cache-poisoning issue. This is the normal process of shipping software—every Bitcoin Core release has had bugs in RC stages.
This is not a design objection. It says nothing about whether BIP-110 should exist. It says the code needs more testing before deployment. That's true of all software.
These objections sound technical but concern a negligible fraction of real Bitcoin usage. They exist to create the appearance of serious trade-offs where the data shows none at scale.
Disabling OP_IF in tapscript is aggressive and affects legitimate use cases. Raised by: Rijndael, Not Me, friendly nym, Adam Back, Super Testnet
"This BIP is the epitome of a pareto principle failure. 2-7 cause >80% of the work for <20% of the result."— friendly nym
How many tapscript transactions use OP_IF on mainnet? A vanishing fraction. The overwhelming majority of taproot usage is key-path spends that never touch the script tree. We are discussing a temporary 1-year restriction on an opcode used in a fraction of a percent of transactions, protected by a grandfather clause on all existing UTXOs.
Meanwhile, millions of data-embedding transactions hit the chain daily. Treating a rounding error as a showstopper for action against a measured, ongoing problem is not serious engineering—it's obstruction dressed as caution.
"BitVM anchors need ~256b OP_RETURN space." Raised by: Adam Back, Rijndael
BitVM has zero transactions on mainnet. No deployed contracts. No users. No anchors. It is a research project.
Blocking a proposal that addresses millions of real spam transactions to protect a research project with zero real-world usage is not a technical argument—it is using vaporware as a human shield. The 1-year auto-expiry means that if and when BitVM deploys, the temporary restriction will have already ended. This objection was designed for precisely this scenario.
Lower than the standard 95% used for permanent soft forks. Activating with 45% of hashrate opposed risks a chain split. Raised by: Various
This is one of the objections where there may be genuine substance, though much of the surrounding debate contains enough rhetorical noise that the underlying issue is often obscured. The game theory analysis argues that rational miners will converge on the dominant chain, but that is a partial treatment. A fuller analysis must examine how MEV and inscription-related revenue concentrate across mining pools. It must also weigh countervailing factors such as liability exposure, since miners facilitating arbitrary data embedding face risks related to illegal content and regulatory scrutiny.
At the network level, Nakamoto consensus continues to provide strong convergence incentives (see white paper, section 6). Subsidy dominance and the asymmetric cost of mining on a minority chain have driven convergence across every soft fork to date. The open question is the full rational calculus for an individual miner — not only direct fee revenue, but also liability exposure, insurance costs, network health, price appreciation, and other externalities. That is where the real analysis is needed.
"What if it activates without overwhelming consensus?" Raised by: Aaron, zender, Adam Back
This is closely related to the threshold question above. Every soft fork carries chain split risk — SegWit, P2SH, CLTV, CSV — so this objection is not specific to BIP-110. Raising it as a unique risk without that context is misleading.
That said, Nakamoto consensus keeps the network together through strong game-theoretic incentives (see white paper, section 6). The inscription fee premium is ~0.08% of total block reward. A fuller analysis of the miner-rational case — as outlined in T3 — would address both the threshold and chain split concerns together, and deserves dedicated analysis beyond the scope of this article.
The Pareto argument: rule 1 delivers most of the value; rules 3-7 add complexity for diminishing returns. Raised by: friendly nym, Not Me
If someone says "I'd support rules 1-2 but not 3-7," that's constructive. But the people raising this objection don't support any version. The "scope" critique creates the appearance of reasonable engagement while ensuring no version is ever "right enough."
This is a negotiation tactic, not a technical objection. The tell: ask them if they'd support a 1-rule version. They won't.
Technically flavored but built on circular reasoning, false dilemmas, debunked claims, or double standards.
"Spammers will just use fake pubkeys, stamps, runes—it's information-theoretically impossible to stop." Circular Reasoning
Chris Guida's data: 99% reduction when filters are active. That is the empirical answer.
Peter Todd created Libre Relay (a bypass tool) then cited its existence as proof limits don't work—textbook circular reasoning. By this logic we shouldn't have locks on doors because lockpicks exist.
"Presigned transactions could become unspendable—de facto confiscation." Misleading Debunked
The grandfather clause exempts all pre-activation UTXOs. The code audit confirms correct implementation with per-input flag override. This objection has been answered in the BIP text, the code, and every public discussion. Continuing to raise it is not ignorance—it is deliberate misinformation.
"Hugely risky and wild idea." Appeal to Tradition
The auto-expiry (~52,416 blocks) means the worst case is that the restriction simply ends. The code audit confirms it genuinely auto-expires. Every Bitcoin feature was unprecedented once. "We've never done it" is an appeal to tradition, not a technical argument.
"The salvageable parts should be folded into the Great Consensus Cleanup." Delay Tactic
GCC has no timeline, no activation mechanism, and no delivery date. Meanwhile millions of spam transactions hit the chain daily. "Wait for GCC" is functionally identical to "do nothing." If the parts are salvageable, ship them now; GCC can supersede later.
"40k lines of under-reviewed changes." Genetic Fallacy
Core v30 merged OP_RETURN changes despite 4:1 opposition. The "review process" argument cuts both ways. Knots surged from 2-4% to 21% because users lost confidence in Core's process. Smearing the alternative while defending the governance failure that created demand for it is not a technical argument.
Low early signaling numbers prove failure. Snapshot Fallacy
Miners rationally wait until the deadline—early signaling reveals strategy. SegWit: months of near-zero signaling, then rapid cascade in a single retarget period. The game theory analysis explains why current numbers are not predictive. Citing them as proof of failure is either ignorant of game theory or deliberately misleading.
Without OP_RETURN, data goes into UTXO-polluting methods. False Dilemma
False binary. The 80-byte limit operated for a decade without either problem. The OP_RETURN analysis documents how this framing was manufactured to justify a 1,250x increase that primarily benefits VC-funded data projects like Citrea.
"Needs a different champion who can suppress their anger about disagreed narratives." Ad Hominem
The code works or it doesn't. The game theory holds or it doesn't. Tone-policing the author is deflection—especially from someone who uses "pleb slop," "douche-bags," and "stop the grandstanding" in the same chat.
"If 55% can activate this, what stops 51% changing the 21M cap?" Slippery Slope
The instinct to think about precedent is sound. But every fork happens in a completely different environment. The next fork will involve different technology, a different reward epoch, different developers, different hardware, different economic conditions, and different community dynamics. The slope is not fixed — it changes with every variable.
Vigilance about precedent is healthy, and this concern comes from a good place. But a temporary spam filter and a permanent monetary policy change have entirely different incentive structures. The Bitcoin community would never accept inflation — it is the one consensus rule that unites every participant in the network. Ideally, no soft fork would be needed at all — if Core reverted the v30 change, BIP-110 would be unnecessary. BIP-110 exists as a backstop in case they don't. The concern is worth keeping in mind, but the two situations are not comparable in practice.
No technical content. Rhetorical tactics used to create the impression of opposition without substance. These are not arguments to be answered but tactics to be recognized.
DARVO. BIP-110 is a community response to Core v30's unilateral removal of a decade-old protection, merged despite 4:1 opposition. Characterizing the defensive response as the "attack" while ignoring the precipitating action is textbook Deny, Attack, Reverse Victim and Offender. — Alex Thorn, Orange Heart, zender, Bitcoin Eagle
Gaslighting. 80 bytes to 100,000 bytes is a 1,250x increase. Defaults determine behavior for 95%+ of users. If it truly didn't matter, there would be no reason to change it—and no reason to fight BIP-110. — Various Core proponents
Appeal to popularity. Prediction markets reflect sentiment, not technical merit. SegWit would have had terrible odds for most of 2016-2017. Markets are manipulable. Not a technical argument. — Aaron, various
Bandwagon fallacy. Knots: 2-4% to 21%. OP_RETURN PR: rejected 423-105. The data says otherwise. — Various
Smear. Associating a software preference with Nazism. Zero technical content. Documented in the OP_RETURN analysis as part of the villainization playbook. — External social media
Ad hominem at institutional scale. Character attacks, religious mockery, DNS seed removal, GitHub muting. The proposal's merit is independent of its author. — Various
Class contempt. Dismissing community concerns as beneath engagement. A power move, not a rebuttal. — Adam Back
Deflection. "Stop the grandstanding." Redirecting from substance to delivery. Used to shut down discussion when points can't be answered on merit. — Adam Back
Tu quoque. When documented conflicts (Lopp/Citrea, Todd/Libre Relay, Poinsot/Chaincode) are raised, the response is to attack BIP-110 proponents' associations. "You too" is not a rebuttal. — Various
Gaslighting. "Lols AXA bilderberg enough to stop reading." Blockstream's AXA investment and Epstein-linked funding are documented by The Guardian. Dismissing documented facts as conspiracy—without engaging the evidence—is itself gaslighting. — Adam Back
False equivalence. One side changed a decade-old default unilaterally despite 4:1 opposition. The other is responding. These are not symmetrical positions. — Adam Back
Intimidation. Economically suicidal given subsidy dominance. Raised to inflate the perceived cost of supporting BIP-110. — Various
Moving goalposts. No BIP has ever met this standard. Absurd on its face. — Adam Back
Gaslighting. Luke muted on GitHub. Mechanic muted. DNS seed removed. Gloria Zhao resigned. Critics called "abusive." All while defending "censorship resistance." The contradiction is documented.
Of the ~30 distinct objections raised against BIP-110 in the Fork Talk chat:
This is not a balanced technical debate. It is a campaign to manufacture doubt against a data-backed proposal using theatrical objections and information warfare. The objections are performance; the data is real.
The material objections are bounded, temporary, and affect a rounding error of transactions. The problem they're blocking action against is unbounded, growing, and affects every node on the network every day.