Bitcoin sees BIP-110 debate after 66kB image transaction

BIP-110 targets such embeds; opponents say workarounds remain

A Slovak Bitcoin developer, Martin Habovštiak, embedded a 66-kilobyte image in a single Bitcoin transaction, spotlighting the debate over BIP-110 and its proposed limits on arbitrary data in Bitcoin transactions, including a tighter OP_RETURN limit. The demonstration revived long-running questions about whether consensus rules should try to exclude non-financial data or whether policy-layer tools and fees suffice.

According to The Block, Luke Dashjr disputed claims that the image was stored as a single contiguous blob and argued that BIP-110’s restrictions on OP_RETURN size, data pushes, and certain script field usages would still invalidate the technique. The same outlet also noted that a BIP-110-compliant variant of the experiment became larger due to required chunking, which critics say underscores that workarounds remain even when specific paths are filtered.

How the 66 kB image was embedded in one transaction

The transaction bundled a 66 kB TIFF payload without relying on OP_RETURN outputs or Taproot-style inscription conventions, showing that non-payment content can be placed on-chain within a single transaction. The approach highlights how data can be reconstructed from fields inside a transaction even if it is not exposed via commonly filtered channels.

Whether the payload was contiguous is contested. Proponents of BIP-110 emphasize that the proof-of-concept did not use the very paths they aim to restrict, while others note that, from a retrieval standpoint, the image can still be assembled from the transaction’s components. The distinction matters because BIP-110 focuses on constraining certain data pushes and script usages rather than the mere possibility of assembling data across parts.

In practice, narrowing one set of script paths or push sizes can shift arbitrary data to others. This is why many engineers separate consensus-rule edits (like BIP-110) from policy-layer measures such as relay and mempool filters and fee-based incentives, which can influence behavior without changing what the protocol treats as valid.

Governance risks: activation threshold, neutrality, user impact

BIP-110’s activation and governance design have drawn scrutiny from some long-time contributors. As reported by Cointeeth, Jameson Lopp criticized the proposal’s 55% miner threshold as too low and warned that poorly scoped constraints could risk freezing user funds if they collide with existing transaction patterns or wallet behaviors.

Opponents also frame the issue as one of neutrality and precedent, arguing that the protocol should remain agnostic to content types even if some uses are unpopular. “BIP-110 represents ‘permissionless censorship’ and risks undermining Bitcoin’s neutrality,” said Adam Back, CEO at Blockstream.

For node operators, miners, and wallet developers, the trade-off is between protocol-level exclusions and relying on fees and relay policies to discourage non-transactional payloads. At the time of this writing, Bitcoin (BTC) traded around $70,125 with neutral momentum (RSI near 51) and medium volatility near 3%, a backdrop that may shape whether policy and pricing dynamics, rather than new consensus rules, ultimately curb data-heavy activity.