What Is BIP-110? Bitcoin’s Data Limits and Fork Risk Explained

TL;DR

• BIP-110 proposes a temporary soft fork that would restrict several ways arbitrary data can be embedded in Bitcoin transactions.
• Supporters say the limits would protect node operators, reduce non-payment data use, and refocus Bitcoin on money.
• Critics argue that converting a “spam” dispute into consensus rules threatens neutrality, future protocol development, and chain stability.
• Miner signaling was 0.83% as of July 20, 2026, far below the 55% early-lock-in threshold. Without a major shift, mandatory signaling could isolate BIP-110 nodes on a minority chain.

Introduction

BIP-110, formally called the Reduced Data Temporary Softfork (RDTS), is one of Bitcoin’s most divisive protocol proposals in years. It targets transaction structures used by Ordinals, inscriptions, BRC-20 tokens, and other forms of non-payment data.

Yet the deeper dispute is not about images or tokens. It is about where Bitcoin should draw the line between optional node policy and network-wide consensus—and how much agreement should be required to change that line.

What Would BIP-110 Change?

The BIP-110 specification would apply additional consensus rules for roughly one year after activation:

• New output scripts would generally be limited to 34 bytes, while OP_RETURN outputs could use up to 83 bytes.
• Data pushes and script-argument witness elements would be capped at 256 bytes.
• Taproot annexes, large control blocks, OP_SUCCESS opcodes, and executed OP_IF or OP_NOTIF instructions in Tapscript would be restricted.
• Inputs spending UTXOs created before activation would be exempt throughout the deployment.

These rules would make several popular data-embedding methods invalid under BIP-110. They would not make arbitrary data impossible to store. Data can still be divided, disguised, or encoded through permitted structures, although supporters argue that greater cost and complexity would discourage such use.

Policy vs Consensus: The Key Distinction

Bitcoin nodes already choose which unconfirmed transactions to relay or mine through configurable policy. Bitcoin Core 30.0 increased the default OP_RETURN data-carrier setting to 100,000 bytes and allowed multiple OP_RETURN outputs, but node operators can still restore a smaller limit.

These are policy choices: a transaction rejected from one node’s mempool may still be valid in a block.

BIP-110 moves the dispute to consensus. During its active period, upgraded nodes would treat transactions violating its limits as invalid even if they pay fees and remain valid under today’s Bitcoin rules. That jump from local filtering to global validity is the heart of the controversy.

How Would BIP-110 Activate?

BIP-110 uses version bit 4 and a modified BIP9 deployment. Early lock-in requires 1,109 of 2,016 blocks—55%—to signal in one difficulty-adjustment period.

If that never happens, enforcing nodes enter a mandatory-signaling window from blocks 961,632 through 963,647. They reject blocks that do not signal bit 4, with lock-in scheduled no later than block 963,648 and activation at block 965,664. The rules expire after 52,416 active blocks, or approximately one year.

“Mandatory” applies only to nodes running the BIP-110 rules. Existing Bitcoin nodes will continue accepting non-signaling blocks. If most hashpower remains on the existing chain, BIP-110 nodes could reject that chain and follow a much slower minority branch. The schedule therefore cannot manufacture network-wide consensus by itself.

Why Supporters Believe It Is Necessary

The proposal’s author, Dathon Ohm, and early contributor Luke Dashjr argue that arbitrary data creates distorted incentives. Miners receive a one-time fee, while every full node must download and preserve the resulting blockchain data. In their view, non-payment uses compete with monetary transactions, raise infrastructure costs, and risk turning Bitcoin into a general-purpose data layer.

Supporters around Bitcoin Knots and OCEAN also frame the proposal as temporary and deliberately narrow. Pre-activation UTXOs are grandfathered, known monetary use cases are intended to remain available, and the one-year sunset gives developers time to design a more durable solution.

Dashjr has described failure in existential terms, arguing that Bitcoin must actively defend its role as permissionless money.

Why Critics Consider It Dangerous

Michael Saylor accepts the goals of affordable nodes and accessible payments but rejects consensus-level policing of transaction purpose. His concern is precedent: if currently valid, fee-paying transactions can be invalidated because their use is unpopular, future disputes could target privacy, authentication, contracts, or applications that do not yet exist. He has called BIP-110 a “Bitcoin Iatrogenic Proposal”—a treatment that may cause more harm than the condition.

Adam Back argues that telling users how they may use valid block space conflicts with Bitcoin’s cypherpunk neutrality. In his view, supporters are free to fork, but cannot assume the wider network will follow without broad coordination.

Jameson Lopp’s objections are more technical. He highlights the 55% threshold and mandatory signaling as chain-split risks, points to edge cases involving Taproot and Miniscript, and argues that the limits constrain future upgrades without stopping determined data embedding.

BIP editor Mark “Murch” Erhardt separately stresses that publishing or completing a BIP is not an endorsement and that minority node counts do not replace economic consensus.

Even OCEAN is not a single bloc. Jason Hughes, its vice president of development and engineering, wrote on July 17 that he was neither pro- nor anti-BIP-110, but saw no measurable majority behind it. Based on current adoption and mining data, he estimated its chance of success at below 5%.

Where BIP-110 Stands

At 01:05 UTC on July 20, 2026, the public signaling monitor recorded 10 signaling blocks out of 1,203 in the current period, or 0.83%. The highest completed-period rate was 0.99%, still far below 55%.

Bitcoin Core has not merged BIP-110, and public node counts remain disputed because reachable nodes are easy to multiply and do not reveal their economic weight.

If these conditions persist, the most likely outcome is not a network-wide Bitcoin upgrade. It is either no lasting fork because enforcing users revert, or a small minority chain with limited hashpower and uncertain market infrastructure.

Why Investors Should Care

A clean rejection would reinforce Bitcoin’s high threshold for consensus change. A late surge in miner and economic-node support would force wallets, custodians, and miners to prepare quickly.

A disorderly split could create temporary uncertainty around confirmations, withdrawals, replay exposure, and which chain carries the BTC ticker—even if the dominant chain continues operating almost normally.

Key Indicators to Watch

• Signaling through block 961,631，currently expected around August, 2026.
• Major mining-pool and economic-node commitments.
• Chain growth and hashpower after block 961,632.
• Wallet, custodian, and exchange contingency notices.
• Whether BIP-110 implementations add replay protection or change their activation plan.

Conclusion

BIP-110 is less a referendum on Ordinals than a test of Bitcoin governance. Its supporters want consensus to defend Bitcoin’s monetary focus; its critics believe neutrality is protected by refusing contested consensus changes.

Current signaling shows no miner coordination close to the activation threshold. Block 961,632 will reveal whether the disagreement ends as a debate or becomes an operational fork.

Disclaimer

This article is for informational purposes only and does not constitute investment advice. Cryptocurrency markets are volatile, and readers should conduct their own research before making financial decisions.