For anyone not massively technically minded about the whole Core vs Knots debate
This is Grok's simplified answer...
Bitcoin’s OP_RETURN is a feature that lets users add a small amount of data (like notes or timestamps) to transactions on the blockchain.
It’s currently limited to 80 bytes to prevent spam and keep Bitcoin focused on financial transactions.
Recently, a Bitcoin Core developer, Peter Todd, proposed removing this 80-byte limit and allowing multiple OP_RETURN outputs per transaction.
Supporters, like Todd, say this would simplify the code, support new use cases (like sidechains), and reduce network congestion without bloating the blockchain’s critical data set (UTXO).
Critics, like developer Luke Dashjr, argue it could turn Bitcoin into a general data storage system, encouraging spam, illegal content, or non-financial uses, which they see as betraying Bitcoin’s purpose as a decentralized currency.
The debate is heated because it’s not just technical—it’s about Bitcoin’s core identity: money vs. a broader data platform. It echoes past fights, like the 2014 “OP_RETURN Wars,” and shows deep divisions in the community.
Some worry about centralization if developers push changes without consensus, and others see moderation (like muting critics on GitHub) as censorship.
For now, the proposal is under review, but it’s sparking big arguments online.
Grok today