Bitcoin devs weigh BIP-110 as 66KB image bypasses rules

TLDR

• 66 KB TIFF embedded in one Bitcoin transaction challenges BIP-110 limits.
• Developer bypassed typical inscription paths BIP-110 targets to restrict data.
• BIP-110-compliant variant was larger, implying workarounds may inflate storage.

A Slovak Bitcoin developer, Martin Habovštiak, embedded a 66-kilobyte TIFF image directly in a single Bitcoin transaction, testing whether BIP-110’s targeted restrictions meaningfully curb arbitrary data on-chain. As reported by The Block (https://www.theblock.co/post/391667/developer-embeds-image-on-bitcoin-as-a-single-transaction-challenging-bip-110s-core-claims), the experiment avoided common inscription paths that BIP-110 aims to limit.

The report notes the transaction decodes into a standard TIFF and that a version designed to comply with BIP-110 was actually larger. That outcome suggests some workarounds could inflate data rather than reduce it.

Why it matters: effectiveness, ‘contiguous data,’ and governance trade-offs

At issue is whether BIP-110’s path-specific constraints, covering elements like OP_RETURN sizing and select script usage, can prevent non-financial “Bitcoin inscriptions” or whether determined users will route around them. The debate also hinges on what counts as “contiguous data,” i.e., bytes placed back-to-back within a transaction structure, a definition critics say is hard to police consistently.

A number of analysts argue that economic fees often govern behavior more reliably than rule-based bans on specific script paths. Based on analysis from Because Bitcoin (https://becausebitcoin.com/post/single-transaction-image-tests-bip-110-bitcoin-data-restrictions), the demonstration underscores how attempts to block categories of byte placement can shift, rather than stop, on-chain data storage.

Critics warn that tightening protocol rules could introduce neutrality and governance risks if not broadly supported by the ecosystem. “BIP-110 is an ‘attack’ on norms of consensus and could freeze funds,” said Adam Back, CEO of Blockstream, as reported by Cointelegraph (https://cointelegraph.com/news/adam-back-opposes-bip110-fixing-arbitrary-data-spam).

Institutional commentary has also highlighted soft-fork trade-offs, including update burdens for node operators and fragmentation risk if activation proceeds without wide consensus. According to MEXC News (https://www.mexc.com/news/838635), some observers worry about policy creep and potential legal exposure for hosting large arbitrary data.

At the time of this writing, market context shows Bitcoin (BTC) around $70,115 with medium volatility and a neutral RSI reading, indicating a steady backdrop as the technical debate unfolds.

What was done: single transaction, no OPRETURN/Taproot/OPIF

The demonstration placed a 66 KB image as contiguous data within a single transaction while deliberately avoiding OPRETURN, Taproot, and OPIF. That approach targets areas BIP-110 does not directly restrict, probing how far the proposal’s scope can reach in practice.

Notably, the developer also produced a purported BIP-110-compliant variant that ended up larger than the original, implying certain compliance paths may be less space-efficient. In effect, the test measures how rule-based constraints interact with fee incentives and whether path-specific limits can reduce, rather than re-route, arbitrary data on-chain.