Bitcoin dev encodes 66KB image on-chain to challenge BIP-110 limits
Bitcoin developer Martin Habovštiak encoded a 66KB image into a single on-chain Bitcoin transaction to challenge BIP-110, a proposed anti-spam soft-fork favored by Bitcoin Knots proponents (notably Luke Dashjr). BIP-110 (initially BIP-444) would restrict non-payment data by capping OP_RETURN to 83 bytes, limiting individual data pushes to 256 bytes and banning certain opcodes. Habovštiak’s inscription avoided OP_RETURN, used SegWit v0 (not Taproot) and contained no OP_IF statements, arguing the BIP’s targeted constraints can be bypassed. He says a BIP-110–compliant version of the same image would be larger overall, and therefore the proposal could paradoxically increase total on-chain data. The demonstration reignites the debate between Bitcoin Core and Bitcoin Knots over whether arbitrary data should be limited to reduce node operator liability and preserve Bitcoin’s payment focus. Current node support for BIP-110 is modest: The Bitcoin Portal reports 8.8% of nodes back BIP-110, while Bitcoin Knots node count has grown tenfold since early last year. Habovštiak kept his code private to avoid encouraging NFT-style use and framed the test as a one-time proof-of-concept.
Neutral
This technical demonstration is unlikely to move markets materially on price alone — it concerns protocol policy and node operator preferences rather than monetary supply or adoption metrics. Traders typically react to changes that directly affect liquidity, issuance, large-scale adoption, or regulatory clarity. The Habovštiak inscription does, however, increase short-term uncertainty around Bitcoin’s technical roadmap and could influence developer coordination and node software choices (Bitcoin Core vs Bitcoin Knots). If BIP-110 gains traction and is deployed, it might reduce certain kinds of on-chain activity (inscriptions/large arbitrary data), potentially lowering demand for low-fee inscription activity but raising debate-driven volatility. Historically, protocol governance disputes (e.g., SegWit activation, previous soft-fork debates) produced short-lived volatility around announcements and node-count metrics but did not change Bitcoin’s long-term bullish fundamentals. Therefore expect limited short-term trading noise around developer commentary and node-support statistics, but no durable directional price signal solely from this event. Traders should monitor: node adoption metrics (Knots vs Core), further technical analyses proving bypasses or vulnerabilities, and any client updates that could force reorgs or incompatible forks.