# Bitcoin’s Data Debate: The OP\_RETURN Policy Shift, Explained ### Tl;DR * **OP\_RETURN** lets people attach extra data to Bitcoin transactions. * There *was* a cap – 80 bytes max by default – originally added to limit spam and reduce node strain. * Starting **October 2025,** [Bitcoin Core v30](https://x.com/bitcoincoreorg/status/1931299560329982374?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1931434755104665963%7Ctwgr%5Ece20013a43f5d6ee0c37fa4127749818c0fd5614%7Ctwcon%5Es2_\&ref_url=https%3A%2F%2Fbeincrypto.com%2Fbitcoin-core-op-return-limit-version-30%2F) will remove this limit from its default mempool policy – effectively enabling up to 4MB of arbitrary data. * Supporters see this as long-overdue modernization. Critics call it a betrayal of Bitcoin’s monetary purpose. * Beyond code changes, this is about what Bitcoin *should* be — a hard-money ledger, or a programmable platform? ### What is OP\_RETURN? Bitcoin’s scripting language includes “opcodes”. They are script instructions – like tiny commands – that tell the blockchain how to process a transaction. OP\_RETURN is one such opcode. It lets users attach arbitrary, provably unspendable data to a transaction. Think of it like a sticky note you can attach to a transaction – extra info that doesn’t move coins but carries meaning. Why would anyone want to do that? To anchor external protocols (like BRC-20), timestamp a document, or even write the occasional meme on-chain. The thing is, OP\_RETURN data isn’t “spendable.” It doesn’t move coins around. And because it’s not needed to validate the Bitcoin supply, most node operators are free to ignore it – or “prune” it to save space. ### The Mempool Showdown (and What's Changing) Until now, Bitcoin nodes by default only relayed OP\_RETURN data of 80 bytes or less. So the size was not limited by consensus rules – but a mempool policy. But since most nodes run with default settings, it effectively shaped what the network would accept. That’s about to change. In **Bitcoin Core v30**, scheduled for release in **October 2025**, the default mempool policy will stop filtering out large OP\_RETURN transactions. That means: * The **80-byte limit is gone** for default node behavior. * Nodes may now **relay up to 4MB of arbitrary data per output**, matching Bitcoin's max block size. * While node operators *can* still manually override this, most won’t – making this a **de facto policy shift** across the network. ### The Battle Lines **The “Let It Grow” Camp** * [Peter Todd](https://x.com/peterktodd) , [Antoine Poinsot](https://x.com/darosior), and others back the change, arguing it reduces misuse of worse parts of Bitcoin (e.g., the UTXO set). * They believe Bitcoin should evolve — enabling things like BitVM, zero-knowledge proofs, timestamped records, and recursive contracts. * Other chains allow arbitrary data — why shouldn’t Bitcoin? **The “Keep Bitcoin Clean” Camp** * [Samson Mow](https://x.com/excellion) and [Luke Dashjr](https://x.com/LukeDashjr) oppose the change, warning it distracts from Bitcoin’s core function: sound money. * They believe Bitcoin is for money – not messages, NFTs, or memes. * They argue larger relay sizes encourage bloat, spam, and unnecessary complexity. * In their view, Bitcoin is not a smart contract or data storage platform — it’s a financial protocol. ### The Bigger Picture This isn’t just about an 80-byte rule. It’s about what kind of future Bitcoin is building toward. * Is it a rigid monetary system that resists experimentation? * Or is it a base layer for building new protocols – like Fractal – that extend its utility without breaking its core? The new policy signals a shift: Bitcoin will tolerate more data, by default. Whether that becomes a feature or a bug depends on what we do with it. ### Fractal’s View: Let Builders Build At Fractal, we see OP\_RETURN for what it is: a *sandboxed innovation surface*. One that lets builders experiment safely, without touching Bitcoin’s monetary core. That’s why: * Fractal supports OP\_RETURN-based metadata protocols — anchoring data without bloating the UTXO set. * We provide an scalable venue for high-volume activity (e.g., 8–10M inscriptions daily). * We reduce mainnet congestion – while staying fully Bitcoin-compatible. * We mirror Bitcoin Core: as Core evolves, so do we. We welcome Bitcoin Core’s shift — and we’re ready for it. While Fractal follows Core policy, we already support OP\_RETURN-based metadata anchoring at scale. It’s live. It’s prunable. And it’s built for what’s next. ### Final Thoughts Bitcoin Core v30’s mempool policy update doesn’t just lift a data cap — it reignites a deep philosophical debate. Some will use it to build more expressive apps on Bitcoin. Others will use it to argue that Bitcoin is losing focus. At Fractal, we’re focused on this: Give builders the tools. Stay rooted in Bitcoin. Scale responsibly. > Is Bitcoin a locked-down ledger, or a launchpad for builders? > > We believe it can be **both** — if we do it right. **Want to see OP\_RETURN in action?** Start [building on Fractal](https://fractalbitcoin.io/build) — the innovation layer for Bitcoin. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fractalbitcoin.io/articles/bitcoins-data-debate-the-op_return-policy-shift-explained.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.