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 knowledge doorway does not take away the potential, it simply modifications the place bytes cover.
The demonstration lands amid Bitcoin’s most contentious governance battle in years. One faction needs stricter filters to maintain “spam” off the blockchain.
One other argues that harsh restrictions push folks into worse behaviors and benefit massive miners. Habovštiak’s experiment offers proof for the second place: filtering redirects relatively 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 not too long ago relaxed, and Taproot’s witness construction that enabled many inscriptions.
Bitcoin transactions are bytes. Nodes implement that bytes observe structural guidelines, corresponding to legitimate signatures, correct formatting, and bonafide 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 by way of software program defaults. It can’t 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 layer | What it controls (plain English) | What it may’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” threat (Slipstream-type routes) |
Coverage can sluggish habits, elevate friction, and impose prices. It can’t assure prevention if a transaction stays consensus-valid and pays enough charges.
Miners can embrace any consensus-valid transaction, particularly when it reaches them by way of 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 folks into worse encodings, corresponding to stuffing knowledge into outputs that seem spendable, bloating the UTXO set that each node should preserve.
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. Companies explicitly launched for this exist already.
MARA’s Slipstream operates as a direct submission pipeline for “massive or non-standard” transactions that nodes usually exclude from mempools even after they observe consensus guidelines. The service routes round defaults relatively than breaking guidelines.
This creates a centralization vector that stricter filters might amplify. When common nodes will not relay sure transaction varieties, solely miners and specialised providers 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 folks pay?”
BIP-110 and the governance battlefield
The demonstration arrives as Bitcoin debates BIP-110, a proposal to quickly limit data-carrying transaction fields on the consensus degree for roughly one 12 months.
| Discipline / space | What BIP-110 proposes (plain English) | What it’s attempting to forestall | Principal tradeoff / threat |
|---|---|---|---|
| New output scripts | New scriptPubKeys > 34 bytes invalid (besides OP_RETURN allowance) | Knowledge stuffed into outputs | Threat of pushing knowledge elsewhere |
| OP_RETURN exception | OP_RETURN allowed as much as 83 bytes | Small provable notes | Critics: nonetheless doesn’t “ban knowledge” |
| Payload limits | Caps sure pushed knowledge parts (basic 256-byte ceiling with exceptions) | Giant embedded blobs | Workarounds might emerge |
| Witness stack parts | Limits witness component sizes (basic 256 bytes) | Inscription-style payloads | Would possibly redirect to worse encodings |
| Period framing | Short-term (~1 12 months) | Tactical slowdown | Implies “no clear everlasting repair” |
| Second-order impact | If knowledge shifts into UTXO-like outputs | Keep away from long-term node burden | Backfire threat: UTXO bloat will increase |
The draft would make new output scripts exceeding 34 bytes invalid, aside 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 effects and implementation dangers. The proposal represents an escalation from policy-level filtering to consensus-level restriction, a shift carrying governance implications past the instant 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 building, but additionally that he might produce options utilizing totally different encodings.
The underlying dynamic persists: squeeze one sample, and incentives plus ingenuity push knowledge elsewhere.
The non permanent 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 brief measure admits the issue might lack a clear technical resolution, solely tactical administration with a restricted shelf life.
The worst-behavior downside
Proscribing fashionable knowledge pathways can backfire by pushing utilization towards encodings that impose increased community prices.
When builders create outputs that look spendable to hold arbitrary knowledge, they improve the UTXO set, which is the database of unspent outputs each full node should preserve in accessible storage.
UTXO development 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, probably indefinitely.
The node price accumulates relatively than getting 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 purpose they goal to protect.
Three paths ahead
The enforcement economics recommend 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 relatively 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 threat rises as a result of solely miners and specialised pipelines can reliably verify these transactions.
The third path implements consensus restrictions, corresponding to these outlined in BIP-110. Well-liked patterns might quickly decline, however adaptation continues as new encodings emerge. Collateral harm will increase if limits push knowledge into outputs that bloat the UTXO set.
Governance threat escalates as contentious consensus modifications elevate coordination challenges and the potential for community splits.
What decides the end result
Three indicators sign which state of affairs materializes.
First, miner habits. Do mining swimming pools proceed accepting non-standard transactions by way of 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 essential as technical advantage.
Third, second-order results. Do restrictions push extra knowledge into encodings that improve node burden? UTXO development charges throughout coverage tightening durations would offer empirical proof.
The uncomfortable actuality
For those who oppose on-chain knowledge storage past monetary transactions, Habovštiak’s demonstration delivers an uncomfortable message: you most likely cannot ban it.
You’ll be able to value it by way of price markets. You’ll be able to discourage it by way of coverage defaults. You’ll be able to elevate friction by way of 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 that means. The protocol does not distinguish between “cash transactions” and “knowledge 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 stop arbitrary knowledge, because the demonstrated reply is “not simply, and maybe by no means.”
The controversy is which tradeoffs the community accepts: centralization towards miners who bypass filters, governance threat from contentious consensus modifications, or increased long-term prices from worse encoding selections.
Habovštiak’s picture proves the filters do not work as marketed. What comes subsequent depends 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.
