Strategy executive chairman Michael Saylor and Blockstream co-founder Adam Back have rejected BIP-110, a proposed soft fork intended to restrict arbitrary data embedded in Bitcoin transactions. Their opposition sharpens a dispute over whether Bitcoin’s consensus rules should distinguish monetary activity from inscriptions, images and token metadata. Saylor argued that the proposal would convert a disagreement about spam into a protocol change invalidating transactions that remain valid and pay fees. The controversy is therefore less about Ordinals than about who may redefine acceptable Bitcoin usage, a question that becomes consequential whenever network participants attempt to transform cultural preferences into enforceable consensus.
There are 110 things more dangerous to Bitcoin than spam.
BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions.
That precedent is the danger. We should save our energy for threats that really matter. $BTC https://t.co/LoSkl9XSo1
— Michael Saylor (@saylor) July 11, 2026
BIP-110 turns blockspace policy into consensus rules
BIP-110, formally described as the Reduced Data Temporary Soft Fork, would impose consensus-level data restrictions for one year. Its rules would limit new output scripts to 34 bytes, retain an 83-byte allowance for OP_RETURN outputs and restrict many data pushes or witness elements exceeding 256 bytes. The proposal also introduces limitations affecting selected Taproot structures and undefined witness versions. Supporters frame these restrictions as defensive infrastructure rather than transaction censorship, arguing that arbitrary data burdens node operators, competes with payments and redirects development attention from Bitcoin’s monetary role. Existing outputs created before activation would receive grandfathered treatment under the specification.
Yet the mechanism creates a paradox. Bitcoin’s censorship resistance is celebrated because valid transactions compete through fees, without authority judging their purpose. BIP-110 would instead encode a technical boundary around forms of data, even when users compensate miners for block space. Saylor warned that this precedent could matter more than the alleged spam problem, because future campaigns might invoke similar logic against other disfavored activity. His objection treats protocol restraint as a strategic asset, suggesting that Bitcoin’s credibility ultimately depends not merely on fixed supply but on avoiding interventions that appear reasonable during one dispute and dangerous during the next.
Back warns that dissent does not equal network consensus
Back reached a conclusion while addressing advocates who believe the network requires stronger protection from inscriptions. He acknowledged their concerns but said Bitcoin had effectively rejected the requested direction, adding that dissatisfied participants could coordinate a separate fork. His argument emphasized permissionless participation: users may propose rules and run alternative software, but they cannot compel the network to follow. Back’s response casts rejection as evidence that decentralized governance is functioning, however frustrating that appears to reformers. The absence of formal authority means consensus emerges from independent choices by miners, node operators, businesses and users, not from rhetorical certainty or credentials.
On the filter fork topic.
I don't usually have time, but this morning listened to one of the twitter spaces from earlier in the week, with some well meaning relative bitcoin newcomers, that humanized them, and their concerns and thoughts for why they thought that made it…
— Adam Back (@adam3us) July 11, 2026
BIP-110 uses a user-activated soft-fork design and offers early lock-in if 55% of blocks signal during a difficulty period, followed by mandatory signaling under its timeline. Recent monitoring showed miner support below 1%, with no major pool providing backing, while node adoption remained limited. The proposal now risks producing a minority chain rather than changing Bitcoin’s dominant rules, exposing the practical difference between publishing a Bitcoin Improvement Proposal and securing adoption. Whether inscriptions represent harmful data or legitimate demand remains unresolved, but Saylor and Back insist consensus engineering is the riskier battlefield.