Bitcoin’s block 896,696 has made history by hosting the largest OP_RETURN transaction ever seen on the network—a single transfer that consumed nearly an entire megabyte of block space. Dubbed the “first-ever 1 megger” by its creators, the event has sparked heated discussions about the protocol’s 80-byte limit on script opcodes, the power of individual nodes, and the very purpose of Bitcoin itself.
The OP_RETURN War of 2025
OP_RETURN is a Bitcoin script opcode that allows embedding up to 80 bytes of unspendable data without expanding the UTXO set. It is commonly used for timestamping, asset issuance, and inscriptions. However, the strict size ceiling has long been a point of contention. A recent proposal to remove the 80-byte constraint on script opcodes in Bitcoin Core has stirred spirited debate among developers and the broader community.
Proponents argue that lifting the cap would eliminate the need for convoluted workarounds, while opponents warn of potential spam and chain bloat. Since the change applies to relay policies rather than consensus rules, enforcement ultimately rests with individual node operators. This has led to what some are calling the OP_RETURN War of 2025.
Creative Exploits: Rickrolls and 1-Meggers
In the midst of the debate, OP_RETURN transactions have become an unexpected medium for creative expression. A recent transaction carried a playful twist on Rick Astley’s 1987 hit: “Never gonna give you OP_RETURN. never gonna let you down…” Another simply stated: “Filters have a huge influence on what gets mined.”
The most audacious experiment came on May 15 from a group known as The Wizards of Ord. They crafted block 896,696 to showcase their full collection of 3,333 inscriptions. To bypass the default 80-byte limit, the transaction was sent directly to mining pool Marathon (MARA), which chose to ignore standard relay policies. The transaction used SegWit-enabled v2 format, sent 0 BTC, and paid a generous fee to attract miners. The result: nearly 1 MB of arbitrary data packed into a single OP_RETURN, filling the entire block.
Node Software Fragmentation: Knots vs. Core
This event coincides with a surge in adoption of Bitcoin Knots, a full node implementation that retains granular control over OP_RETURN via the -datacarrier and -datacarriersize flags. Setting -datacarrier=0 outright rejects all OP_RETURN transactions from the mempool, while modifying -datacarriersize enforces strict data caps.
Knots node count has risen from roughly 600 in mid-March to approximately 2,000 currently, though this still lags behind the 19,470 publicly visible Bitcoin Core nodes. As node software diverges, the network appears to be entering a phase of quiet redefinition—where policy, purpose, and participation are tested one byte, one block, and one meme at a time.
Bitcoin’s Identity in Question
The flurry of OP_RETURN experiments underscores a fundamental debate: should Bitcoin remain a peer-to-peer payment system, or can it accommodate data storage and creative expression? Miners drawn by high fees, node operators enforcing strict filters, and community members arguing over consensus—all reflect a network in transition. As the boundaries of what is possible are pushed, the answers will shape Bitcoin’s evolution for years to come.