The OP_RETURN Controversy: Bitcoin Core vs. Bitcoin Knots
Bitcoin has never been free of internal debates.
The block size wars of 2017 taught us how messy and consequential, governance disputes can be.
Today, another conflict is brewing, this time over something most users barely notice: OP_RETURN.
At first glance, this may seem like an obscure technical quibble. But the fight between Bitcoin Core (the dominant reference implementation) and Bitcoin Knots (an alternative client maintained by Luke Dashjr) could have real consequences for Bitcoin’s future direction.
Let’s break down what’s happening, why it matters, and where it could go.
ON BITCOIN is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
What is OP_RETURN?
OP_RETURN is a Bitcoin script opcode that allows transactions to carry arbitrary data in an unspendable output.
Originally limited to a few dozen bytes, it became a controlled way for developers to attach metadata to transactions, think digital notaries, timestamping, or basic asset issuance.
The catch?
OP_RETURN can also be used to embed anything: from memes to NFT-like inscriptions, even entire documents.
To prevent abuse and “data spam,” Bitcoin Core has historically capped OP_RETURN outputs at 80 bytes.
