OP_RETURN
TECHNOLOGYDEFINITION
A Bitcoin script opcode that marks a transaction output as provably unspendable while allowing a small amount of arbitrary data to be attached to it — the standard way to timestamp or annotate a transaction without creating spendable, unused outputs.
OP_RETURN outputs were originally added to give developers a clean way to embed small amounts of data — timestamps, hashes, protocol messages — without bloating Bitcoin's UTXO set with unspendable "dust" that nodes must track forever. Because the output is provably unspendable, nodes can discard it from memory more efficiently than an ordinary spendable output.
The opcode has become more contentious as data-heavy uses — ordinal inscriptions, tokens, and other non-financial content — increasingly use OP_RETURN and similar mechanisms to store data on-chain, growing block sizes and node storage costs. That tension came to a head in August 2026, when a contested soft fork proposal, BIP-110, tried to cap OP_RETURN payloads at 83 bytes; it drew signaling support from barely 1% of miners before the activation attempt collapsed.
IN A SENTENCE
“OP_RETURN was supposed to be the tidy way to add a note to a transaction — now it's a proxy war over what belongs on the blockchain.”
Key facts
Common questions
Does OP_RETURN cost bitcoin holders anything?
Not directly — but data-heavy OP_RETURN usage adds to block size and node storage costs over time, which is the core of the ongoing debate over whether to limit it.
What happened with BIP-110?
A 2026 soft fork proposal tried to cap OP_RETURN payloads and shrink transaction outputs. It mined two blocks under its rules before miner signaling support collapsed to under 1%, far short of the 55% needed to activate.