Murch, Bitcoin Core developer and editor of the official community enchancment proposals (BIP) repository, revealed on-chain information exhibiting that OP_RETURN outputs bigger than 83 bytes symbolize simply 0.0032% of Bitcoin’s complete block house.
In his publication, he described that share as “surprising” (in an ironic tone) directed in direction of those that warned that Bitcoin Core v.30 would open the door to probably unlawful content material and the spam within the Bitcoin community by having enabled a lot of these outputs.
The information comes from two Dune Analytics charts created by Murch himself, masking February 2023 to Might 2026. The primary information the weekly rely of OP_RETURN outputs sorted by dimension. Within the week analyzed by Murch, outputs longer than 83 bytes represented simply 0.000075% of the overall outputs.
The second graph measures the overall house occupied by these outputs in bytes per week: these bigger than 83 bytes absorbed 0.14% of the overall house consumed by OP_RETURN outputs, equal to 0.0032% of Bitcoin block house.
Each graphs uncovered by the developer present a low quantity of OP_RETURN outputs exceeding the 83-byte restrict on community utilization.
Opposite to the information supplied by Murch, a report revealed in mid-April by a Bitcoin node dealer warned that over the past quarter, registrations by way of protocols resembling Ordinals and Runes and transactions with OP_RETURN accounted for 44% of Bitcoin operations; of this share, virtually 63% had been OP_RETURN outputs.
This information, which coincides with what was reported by CriptoNoticias in October 2025, displays that, contemplating not solely OP_RETURN operations better than 83 bytes, the share indicated by Murch will increase significantly.
OP_RETURN is a Bitcoin opcode that enables arbitrary information (textual content, identifiers, information) to be included inside a transaction. Till Bitcoin Core 29, the restrict for that information was 83 bytes.
In October 2025, and after a debate that had begun months earlier than, Bitcoin Core 30 expanded that restrict to 100,000 bytes by defaulta change criticized by the bitcoiner neighborhood since, in accordance with its detractors, it facilitates the usage of Bitcoin as a file community, growing what they think about spam by taking on block house with out transferring financial worth.
Identical information, reverse arguments
Adam Again, co-founder of Blockstream, additionally satirically dismissed the alarm. In X he wrote that Bitcoin Mechanic (developer and one of the vital energetic critics of the change launched in Core 30) “positively price forking”in sarcastic reference to the place of those that suggest, resembling Mechanic, the introduction of a mushy fork by the BIP-110 proposal to keep away from the inclusion of arbitrary information in Bitcoin. For Again, this proposal is disproportionate to an affect that the information doesn’t assist.
One miner and node operator famous that “so why was it so necessary to open it by default within the reference implementation?”, warning that if the usage of OP_RETURN outputs bigger than 83 bytes is so marginal, the extension in Core v.30 wouldn’t have been needed.
Likewise, one other person responded with the identical logic: “It is not about amount, however about high quality,” arguing that the present low incidence doesn’t justify having opened the restrict and that the issue shouldn’t be what number of outputs exceed 83 bytes at this time, however what sort of content material might be embedded tomorrow with out restriction.
Steve Tippeconnic, a developer specializing in quantum, added a extra exact technical criticism. In line with him, increasing the restrict of OP_RETURN didn’t remedy the issue that its defenders argued, since the usage of information embedded within the witnessthe transaction house the place digital signatures are saved and the place protocols like Ordinals may also embed data.
Alternatively, stated the quantum specialist, the change opened up a brand new vector to embed information extra immediately and visiblywith out addressing the origin of the controversy. “Simply as everybody at BIP-110 predicted,” he wrote, tying that end result to warnings the proposal had raised earlier than Core 30 was launched.
BIP-110: the proposal that desires to reverse the change
BIP-110 is a mushy fork proposal created by nameless developer Dathon Ohm that seeks to limit non-financial makes use of of Bitcoin block house, reserving it for funds and settlements. As reported by CriptoNoticias, this proposal was included by default within the newest replace of the Bitcoin Knots shopper, a software program that filters the operations that Core v.30 enabled.
Activation of BIP-110 requires {that a} important mass of node operators set up that shopper voluntarily to provide the specified impact. If that adoption doesn’t happen, the BIP-110 guidelines by no means come into impact, since with out sufficient nodes to reject blocks with arbitrary information, the community will merely proceed to just accept them as earlier than.
In that context, Murch’s information reignited the controversy over whether or not the expanded OP_RETURN restrict represents an actual threat for Bitcoin or a disproportionate alarm.
