Challenge BIP-110: How will 66kB image transactions impact Bitcoin's on-chain rules and consensus mechanism?

When a transaction only 66kB in size is written into a Bitcoin block, it brings not just an image but also a technical challenge to a proposed protocol. By the end of February 2026, a debate about what data the Bitcoin network should carry has evolved from a conceptual discussion into a direct code-level dialogue. Slovak developer Martin Habovštiak demonstrated this with a clever proof of concept, embedding a TIFF image file as a continuous transaction into the Bitcoin blockchain. This act directly touches on the regulatory boundaries supported by Bitcoin Knots and the BIP-110 proposal advocated by its supporters. At a Bitcoin price of $66,311 on March 2, 2026, this technical game of spam and censorship resistance may be reshaping the fundamental logic of the crypto ecosystem.

Event Overview: A Clean Write Experiment

On February 27, 2026, Rust Bitcoin library maintainer Martin Habovštiak completed a demonstration considered provocative by the community. He permanently inscribed a 66kB TIFF image into the blockchain via a single Bitcoin transaction.

The uniqueness of this transaction lies not in its content but in its implementation. Habovštiak explicitly stated that the transaction did not use the data-carrying instructions primarily targeted by the BIP-110 proposal:

• No OP_RETURN: This opcode is typically used to store arbitrary data in a transaction and is a key restriction targeted by BIP-110, which proposes limiting it to 83 bytes.
• No Taproot reliance: The transaction uses SegWit v0, not Taproot script paths.
• No OP_IF: Avoids conditional statements that could enable complex data embedding.

Through this compliant bypass, Habovštiak proved that even without triggering the instruction set BIP-110 aims to restrict, it is still possible to write relatively large data (66kB) as a continuous data stream into the blockchain. The transaction has been publicly verified on-chain, and its hex data can be directly decoded with standard image software.

From BIP-444 to BIP-110 Filtering Controversy

This experiment is not isolated but a continuation of the long-standing debate within the Bitcoin community about data filtering. To understand its impact, we need to review key milestones over the past year:

Trigger: Bitcoin Core v30 Lifts Restrictions (Mid-2025)

Bitcoin’s most mainstream client, Bitcoin Core, removed the long-standing 83-byte limit on OP_RETURN outputs in version v30. This move was seen by purists as an endorsement of non-financial data, suggesting the network was drifting away from pure payment and store-of-value functions.

Counterattack Begins: Introduction of BIP-444 and BIP-110 (Oct–Dec 2025)

Supporters led by Bitcoin Knots maintainer Luke Dashjr started countering. Anonymous developer Dathon Ohm proposed BIP-444, aiming to temporarily restrict arbitrary data. Later, a stricter BIP-110 was introduced as a formal proposal, proposing a one-year soft fork with restrictions such as limiting OP_RETURN to 83 bytes and capping single data pushes at 256 bytes.

Activation Mechanism Controversy: 55% Threshold Sparks Community Debate (Late 2025 – Early 2026)

BIP-110’s support threshold of 55% hashpower support triggered more controversy than the technical proposal itself. Critics like Blockstream CEO Adam Back criticized it as mob rule, fearing that a low threshold could undermine Bitcoin’s immutability. Support for BIP-110 among nodes gradually increased from about 2.38% in January to roughly 8.8% recently.

Technical Disproof: Habovštiak’s Proof of Concept (Late Feb 2026)

Amid ideological debates, Habovštiak’s experiment refocuses on the technical level. His demonstration is not just data writing but a direct response to the repeated emphasis by BIP-110 supporters on the necessity of technical restrictions.

Technical Anatomy of Bypassing Restrictions

From a data structure perspective, Habovštiak’s operation has clear technical significance.

Transaction Construction Analysis

The core breakthrough is leveraging Bitcoin script system flexibility rather than relying on specific data storage opcodes. Habovštiak split the 66kB TIFF image data and embedded it within seemingly normal transaction input scripts, exploiting SegWit v0’s witness data handling. This makes the transaction structurally resemble a complex fund transfer rather than simple data storage.

