Bitcoin's OP_RETURN cap: spam shield or pointless fork?
One side wants to shrink the data tap before the chain fills with junk. The other says the panic is louder than the actual problem.
BIP-110 would limit OP_RETURN storage to deter arbitrary data uploads. Side A sees it as essential defense against spam and illicit content; Side B argues the issue is minor and a soft fork won't change core incentives.
Why these scores — Side A evidence rests on visible OP_RETURN inscriptions and explicit mentions of porn/spam; Side B evidence is mostly qualitative dismissal of scale without counter-metrics. No bot signatures detected, but both rely on selective chain snapshots rather than full node telemetry.
Bitcoin blocks are quietly filling with images and text that have nothing to do with payments. BIP-110 tries to cap OP_RETURN at a smaller size to slow that trend.
Proponents argue unsupported data methods already exist and can be patched later, so official limits on OP_RETURN are the cleanest first step. Opponents counter that spam volume remains low relative to total activity and that forks risk splitting attention without fixing fee markets.
The fight now sits at 69 engagement with 80 authenticity. Both camps cite on-chain patterns, yet neither has shown sustained node-level data proving the scale of the claimed problem or solution.
BIP-110 restricts OP_RETURN to stop porn and spam; other storage tricks are unofficial and can be closed later.
- @ScarcityMan“BIP-110 restricts OP_RETURN to prevent porn and spam; other storage is unsupported and fixable later.”
Spam fears are exaggerated and a minority fork will not fix Bitcoin's real data and fee issues.
- @LynAldenContact✓ verified“Concerns over spam are overblown; a minority fork won't solve real issues on Bitcoin.”
Read it straight — Compare actual daily OP_RETURN byte counts against total block weight over the last 12 months before taking either framing.