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 normal node software program. Martin Habovštiak did not do that to make artwork, however to show that closing one information doorway does not take away the aptitude, it simply modifications the place bytes disguise.
The demonstration lands amid Bitcoin’s most contentious governance combat in years. One faction needs 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 relatively than stopping them.
What truly occurred
Habovštiak’s write-up features a transaction ID and verification methodology.
Customers can run bitcoin-cli getrawtransaction, then xxd -r -p to reconstruct the file. The development avoids the 2 pathways most cited in information storage debates: the OP_RETURN discipline that Bitcoin Core lately relaxed, and Taproot’s witness construction that enabled many inscriptions.
Bitcoin transactions are bytes. Nodes implement that bytes comply with structural guidelines, similar to legitimate signatures, correct formatting, and legit spending situations.
They do not implement that bytes “imply cash solely.” If somebody constructs legitimate transaction bytes that additionally kind a sound picture file, the community shops and relays them.
Bitcoin can discourage sure information patterns by software program defaults. It can’t forestall 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 layer | What it controls (plain English) | What it could actually’t assure | Why it issues right here |
|---|---|---|---|
| Consensus guidelines | What makes blocks/tx legitimate | Can’t implement “money-only that means” | If it’s legitimate, it may be mined |
| Coverage / standardness | What nodes relay / mempools settle for by default | Will be bypassed | Filters add friction, not certainty |
| Miners’ inclusion | What will get into blocks | Incentives override preferences | Charges can “purchase” inclusion |
| Direct submission pipelines | Bypasses relay community | Concentrates entry | “Pay-to-play” danger (Slipstream-type routes) |
Coverage can gradual conduct, elevate friction, and impose prices. It can’t assure prevention if a transaction stays consensus-valid and pays ample charges.
Miners can embrace any consensus-valid transaction, particularly when it reaches them by paths that bypass common node relay.
OP_RETURN measurement limits have at all times 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, similar to stuffing information 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 methodology, 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. Companies 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 once they comply with consensus guidelines. The service routes round defaults relatively than breaking guidelines.
This creates a centralization vector that stricter filters could amplify. When common nodes will not relay sure transaction sorts, 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 is 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 roughly one 12 months.
| Area / space | What BIP-110 proposes (plain English) | What it’s attempting to forestall | Primary tradeoff / danger |
|---|---|---|---|
| New output scripts | New scriptPubKeys > 34 bytes invalid (besides OP_RETURN allowance) | Information stuffed into outputs | Threat of pushing information elsewhere |
| OP_RETURN exception | OP_RETURN allowed as much as 83 bytes | Small provable notes | Critics: nonetheless doesn’t “ban information” |
| Payload limits | Caps sure pushed information parts (normal 256-byte ceiling with exceptions) | Massive embedded blobs | Workarounds could emerge |
| Witness stack parts | Limits witness ingredient sizes (normal 256 bytes) | Inscription-style payloads | May redirect to worse encodings |
| Period framing | Short-term (~1 12 months) | Tactical slowdown | Implies “no clear everlasting repair” |
| Second-order impact | If information shifts into UTXO-like outputs | Keep away from long-term node burden | Backfire 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 parts, usually capping them at 256 bytes with slim exceptions.
Supporters body BIP-110 as a measure that protects node operators from runaway storage prices.
Critics warn about unwanted side effects and implementation dangers. The proposal represents an escalation from policy-level filtering to consensus-level restriction, a shift carrying governance implications past the quick 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 totally different encodings.
The underlying dynamic persists: squeeze one sample, and incentives plus ingenuity push information elsewhere.
The momentary framing, one 12 months relatively than everlasting, acknowledges this actuality implicitly. A everlasting change would require confronting tougher questions concerning the sustainability of enforcement.
A short lived measure admits the issue could lack a clear technical answer, solely tactical administration with a restricted shelf life.
The worst-behavior downside
Proscribing in style information pathways can backfire by pushing utilization towards encodings that impose greater community prices.
When builders create outputs that look spendable to hold arbitrary information, they improve 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 information 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 relatively than growing old away.
This explains Bitcoin Core’s historical reluctance to impose harsh limits on OP_RETURN. The choice is not essentially higher. Filters that appear protecting can improve long-term working prices for nodes, undermining the decentralization aim they intention to protect.
Three paths ahead
The enforcement economics recommend three eventualities.
The primary path maintains the established order: value it, do not ban it. Arbitrary information persists, ruled primarily by payment markets. When blockspace turns into scarce, data-heavy transactions are naturally priced out. The lever turns into financial relatively than technical.
The second path tightens coverage filters whereas leaving consensus unchanged. Information 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 verify these transactions.
The third path implements consensus restrictions, similar to these outlined in BIP-110. Widespread patterns could briefly decline, however adaptation continues as new encodings emerge. Collateral injury will increase if limits push information 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 result
Three indicators sign which state of affairs materializes.
First, miner conduct. Do mining swimming pools proceed accepting non-standard transactions by direct channels? Companies 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 necessary as technical benefit.
Third, second-order results. Do restrictions push extra information into encodings that improve node burden? UTXO progress charges throughout coverage tightening durations would supply empirical proof.
The uncomfortable actuality
Should you oppose on-chain information storage past monetary transactions, Habovštiak’s demonstration delivers an uncomfortable message: you most likely cannot ban it.
You possibly can value it by payment markets. You possibly can discourage it by coverage defaults. You possibly can elevate friction by implementation complexity.
However full prevention requires both accepting financial constraints you can’t management or implementing consensus restrictions that carry their very own dangers.
Bitcoin validates transaction construction, not that means. The protocol does not distinguish between “cash transactions” and “information transactions” as a result of that distinction requires interpretation that the community can’t carry out.
The actual debate is not whether or not Bitcoin can technically forestall arbitrary information, because the demonstrated reply is “not simply, and maybe under no circumstances.”
The controversy is which tradeoffs the community accepts: centralization towards miners who bypass filters, governance danger from contentious consensus modifications, or greater 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.