Comparison with BIP-110 Restrictions

Habovštiak further created a BIP-110-compliant image transaction version and tested it in regtest. He claims the compliant version is even larger than the original, implying BIP-110 restrictions could increase total blockchain storage due to data restructuring. This directly challenges BIP-110’s goal of reducing data.

Camps and Clashes Behind the Technical Experiment

This event has garnered widespread attention because it concretizes the long-standing ideological divide within the community.

Pro-BIP-110 Camp Arguments

• Core claim: Figures like Luke Dashjr argue that misuse of non-financial data constitutes spam, increasing node hardware burdens and legal risks, ultimately harming Bitcoin’s decentralization.
• Reaction to the experiment: After the event, Dashjr publicly questioned Habovštiak’s demonstration on X, claiming the transaction was not truly continuous and attempting to deny its challenge from a technical standpoint. This indicates supporters aim to defend their technical foundation.

Anti-BIP-110 Camp Arguments

• Core claim: Figures like Adam Back and Wang Chun (Shen Yu) believe Bitcoin’s immutability is paramount. Any rule change justified as anti-spam, especially with low thresholds like 55%, risks opening governance Pandora’s box, potentially leading to censorship of certain addresses.
• Reaction to the experiment: Opponents see this as a disproof of BIP-110’s technical feasibility and necessity. Habovštiak explicitly states his motivation is to oppose what he perceives as lies from the Knots camp.

Boundaries Between Facts, Opinions, and Speculation

When analyzing this event, it’s crucial to distinguish different levels of information:

• Facts: A developer indeed created a transaction embedding a 66kB TIFF image into the mainnet. The transaction did not use OP_RETURN, Taproot, or OP_IF. It can be verified by any full node.
• Opinions: Whether this counts as bypassing BIP-110 depends on the definition of bypass. Supporters may see it as exposing new loopholes, reinforcing the need for restrictions. Opponents see it as proof of restrictions’ futility.
• Speculation: Whether this experiment will trigger a new wave of NFT-like data writing is uncertain. Habovštiak has stated he will not publish code and does not want to trigger such activities. Thus, viewing it as the start of a new attack wave lacks direct evidence; it’s more symbolic protest.

Ripple Effects on Nodes, Miners, and Developer Ecosystem

Although a one-time experiment, it has potential impacts on various participants:

• Node operators: For nodes running Bitcoin Core, this transaction is indistinguishable from normal transactions and causes no extra burden. For nodes running Bitcoin Knots or those attempting to enforce BIP-110 rules early, this compliant transaction raises a philosophical question: if rules cannot restrict their target behavior, are the rules still effective?
• Miners and security budget: The event rekindles discussions on block space usage. Supporters of BIP-110 argue that data writes benefit from SegWit discounts, creating unfair fee market competition. Opponents (including miners) argue that with block rewards halving and current issuance around 19.99 million BTC, any fee income should not be actively cut. Data embedding transactions have previously contributed nearly $10 million in fees in a single day. Miner attitudes toward such transactions are becoming more complex.
• Developer community: BIP-110 client implementations have been reported to contain numerous bugs, with some failing even basic tests. Habovštiak’s elegant demonstration contrasts sharply with the rough state of BIP-110 client code, potentially undermining confidence in the proposal’s technical maturity.

Evolutionary Scenarios

Based on current facts, several future paths can be envisioned:

Conclusion

A 66kB image reflects deep dilemmas in Bitcoin’s development: in the pursuit of censorship resistance, how do we define what is garbage? Who gets to decide? Habovštiak’s experiment does not attack the Bitcoin network itself but challenges the logic of a proposal seeking to alter default rules. It reminds us that every evolution of Bitcoin requires not only ideological consensus but also technically robust implementation. Regardless of BIP-110’s final outcome, this debate over data boundaries will be another memorable chapter in Bitcoin governance history.