--
Share
In Bitcoin, the most consequential decisions often hide in the quiet corners of GitHub. They aren’t the big, dramatic fights that make headlines. They’re the small pull requests — the one-liners that set the tone for how the protocol is actually used. One of those moments happened in 2014, when Core developers debated how much arbitrary data should be allowed in OP_RETURN.
A fix was proposed: restrict the data carrier size. Define its meaning clearly. Make it unambiguous that Bitcoin is for money, not for storage. That proposal was rejected.
Ten years later, we’re still paying for that mistake.
Today, PR #29187 reintroduces the same concept: limiting Bitcoin’s data carrier to stop abuse. The irony? What was dismissed in 2014 as “too restrictive” is now framed as a necessary defense against inscriptions clogging the chain. It should have been merged back then.

