A Bitcoin developer embedded a 66-kilobyte picture inside a single transaction with out utilizing OP_RETURN or Taproot.
The transaction adopted consensus guidelines. Anybody can confirm the bytes utilizing customary node software program. Martin Habovštiak did not do that to make artwork, however to show that closing one knowledge doorway does not take away the aptitude, it simply modifications the place bytes disguise.
The demonstration lands amid Bitcoin’s most contentious governance battle in years. One faction desires stricter filters to maintain “spam” off the blockchain.
One other argues that harsh restrictions push individuals into worse behaviors and benefit giant miners. Habovštiak’s experiment gives proof for the second place: filtering redirects somewhat than stopping them.
What really occurred
Habovštiak’s write-up features a transaction ID and verification technique.
Customers can run bitcoin-cli getrawtransaction, then xxd -r -p to reconstruct the file. The development avoids the 2 pathways most cited in knowledge storage debates: the OP_RETURN area that Bitcoin Core lately relaxed, and Taproot’s witness construction that enabled many inscriptions.
Bitcoin transactions are bytes. Nodes implement that bytes observe structural guidelines, equivalent to legitimate signatures, correct formatting, and legit spending circumstances.
They do not implement that bytes “imply cash solely.” If somebody constructs legitimate transaction bytes that additionally type a legitimate picture file, the community shops and relays them.
Bitcoin can discourage sure knowledge patterns via software program defaults. It can not stop them with out instantly confronting miners’ financial incentives.
The excellence no person explains
Bitcoin operates with two layers of guidelines. Consensus guidelines decide what blocks are legitimate. Coverage guidelines decide what transactions particular person nodes relay and what miners usually settle for into mempools by default.
Rule layerWhat it controls (plain English)What it could’t guaranteeWhy it issues hereConsensus rulesWhat makes blocks/tx validCan’t implement “money-only which means”If it’s legitimate, it may be minedPolicy / standardnessWhat nodes relay / mempools settle for by defaultCan be bypassedFilters add friction, not certaintyMiners’ inclusionWhat will get into blocksIncentives override preferencesFees can “purchase” inclusionDirect submission pipelinesBypasses relay networkConcentrates entry“Pay-to-play” danger (Slipstream-type routes)
Coverage can gradual conduct, elevate friction, and impose prices. It can not assure prevention if a transaction stays consensus-valid and pays ample charges.
Miners can embrace any consensus-valid transaction, particularly when it reaches them via paths that bypass common node relay.
OP_RETURN dimension limits have all the time been coverage selections, not consensus partitions. Bitcoin Core has traditionally handled these as standardness nudges, with builders arguing that harsh limits push individuals into worse encodings, equivalent to stuffing knowledge into outputs that seem spendable, bloating the UTXO set that each node should keep.
Habovštiak’s demonstration makes this summary argument concrete. Cap one technique, and engineering effort flows towards one other.
The pay-to-play downside
Even when many nodes refuse to relay “non-standard” transactions, financial incentives create workarounds. Mining swimming pools settle for transactions instantly, bypassing the relay community. Providers explicitly launched for this exist already.
MARA’s Slipstream operates as a direct submission pipeline for “giant or non-standard” transactions that nodes usually exclude from mempools even after they observe consensus guidelines. The service routes round defaults somewhat than breaking guidelines.
This creates a centralization vector that stricter filters could amplify. When common nodes will not relay sure transaction varieties, solely miners and specialised companies can reliably land them in blocks.
At 10 satoshis per digital byte, one megabyte of blockspace prices roughly 0.1 BTC. At 50 satoshis per byte, roughly 0.5 BTC. The “ban” query turns into “what’s going to individuals pay?”
BIP-110 and the governance battlefield
The demonstration arrives as Bitcoin debates BIP-110, a proposal to briefly prohibit data-carrying transaction fields on the consensus degree for about one 12 months.
Discipline / areaWhat BIP-110 proposes (plain English)What it’s attempting to preventMain tradeoff / riskNew output scriptsNew scriptPubKeys > 34 bytes invalid (besides OP_RETURN allowance)Knowledge stuffed into outputsRisk of pushing knowledge elsewhereOP_RETURN exceptionOP_RETURN allowed as much as 83 bytesSmall provable notesCritics: nonetheless doesn’t “ban knowledge”Payload limitsCaps sure pushed knowledge components (basic 256-byte ceiling with exceptions)Giant embedded blobsWorkarounds could emergeWitness stack elementsLimits witness aspect sizes (basic 256 bytes)Inscription-style payloadsMight redirect to worse encodingsDuration framingTemporary (~1 12 months)Tactical slowdownImplies “no clear everlasting repair”Second-order effectIf knowledge shifts into UTXO-like outputsAvoid long-term node burdenBackfire danger: UTXO bloat will increase
The draft would make new output scripts exceeding 34 bytes invalid, apart from OP_RETURN outputs, which will be as much as 83 bytes. It additionally proposes limits on payload sizes and witness stack components, typically capping them at 256 bytes with slender exceptions.
Supporters body BIP-110 as a measure that protects node operators from runaway storage prices.
Critics warn about negative effects and implementation dangers. The proposal represents an escalation from policy-level filtering to consensus-level restriction, a shift carrying governance implications past the fast technical query.
Habovštiak’s experiment feeds instantly into this debate. It demonstrates that even consensus restrictions face strain to adapt. He notes BIP-110 might invalidate his particular development, but additionally that he might produce alternate options utilizing completely different encodings.
The underlying dynamic persists: squeeze one sample, and incentives plus ingenuity push knowledge elsewhere.
The non permanent framing, one 12 months somewhat than everlasting, acknowledges this actuality implicitly. A everlasting change would require confronting tougher questions in regards to the sustainability of enforcement.
A brief measure admits the issue could lack a clear technical resolution, solely tactical administration with a restricted shelf life.
The worst-behavior downside
Proscribing in style knowledge pathways can backfire by pushing utilization towards encodings that impose larger community prices.
When builders create outputs that look spendable to hold arbitrary knowledge, they enhance the UTXO set, which is the database of unspent outputs each full node should keep in accessible storage.
UTXO progress represents a extra persistent burden than witness knowledge or OP_RETURN payloads, which will be pruned. An output that encodes a picture file stays within the UTXO set till somebody spends it, doubtlessly indefinitely.
The node value accumulates somewhat than ageing away.
This explains Bitcoin Core’s historic reluctance to impose harsh limits on OP_RETURN. The choice is not essentially higher. Filters that appear protecting can enhance long-term working prices for nodes, undermining the decentralization objective they intention to protect.
Three paths ahead
The enforcement economics counsel three situations.
The primary path maintains the established order: value it, do not ban it. Arbitrary knowledge persists, ruled primarily by price markets. When blockspace turns into scarce, data-heavy transactions are naturally priced out. The lever turns into financial somewhat than technical.
The second path tightens coverage filters whereas leaving consensus unchanged. Knowledge shifts towards harder-to-filter encodings and direct-to-miner submission. Centralization danger rises as a result of solely miners and specialised pipelines can reliably affirm these transactions.
The third path implements consensus restrictions, equivalent to these outlined in BIP-110. Fashionable patterns could briefly decline, however adaptation continues as new encodings emerge. Collateral harm will increase if limits push knowledge into outputs that bloat the UTXO set.
Governance danger escalates as contentious consensus modifications elevate coordination challenges and the potential for community splits.
What decides the end result
Three indicators sign which situation materializes.
First, miner conduct. Do mining swimming pools proceed accepting non-standard transactions via direct channels? Providers like Slipstream exist particularly for this, as their sustained operation reveals miner priorities.
Second, governance trajectory. Does BIP-110 collect significant adoption past debate? The proposal requires coordinated activation throughout a decentralized community, making political viability as essential as technical advantage.
Third, second-order results. Do restrictions push extra knowledge into encodings that enhance node burden? UTXO progress charges throughout coverage tightening durations would offer empirical proof.
The uncomfortable actuality
If you happen to oppose on-chain knowledge storage past monetary transactions, Habovštiak’s demonstration delivers an uncomfortable message: you most likely cannot ban it.
You possibly can value it via price markets. You possibly can discourage it via coverage defaults. You possibly can elevate friction via implementation complexity.
However full prevention requires both accepting financial constraints you can not management or implementing consensus restrictions that carry their very own dangers.
Bitcoin validates transaction construction, not which means. The protocol does not distinguish between “cash transactions” and “knowledge transactions” as a result of that distinction requires interpretation that the community can not carry out.
The true debate is not whether or not Bitcoin can technically stop arbitrary knowledge, because the demonstrated reply is “not simply, and maybe in no way.”
The controversy is which tradeoffs the community accepts: centralization towards miners who bypass filters, governance danger from contentious consensus modifications, or larger long-term prices from worse encoding selections.
Habovštiak’s picture proves the filters do not work as marketed. What comes subsequent is dependent upon whether or not Bitcoin’s customers and builders settle for that actuality or proceed pursuing technical options to what more and more seems to be an financial and governance downside.
