Inscriptions

Bitcoin’s core developer community faces an unprecedented governance crisis as a proposed rule change targeting ordinals and inscriptions has triggered competing technical fixes and explicit fork warnings from major industry figures. The dispute exposes fundamental disagreement over Bitcoin’s purpose, whether it should remain a payment-only system or permit arbitrary data storage, with implications for how protocol decisions get made across institutional blockchain infrastructure.

• BIP-110 proposal would limit transaction data to 256 bytes per unit for one year, designed to block inscription-based file storage on Bitcoin
• Miner signaling stands at 0.73% support as of June 30, far below the 55% threshold normally required for soft fork activation
• Ordinals developers released technical workaround on July 2 that would preserve inscriptions even if BIP-110 activates, triggering immediate counter-response

• 0.73% Miner signaling support for BIP-110 versus 55% standard activation threshold
• 256 bytes Maximum data size per transaction under BIP-110 versus current inscription capacity
• Early August Planned enforcement date when BIP-110 nodes begin rejecting non-compliant blocks

A technical proposal to restrict data storage on Bitcoin has fractured the network’s developer community and raised the prospect of a contentious protocol split, forcing institutional investors to confront fundamental questions about how Bitcoin governance actually works in practice.

BIP-110, authored under the pseudonym Dathon Ohm and championed by Bitcoin Knots maintainer Luke Dashjr, would compress the data capacity available for inscriptions, a technology that lets users embed images, text and other files directly into the blockchain.

The rule is designed to activate automatically around early August regardless of miner support levels, a governance mechanism that contradicts conventional soft fork practice and has already drawn public warnings from Blockstream CEO Adam Back and MicroStrategy executive Michael Saylor about fork risk and protocol instability.

The proposal sits at the intersection of two competing visions for Bitcoin’s future. Dashjr and BIP-110 supporters frame inscription data as spam that degrades the blockchain’s primary function as a payment system, arguing that Bitcoin’s scarcity and integrity depend on rejecting non-monetary uses.

Ordinals developers and their supporters counter that Bitcoin’s permissionless design inherently permits any data storage users are willing to pay for in transaction fees. This disagreement echoes earlier cryptocurrency debates about block size and protocol scope, but it now plays out within Bitcoin’s core development process itself rather than between competing factions.

Miner signaling remains below 1% despite six months of voting, undercutting democratic legitimacy of BIP-110

Mining support for BIP-110 has stalled far short of normal activation thresholds. As of June 30, only three blocks out of 2,016 in the two-week sample window carried the BIP-110 flag, representing just 0.73% of the hashrate. Bitcoin soft forks typically require 95% miner signaling to activate, though the actual threshold has varied across protocol upgrades.

The strongest two-week period since voting opened in December 2025 reached only 0.79% in mid-June, suggesting that mining operations, which generate transaction fees and operate under commercial pressure, view the proposal as either unnecessary or economically harmful.

Miners represent the economic actors most sensitive to changes affecting transaction throughput and fee structure. Their consistent resistance to BIP-110 signals that the proposal lacks the practical support required for normal soft fork activation. This creates a governance problem: the Bitcoin community has never forced through a contentious rule change against mining opposition at this scale.

Bitcoin’s historical protocol upgrades occurred either with broad consensus or were abandoned outright when community backing proved insufficient.

The voting gap matters because it establishes that BIP-110 lacks the distributed legitimacy Bitcoin governance typically requires.

Dashjr plans enforcement from early August regardless of miner participation or network consensus

BIP-110’s enforcement model breaks sharply from standard Bitcoin soft fork practice.

Rather than waiting for 95% miner signaling, the proposal includes code that will activate on a predetermined schedule around early August, with Bitcoin Knots nodes, the software distribution Dashjr maintains and that BIP-110 supporters predominantly run, automatically programmed to reject any blocks that do not carry the compliance flag.

This unilateral enforcement mechanism transforms BIP-110 from a proposal seeking consensus into an ultimatum that forces a binary choice on the network: adopt the rule or split off.

Blockstream’s Adam Back, one of Bitcoin’s most prominent institutional figures, has publicly warned that this approach risks triggering a fork in which the Bitcoin network splits into two competing versions, one running BIP-110-compliant nodes, the other continuing under the original rules.

A fork of that magnitude would fragment liquidity, split exchange order books, and create confusion about which chain maintains Bitcoin’s institutional credibility and price discovery. MicroStrategy’s Michael Saylor, whose company holds Bitcoin as a corporate treasury asset, called the plan a self-inflicted risk that undermines confidence in Bitcoin’s stability.

Dashjr has framed the stakes as existential. In a public statement on Thursday, he wrote: “If BIP110 fails, Bitcoin fails with it.

I am not interested in any CBDC, much less an unregulated CBDC pretending to be decentralised.” He equates inscriptions with government-issued digital currencies, suggesting that a Bitcoin unable to reject arbitrary data loses the property that distinguishes it from traditional financial systems.

This rhetorical escalation underscores how deeply the dispute cuts into competing ideological views of what Bitcoin should be.

Ordinals developers deploy technical workaround within hours, setting up recursive enforcement cycle

On July 2, just days after BIP-110’s enforcement timeline became clear, Ordinals developer lifofifoX published a technical fix that would preserve inscription functionality even after BIP-110 activation. Rather than storing files in the large blocks that BIP-110 targets, the workaround fragments data into smaller, compliant pieces that remain within the 256-byte size limit the rule imposes.

Casey Rodarmor, creator of the Ordinals protocol, approved the fix the same day, posting on GitHub: “Looks good to me! Let’s wait until BIP-110 activates to merge this.”

The response demonstrates that technical barriers alone cannot enforce BIP-110’s intent. Inscriptions can be restructured faster than Bitcoin’s governance cycle can decide rules. This asymmetry favors the ordinals side: defenders can iterate on workarounds indefinitely, while BIP-110 supporters must achieve and maintain network-wide consensus to block each new approach.

Bitcoin Knots maintainers have already filed counter-updates designed to recognize and reject the new fragmented inscription format, but the underlying pattern is now clear: the two sides have entered a technical escalation cycle with no obvious resolution point.

Each workaround will provoke a counter-proposal, and no amount of bandwidth restriction can prevent users from encoding data if they control the software.

Institutional investors must reckon with Bitcoin governance failure as network lacks decision-making mechanism

This dispute exposes a critical structural vulnerability in Bitcoin’s governance model that institutional investors have largely ignored. Bitcoin lacks a formal mechanism for resolving disagreements when technical factions hold incompatible views and neither commands overwhelming consensus.

The protocol has defaulted to a rough social consensus enforced by mining power, but BIP-110 demonstrates that this approach breaks down when a minority faction possesses both development authority and ideological conviction to force through changes unilaterally.

For institutional asset managers and custodians, the implications are severe. A fork splits the asset, divides liquidity across competing chains, and creates accounting ambiguity about which version constitutes “Bitcoin” for portfolio purposes. Insurance products, custody protocols, and settlement systems all depend on Bitcoin’s status as a singular, unified asset.

A governance crisis that produces two competing Bitcoin chains would require institutional infrastructures to choose sides, fragmenting the network’s value proposition and slowing adoption among traditional financial institutions who cannot operate across competing versions.

The ordinals side possesses a technical advantage: any data encoding scheme that fits within protocol limits can be deployed without forcing a network-wide upgrade. BIP-110 supporters rely on centralized distribution of compliant software, specifically Bitcoin Knots, but they cannot prevent users