Bitcoin’s 1-MB OP_RETURN Block Breaks Records as Blockchain Becomes a Message Board

Bitcoin’s 1-MB OP_RETURN Block Breaks Records as Blockchain Becomes a Message Board

N
News Editor 01
2026-07-08 18:24:12
Block 896,696 contained the largest OP_RETURN transaction in Bitcoin history, occupying nearly 1 MB of data. The experiment challenged the default 80-byte limit, sparking debates on protocol direction and miner incentives.
BitcoinOP_RETURNblock recordmining poolprotocol debate

In a development that underscores growing tensions over Bitcoin’s data embedding capabilities, block 896,696 has become the first to feature a full 1-MB OP_RETURN transaction. The block, mined on May 15, 2025, was crafted by a group known as “The Wizards of Ord” to include the entire set of 3,333 inscriptions from their Ordinals collection. The move was hailed by the group’s X account @lifofifo as “the largest OP_RETURN in Bitcoin history” and “the first-ever 1 megger.”

Bypassing the 80-Byte Standardness Rule

OP_RETURN is a Bitcoin Script opcode that allows embedding up to 80 bytes of unspendable data without bloating the UTXO set. However, this 80-byte limit is not a consensus rule but a standardness policy enforced by most full nodes. The Wizards of Ord circumvented this by marking the transaction as non-standard and submitting it directly to mining pool Marathon (MARA). MARA opted to ignore default relay policies and included the transaction, which carried a generous fee despite transferring 0 BTC.

The transaction employed Bitcoin’s v2 format with SegWit support, providing expanded scripting capabilities. By paying a sufficiently high fee, the creators incentivized the miner to include the data-heavy transaction, challenging the typical fee-per-byte economics.

Creative Expression and the ‘OP_RETURN War’

In the weeks leading up to the record block, a flurry of OP_RETURN messages flooded the network, fueling what some call the “OP_RETURN War of 2025.” One message cleverly riffed on Rick Astley’s 1987 hit: “Never gonna give you OP_RETURN, never gonna let you down …” Others contained commentary such as “Filters have a huge influence on what gets mined.” These experiments coincide with a Bitcoin Core proposal to remove the 80-byte cap on script opcodes, which has stirred debate among developers and the broader community.

Rise of Bitcoin Knots Node Software

As on-chain data storage grows, more node operators are turning to Bitcoin Knots, an alternative implementation that retains the -datacarrier and -datacarriersize flags. These parameters allow operators to reject all OP_RETURN transactions (with -datacarrier=0) or enforce a strict 80-byte maximum. Knots adoption jumped from around 600 nodes in mid-March to approximately 2,000 nodes by mid-May, though this still lags behind the roughly 19,470 public Bitcoin Core nodes.

Redefining Bitcoin’s Role

The escalating OP_RETURN experiments signal a growing appetite for creative control at the protocol’s periphery. While some view Bitcoin as a pure peer-to-peer payment network, others see potential for data storage and timestamping. With node software diverging and miners responding to new economic incentives, the network appears to be entering a phase of quiet redefinition—where policy, purpose, and participation are being tested one byte, one block, and one meme at a time.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
100

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.