- Adam Back advocates indistinguishable block data via cryptographic accumulator concept, arguing censorship resistance strengthens satoshi fungibility across transactions.
- Operational impacts include higher block-space demand, potential congestion during peaks, shifting fee markets, and mempool policy fragmentation risks.
Adam Back, co-founder of Blockstream, renewed a long-running dispute over Bitcoin client policy. The trigger is Bitcoin Core v30, due in October, which lifts the OP_RETURN limit to 100,000 bytes. OP_RETURN lets users attach arbitrary data—texts or images—to transactions. Some node operators call these inscriptions “spam” because they increase block weight without moving coins. Others argue fees decide inclusion.
here's an argument i consider more persuasive for spam tradeoffs run amok: as bitcoin tech improves, we should have more cryptographic fungibility, and the blockchain converges to a cryptographic accumulator. you can't censor anything, you can't filter anything as it's all blobs.
— Adam Back (@adam3us) August 20, 2025
Back set out a clear stance. He says Bitcoin should move toward a “cryptographic accumulator,” where blocks carry indistinguishable data. In that design, nodes and miners would not filter payloads because everything would appear as raw bits. He links that approach to stronger fungibility, where one satoshi is as good as any other. He also said he plans to run Core v30.
However, pushback arrived fast. BitcoinMechanic, who operates Knots nodes, warned that indistinguishable payloads weaken public auditability, much like experimental confidential schemes. Peter Todd, a long-time Core contributor, took the opposite view and wrote that blocks “completely filled with indistinguishable garbage” help privacy.
Another user framed it as speech and miner choice: if a miner pays for power and wins a block, that miner decides what to include. Meanwhile, Giacomo Zucco argued that strict mempool filters fail to stop spam and can even make it worse.
“Use whatever mempool filter you want. Your mempool, your rules. It doesn’t change anything, it doesn’t affect me. What is worrying is that this artificial drama driven by podcasters and people with no technical background is dividing the community. This isn’t a problem now, but it will be when Bitcoin faces real adversaries seeking to fork the network. NFTs are not a serious adversary. We saw this in 2017, and it will happen again. It’s classic divide and conquer.” – CalleBTC, Bitcoin developer.
By contrast, AntonBTC noted that filtering predates OP_RETURN (added in 2014) and remains in Core 29, where OP_RETURN is capped at 83 bytes. CalleBTC added a pragmatic line: “your mempool, your rules,” while warning that media theatrics risk social splits.
I really don't understand why nobody seems to be able to make the simple, consistent, honest point: "I'm skeptical of maintaining the long tradition of mempool spam-filtering in Core and in favor of loosening it, since spam attacks are so intense now it may be counterproductive… https://t.co/gXRGBEuDvS
— Giacomo Cringe-Lord Zucco⚡️🌋🧀 (@giacomozucco) August 21, 2025
For markets, the trade-offs are concrete. Larger OP_RETURN payloads can raise demand for block space and fee revenue. Yet they also crowd out plain transfers during busy periods. Moreover, if blocks become harder to parse, privacy can rise while real-time forensics becomes slower.
Until nodes upgrade and miners coordinate around v30, nothing changes on chain. Still, the October release frames an old tension: users want privacy and fungibility; auditors want clarity and simple verification.
