State of the debate: OP_RETURN and arbitrary data on Bitcoin

⚠️ Time-sensitive — not re-verified since `asOf` (2026-07-22). Much of the state described below has a clock on it: Bitcoin Core v30's raised OP_RETURN relay default and the Core-vs-Knots split are given as current conditions, the "Cat" draft is recorded as still carrying no verified BIP number, and — noted inline — BIP-110's August 2026 window is reported closed without activation, with proponents said to be turning to a proof-of-work change instead. That last update rests on owner testimony (stated 2026-08-11), not a primary source. It is also the clearest illustration of why this warning exists: the brief was edited on 2026-08-11 without being re-verified, so asOf was deliberately left at the date of the last actual verification. Re-verify against a primary source before relying on the status of BIP-110, the Cat draft, the reported proof-of-work follow-on, or current relay defaults.

The longest-running active dispute in Bitcoin (inscriptions 2023 → Core-vs-Knots 2025 → BIP-110/"Cat" 2025–26): whether non-monetary data belongs on the chain, and if not, what layer of the stack should say so. The 2025 escalation path ran: Bitcoin Core v30 raised the default OP_RETURN relay limit from ~83 bytes to 100kB (policy only, not consensus) → filter advocates promoted the Knots alternative implementation → a soft-fork draft (BIP-444) was assigned as BIP-110 (2025-12-03) proposing one-year consensus-level data restrictions → a companion "Cat" draft proposed making low-value data-bearing UTXOs unspendable. BIP-110 miner signaling sat below 2% approaching its August 2026 window, and that window has now closed without activation — per the repo owner, stated 2026-08-11, the proposal has failed, with its proponents reportedly turning to a proof-of-work change instead. That is owner testimony rather than a primary source: it is recorded because this brief previously described the window as upcoming, and re-verification against a primary source is still wanted. What failed is a proposal, not the question — the dispute below is about whether non-monetary data belongs on the chain and who gets to say so, and BIP-110's defeat resolves none of it.

Live questions

• Is data embedding a present harm, a future risk, or a self-limiting fad? (Empirics contested and fast-moving — see inscription-demand-has-collapsed.)
• Can any technical layer actually stop it, and at what cost? (Policy filters: no guarantee — relay-filters-cannot-stop-determined-data-embedding; consensus fork: contested — a-soft-fork-can-remove-arbitrary-data-from-bitcoin.)
• Is "spam" even a coherent category for fee-paying valid transactions? (fee-paying-transactions-cannot-be-spam.)
• Does building filtering capability protect Bitcoin from state pressure or hand the state its lever? (filter-capability-invites-broader-censorship.)
• Do illegal-content scenarios (CSAM, leaked documents) change the calculus, and are they evidenced or hypothetical? (csam-is-prevalent-on-the-bitcoin-blockchain, node-operators-face-legal-liability-for-embedded-data.)

Main positions (strongest forms)

1. Money-only / restrictionist: Bitcoin's purpose is money; data embedding externalizes permanent storage costs onto every future node, invites legal and political attack, and should be closed off at whatever layer works — one decisive soft fork being more honest than perpetual filter maintenance.
2. Permissive / market-decides: Validity plus fees is the only neutral rule a permissionless system can enforce; filters are ineffective against adversaries and corrosive as precedent; empirically the market already disciplines low-value uses, and some non-monetary uses (timestamping) are legitimate and near-costless.
3. Filter-at-the-edge (Knots-style middle): Consensus stays untouched, but node operators should ship and maintain restrictive relay defaults as an expression of operator preference and friction against industrial embedding — accepting imperfection.

Related corpus entries

arbitrary-data-undermines-bitcoins-monetary-function, relay-filters-cannot-stop-determined-data-embedding, op-return-filtering-is-technically-trivial, minority-unfiltered-relay-defeats-filtering, fee-paying-transactions-cannot-be-spam, csam-is-prevalent-on-the-bitcoin-blockchain, node-operators-face-legal-liability-for-embedded-data, a-soft-fork-can-remove-arbitrary-data-from-bitcoin, data-restriction-soft-forks-are-true-soft-forks, filter-capability-invites-broader-censorship, inscription-demand-has-collapsed, small-block-position-was-vindicated. Reference points: BIP-110; the "Cat" UTXO draft (no number verified as of asOf date).

Open questions a debate could resolve

• A working definition of "spam" that both camps would sign — or an explicit agreement that none exists and policy must be argued without the word.
• Which observable would change minds: what embedding volume, node-cost trend, or legal event would make a permissive debater accept restriction (or vice versa)?
• Where each debater locates the legitimate decision layer — market, relay policy, miner policy, or consensus — and whether their position is consistent across this and past disputes.
• Whether the one-year sunset design of BIP-110 is credible (would it actually be allowed to lapse?), a question no one on stage has answered directly.