When a single 66kB transaction is recorded on the Bitcoin blockchain, it carries more than just an image—it serves as a technical challenge to a proposed protocol. By late February 2026, the debate over what data the Bitcoin network should store had shifted from ideological arguments to direct engagement at the code level. Slovak developer Martin Habovštiak, through a clever proof of concept, embedded a TIFF image file into the Bitcoin blockchain as a single, continuous transaction. This act directly tested the regulatory boundaries advocated by supporters of the BIP-110 proposal, particularly those aligned with Bitcoin Knots. With the Bitcoin price at $66,311 on March 2, 2026, the ongoing technical tug-of-war between spam prevention and censorship resistance may be reshaping the foundational logic of the crypto ecosystem.
Event Overview: A Clean Data Embedding Experiment
On February 27, 2026, Rust Bitcoin library maintainer Martin Habovštiak carried out a technical demonstration that many in the community viewed as provocative. He permanently inscribed a 66kB TIFF image onto the blockchain through a single Bitcoin transaction.
What set this transaction apart was not its content, but its method of execution. Habovštiak made it clear that the transaction did not use any of the main data-carrying instructions targeted by the BIP-110 proposal:
- No use of OP_RETURN: This opcode is commonly used to store arbitrary data in transactions and is a primary focus of BIP-110, which proposes to limit it to 83 bytes.
- No reliance on Taproot: The transaction used SegWit v0, not Taproot script paths.
- No inclusion of OP_IF: This avoided the complexities of conditional statements that could enable sophisticated data embedding.
By circumventing these restrictions, Habovštiak demonstrated that even without triggering the instruction set that BIP-110 aims to limit, it is still possible to write relatively large data (66kB) as a continuous data stream onto the blockchain. This transaction has been publicly verified on-chain, and its hexadecimal data can be directly decoded and viewed using standard image software.
From BIP-444 to BIP-110: The Filtering Debate
This experiment is not an isolated incident but rather a continuation of the Bitcoin community’s long-standing debate over data filtering. To fully grasp the impact of this event, it’s helpful to review key milestones from the past year:
The Spark: Bitcoin Core v30 Lifts Restrictions (Mid-2025)
Bitcoin’s primary client, Bitcoin Core, removed the long-standing 83-byte limit on OP_RETURN outputs in version 30. Purists saw this move as enabling non-financial data, believing it marked a departure from Bitcoin’s core functions as a payment and store-of-value network.
The Pushback: BIP-444 and BIP-110 Proposed (October–December 2025)
Supporters led by Bitcoin Knots maintainer Luke Dashjr began to push back. An anonymous developer, Dathon Ohm, first proposed BIP-444 to temporarily restrict arbitrary data. Soon after, the stricter BIP-110 emerged as a formal proposal, suggesting a one-year temporary soft fork with measures such as limiting OP_RETURN to 83 bytes and capping single data pushes at 256 bytes.
Activation Mechanism Controversy: 55% Threshold Sparks Debate (Late 2025–Early 2026)
BIP-110’s proposed activation threshold of just 55% hash power support triggered even greater controversy than the technical details themselves. Detractors like Blockstream CEO Adam Back called it "mob rule," arguing that such a low bar could undermine Bitcoin’s immutability. During this period, the share of nodes supporting BIP-110 slowly rose from about 2.38% in January to around 8.8% recently.
Technical Refutation: Habovštiak’s Proof of Concept (Late February 2026)
Amid heated ideological debates, Habovštiak’s experiment brought the discussion back to technical fundamentals. His demonstration was not just about data embedding—it was a direct response to BIP-110 supporters’ repeated claims about the necessity of technical restrictions.
Technical Breakdown: How the Restrictions Were Bypassed
From a data structure perspective, Habovštiak’s transaction is a classic example of technical ingenuity.
Transaction Construction Analysis
The core breakthrough in this transaction lies in leveraging the flexibility of Bitcoin’s scripting system rather than relying on specific data storage opcodes. Habovštiak split the 66kB TIFF image data and embedded it within seemingly standard transaction input scripts, exploiting how SegWit v0 handles witness data. Structurally, the transaction resembles a complex fund transfer rather than a simple data storage operation.
Comparison with BIP-110 Restrictions
| Technical Metric | BIP-110 Proposed Limit | Habovštiak’s Implementation | Comparative Analysis |
|---|---|---|---|
| OP_RETURN Usage | Limited to 83 bytes | Not used | Avoided the most direct regulatory path |
| Taproot Dependency | May restrict specific versions | Used SegWit v0 | Demonstrated legacy script can also carry data |
| Data Continuity | Aims to prevent nonstandard storage | Achieved continuous data stream | Shows that limiting certain opcodes can’t eliminate data embedding |
| Total Data Volume | Seeks to sharply reduce on-chain data | Single transaction of 66kB | Relatively small, but sets a precedent |
Habovštiak went a step further by creating a BIP-110-compliant image transaction and testing it in a regtest environment. He claimed that the compliant version was even larger than the original, suggesting that BIP-110’s restrictions could actually increase the blockchain’s total storage requirements due to data restructuring. This directly challenges BIP-110’s core goal of reducing on-chain data.
The Factions Behind the Technical Experiment
This event drew widespread attention because it brought the arguments of two long-opposed factions in the community into direct, concrete conflict.
Arguments from the BIP-110 Supporters
- Core Position: Luke Dashjr and others insist that non-financial data abuse constitutes spam, increasing hardware and legal risks for node operators and ultimately undermining Bitcoin’s decentralization.
- Reaction to the Experiment: After the event, Dashjr disputed Habovštiak’s demonstration on X, claiming the transaction was not truly continuous and attempting to refute the experiment’s technical challenge. This shows supporters are keen to defend the technical basis of their position.
Arguments from the BIP-110 Opponents
- Core Position: Detractors such as Adam Back and Wang Chun (Shenyu) argue that Bitcoin’s immutability is paramount. Any rule change justified as anti-spam, especially with a low threshold (like 55%), could open a Pandora’s box of governance risks, potentially leading to address-level censorship in the future.
- Reaction to the Experiment: Opponents see this experiment as a refutation of both the technical feasibility and necessity of BIP-110. Habovštiak himself stated that his motivation was to oppose what he called "lies" from the Knots camp.
Drawing the Line: Facts, Opinions, and Speculation
It’s important to clearly distinguish between different types of information when analyzing this event.
- Facts: A developer successfully executed a transaction embedding 66kB of TIFF image data on the Bitcoin mainnet. The transaction did not use OP_RETURN, Taproot, or OP_IF, and can be validated by any full node.
- Opinions: Whether this constitutes a circumvention of BIP-110 depends on how "circumvention" is defined. Supporters may see it as exposing new loopholes, reinforcing the need for restrictions; opponents may see it as proof that restrictions are futile.
- Speculation: As for whether this experiment will trigger a new wave of NFT-like data inscriptions, Habovštiak has stated he will not release the code and does not wish to encourage such activity. There is no direct evidence to suggest this marks the start of a new wave of attacks; it is more of a symbolic protest.
Ripple Effects for Nodes, Miners, and Developers
Though a one-off experiment, this event has potential implications for various participants in the crypto ecosystem.
- Node Operators: For those running Bitcoin Core nodes, this transaction is no different from any other and poses no extra burden. However, for Bitcoin Knots nodes attempting to preemptively enforce BIP-110 rules, this compliant transaction raises a philosophical question: if the rules can’t restrict the targeted behavior, are they effective at all?
- Miners and the Security Budget: The event reignited debate over the use of block space. BIP-110 supporters argue that data inscriptions benefit from SegWit discounts, creating unfair competition in the fee market. Opponents (including miners) counter that, with Bitcoin’s block rewards steadily halving (current supply around 19.99M), all fee revenue is valuable and shouldn’t be cut off. Data shows that inscription-type transactions have contributed nearly $10 million in fees in a single day. Miners’ attitudes toward such transactions are becoming more nuanced.
- Developer Community: The BIP-110 activation client has previously been reported to contain numerous technical bugs, failing even the tests designed by its own proponents. In contrast, Habovštiak’s elegant technical demonstration stands in stark contrast to the rough edges of the BIP-110 client, potentially eroding community confidence in the proposal’s technical maturity.
Scenario Analysis: Possible Future Paths
Based on current facts, several future scenarios can be projected.
| Scenario | Trigger Condition | Network Impact |
|---|---|---|
| Scenario 1: Technical Patch | BIP-110 supporters add Habovštiak’s embedding method to a new list of restrictions, proposing an even stricter BIP-xxx. | Kicks off a cat-and-mouse cycle; rules become increasingly complex but may never fully prevent data embedding. |
| Scenario 2: Consensus Cools | Given BIP-110 client bugs and the recent bypass, wavering node operators drop support, causing adoption to stall or decline. | BIP-110 is effectively shelved; debate returns to the ideological level; the mainnet continues as is. |
| Scenario 3: Fork Risk | Despite insufficient support, core advocates attempt to activate via the low 55% threshold, triggering strong community backlash. | Could lead to severe consensus splits, resulting in Bitcoin chains with different rules and damaging brand value. |
| Scenario 4: Legal Scrutiny | Regulators notice that on-chain content may include infringing or illegal data, imposing compliance demands on node operators. | Regardless of BIP-110’s outcome, legal risk remains a long-term challenge for all data storage transactions. |
Conclusion
A single 66kB image has exposed deep-rooted dilemmas in Bitcoin’s evolution: In a world of code that strives for absolute censorship resistance, how do we define what is "spam"? Who gets to decide? Habovštiak’s experiment did not attack the Bitcoin network—it targeted the logic behind a proposal seeking to change the network’s default rules. It serves as a reminder that every step in Bitcoin’s evolution requires not just ideological consensus, but also robust technical implementation. Whatever the fate of BIP-110, this debate over the boundaries of data will become another memorable chapter in the history of Bitcoin governance.
