Bitcoin Developer Uploads 66KB Image to Challenge BIP-110 Anti-Spam Proposal

A Bitcoin developer has ignited fresh debate over blockchain data restrictions by successfully inscribing a 66-kilobyte image directly onto the Bitcoin blockchain in a single, continuous transaction-a technical demonstration designed to challenge the proposed BIP-110 anti-spam protocol.

Developer Targets BIP-110 Restrictions

Martin Habovstiak, a Slovak developer, created the transaction as a direct response to supporters of BIP-110 and Bitcoin Knots, encoding an image depicting Luke Dashjr-a prominent BIP-110 advocate and CTO of Ocean mining pool-in tears. The move represents more than symbolic protest; it's a technical argument against what Habovstiak views as ineffective data restrictions.

BIP-110, originally introduced as BIP-444 in October 2025, proposes a one-year soft fork implementing seven new transaction validity criteria. The proposal would enforce an 83-byte cap on OP_RETURN, restrict individual data pushes to 256 bytes, and ban certain opcodes-all aimed at limiting non-payment-related data from cluttering the blockchain.

Technical Achievement Bypasses Intended Restrictions

What makes Habovstiak's demonstration particularly noteworthy is how it circumvents BIP-110's intended safeguards. According to the developer's statement on X, he created "a contiguous image file that can be misinterpreted by the BIP-110 Bitcoin fork as an entire transaction and contiguously stored in the BIP-110-compliant chain."

The technical community has largely expressed admiration for the transaction's construction. Notably, Habovstiak's approach avoided OP_RETURN opcodes, bypassed Taproot in favor of SegWit v0, and excluded OP_IF statements-the very elements BIP-110 primarily targets for restriction. This technical feat suggests that determined developers could potentially work around the proposed limitations.

Habovstiak defended his timing in a follow-up post, explaining that mainnet validation provides far more compelling proof than earlier theoretical demonstrations when BIP-110 first emerged.

Controversy Over Data Contiguity

Not everyone accepts Habovstiak's claims at face value. Critics on X have challenged whether the transaction truly qualifies as "contiguous" at the protocol level. Dashjr himself responded, asserting the transaction wasn't genuinely contiguous. Habovstiak countered that critics were applying selective definitions to undermine his demonstration.

Paradoxical Data Increase Claims

Perhaps most significantly, Habovstiak claims to have created an alternative version of his transaction that fully complies with BIP-110 constraints-but that this compliant version was substantially larger than the original. If accurate, this finding suggests the anti-spam proposal could paradoxically increase total data stored on Bitcoin's blockchain rather than reduce it.

Ongoing Tensions Between Bitcoin Core and Knots

The demonstration occurs amid persistent tensions between Bitcoin Core and Bitcoin Knots communities over appropriate blockchain data usage. Since 2023, Dashjr has consistently characterized arbitrary Bitcoin inscriptions as spam, arguing they create potential liability issues for node operators and distract from Bitcoin's core monetary function.

Habovstiak positions himself not as a spam advocate but as a defender of technical accuracy. "There's something I hate much more than spam: Untruths," he stated, criticizing what he perceives as persistent inaccuracies from Knots supporters despite his previous technical demonstrations.

To prevent misuse, Habovstiak deliberately kept his code private, framing the exercise as a one-time proof-of-concept rather than a template for NFT-style blockchain storage.

Current Adoption Metrics

According to data from The Bitcoin Portal, approximately 8.8% of nodes currently support BIP-110. Meanwhile, the Bitcoin Knots node count has experienced dramatic growth, increasing tenfold from levels seen at the beginning of last year, indicating growing support for stricter data policies within a segment of the Bitcoin community.

Coinasity's Take

Habovstiak's technical demonstration highlights a fundamental challenge in blockchain governance: technical restrictions often create new workarounds rather than solving underlying issues. If BIP-110 compliant transactions genuinely result in larger data sizes, the proposal could backfire spectacularly. This incident underscores the complexity of balancing Bitcoin's open architecture with concerns about blockchain bloat-a debate unlikely to resolve quickly given the philosophical divide between preserving Bitcoin's monetary purity and maintaining its permissionless nature. The tenfold increase in Bitcoin Knots nodes suggests this debate will intensify rather than fade.