Many serious Bitcoiners believe arbitrary non-financial data is a threat to Bitcoin's role as money. Here is that affirmative case, made fairly, plus an honest look at the unresolved fight over how to defend the fundamentals.
There is a soft fork with a block height on it, and that changes everything about this conversation.
For two years the argument over inscriptions, ordinals, Runes, BRC-20, and giant OP_RETURN outputs lived on Twitter and in GitHub threads, where it read as a culture-war sideshow. Not anymore. A proposal known as BIP-110, the Reduced Data Temporary Softfork, is now sitting in the release of Bitcoin Knots with a signaling window that opens in early August and activation targeted around September 1, 2026. Whatever you think of it, it has forced a question a lot of people would rather keep vague back into the open: what is Bitcoin actually for?
My answer has never wavered. Bitcoin is money. Not a database with a coin bolted on, not a decentralized cloud drive you rent by paying a miner, not "crypto." Money. The whole point, per the first sentence of Satoshi's white paper, is "a purely peer-to-peer version of electronic cash" that moves value from one party to another without a financial institution in the middle. Everything else is downstream of that.
The best articulation of why arbitrary data threatens that mission came from Bitcoin Mechanic, Chief Boiling Officer at the OCEAN mining pool, across two long sits with Peter McCormack on What Bitcoin Did. I do not agree with him on how to fix the problem, and I will get to that honestly. But the affirmative case he lays out for the fundamentals is the strongest version of the sound-money worldview I have come across, and it deserves to be made well and made fairly. So I will build the case first, then tell you where I get off the train.
The deepest point Mechanic makes across both episodes is almost boring in its simplicity: Bitcoin is two things at once, and people keep loving only one of them. There is the currency, the thing with the 21 million cap that is unconfiscatable and does not melt in your hand like a fiat ice cube. And there is the payment network, the blockchain, the thing that moves that currency around without asking anyone's permission. These are not separate products. The store of value only exists because the payment network exists to defend it.
Here is the line that stuck with me. Every payment on the network is a reaffirmation that there are only 21 million bitcoin. That number is not a law of physics. It is a rule that requires constant reinforcement by people who verify it, and using Bitcoin as money is what reinforces it. Stop using the payment network, treat the chain as a place to park data, and you have quietly stopped defending the one property everyone claims to care about.
This is the separation of money and state made concrete. A monetary network has to stay lean, neutral, and hard to capture precisely because money is what states most want to control. Mechanic frames the moment as the mirror image of the block size war: back then, the big blockers loved the payment network enough to sacrifice the decentralization that made verification possible; today, the store-of-value crowd loves the currency so much they have forgotten the payment network is what keeps it alive. He needles Michael Saylor's "never spend, just hold" posture as a worldview that champions half the story and assumes the other half takes care of itself. A network optimized to be a permissionless monetary rail is a different thing than one optimized to store arbitrary content, and trying to be both is how you slowly stop being either.
Ask Mechanic why Bitcoin gets to call itself Bitcoin and not just another shitcoin with a better logo, and the answer is not the price or the brand. It is that the rules are simple and cheap enough that ordinary people can enforce them. That is the whole ballgame. You download a node onto a laptop, sync the chain, and from that moment you validate every rule for yourself. Nobody grants you that right and nobody can revoke it. Because the resource requirements are low and the feature set of the blockchain is minimal, verification stays within reach of a normal person, which means the rules are enforced by a wide base of users rather than a handful of professionals.
His warning is that arbitrary data attacks this from the side. It does not break anything on day one. It makes the chain heavier and nodes more expensive to run, and slowly converts running a node from something you do into something someone does for you. By his accounting, the inscription wave drove the UTXO set from roughly 4 gigabytes to 12 and the count from around 70 million UTXOs toward 200 million, writing off a class of cheap hardware that could previously sync a node. I have not audited those figures, but the direction is the part that matters, and it is not in dispute.
Here is the asymmetry that makes it a quiet emergency. If mining gets unprofitable, difficulty drops and miners come back. There is no such mechanism for nodes. If running one gets too painful, people just stop, nothing pulls them back, and only big data companies are left validating everything, at which point you are indistinguishable from every centralized system Bitcoin was built to escape. It is a genuinely good point.
Now the contested part, and I want to label it as what it is: an argument held by a camp, not a settled fact. Mechanic's position is that arbitrary data has always been treated as an attack to resist, and that this was uncontroversial network-engineering common sense right up until 2023. Framing inscriptions as "valid transactions," he argues, is a rhetorical move introduced by the people doing the inscribing, and calling it valid is like insisting you are obligated to read every spam email in your inbox. Spam is in the eye of the receiver. The sender never thinks their own message is spam.
What actually changed in 2023 is not in dispute. Casey Rodarmor's ordinals scheme figured out that after Taproot, you could stuff content into the witness portion of a transaction, wrapped in an OP_FALSE OP_IF envelope and revealed through a commit-and-reveal Taproot spend, and get the witness discount on top of it. That is how you put a JPEG, or a whole video, onto the chain at a discount, bypassing the old limits. Mechanic characterizes the underlying behavior as an exploit that got normalized after the fact. That framing is his, but the mechanics are documented and real.
His sharpest philosophical point is about obligation. You are not obligated to relay anything, and you have no incentive to relay a stranger's data to a miner for free while your own transactions compete for the same block space. A monetary network is useless if none of us relay each other's financial transactions, so we are incentivized to do that. But relaying somebody's picture of a cat? You owe that to no one.
This is where he thinks the other side gave the game away. For two years the argument was that spam filters do nothing. Then it quietly became that we must remove the OP_RETURN filter because it is working and pushing data storage toward more harmful methods. Both cannot be true, and the flip was, in his words, a lot of gaslighting. Even a neutral write-up at Bitcoin Magazine frames the pro-restriction position this way: spammers migrating to more expensive methods is itself evidence that filters bite.
Be fair to the other side, because they are not clowns. On the bitcoin-dev mailing list, Antoine Poinsot argued that the OP_RETURN limits "encourage harmful practices while being ineffective in deterring unwanted usage," the harmful practice being fake spendable outputs that bloat the UTXO set forever, which is worse for node operators than a prunable OP_RETURN. That is a serious argument made in good faith. Mechanic's rebuttal is that it treats a technically true point as if it settled the matter, when the actual scale of the harm points the other way. Reasonable, technical people land on opposite sides of this, which is exactly why nobody in this fight has a monopoly on intelligence.
"Who Really Controls Bitcoin" was the title of the second episode, and it is the argument underneath all the OP_RETURN minutiae. The popular framing goes: spammers want their data in the chain, miners want the fees, so it is going in the chain, end of story. Mechanic says that forgets a third party. The node. The node has no incentive to take your picture and hand it to Foundry to immortalize, and the node is where Bitcoin's sovereignty actually lives. He tells a story that should bother everyone: he talked to one of the largest Bitcoin exchanges in the world and learned they do not run their own node. A third party does it for them, and nobody there felt embarrassed about it. That is the road back to the internet we already have, where a few big companies run everything on your behalf and quietly become the gatekeepers.
His answer is the reason he works where he works. With centralized mining, a giant pool can stuff non-standard junk into a block and force everyone else to eat the cost, so nodes end up groveling and guessing what miners want. With decentralized mining, the incentive flips: a miner who packs a block full of filtered junk risks slower propagation and a higher chance of getting orphaned, so miners are punished for disrespecting nodes. That is the thesis behind OCEAN and its DATUM protocol, which lets individual miners build their own block templates instead of taking orders from a pool. When miners, not pools, decide what goes in a block, the node reclaims its seat at the top of the hierarchy.
He ties this to the block size war, which ended when node-running users asserted that it was them, not the miners, who decided the rules. And he makes one point that is genuinely clarifying, whatever you think of the policy: spam filtering and censorship resistance are opposites, not cousins. Bitcoin is censorship resistant because if almost the entire network tries to stop your transaction, you can still find one block and win. A spam filter is the reverse. Keep data out, find even one clean block, and the filter worked. The more people filter, the more effective it gets, which is why filtering is not censorship in the way the word usually gets thrown around.
The last plank of the affirmative case is the most counterintuitive and, I think, the most true: Bitcoin gets harder every time somebody tries to capture it and fails. Mechanic's model is the 2017 user-activated soft fork, BIP-148. At the time it looked insane. A few hundred nodes announced they would reject any block that did not signal for SegWit after August 1, and everyone laughed. Then the game theory did its work. No miner wanted to mine a chain that node operators would throw in the garbage, and the network activated SegWit at block 481,824 without the block size increase the big miners had demanded. The lesson is permanent: node-running users, the people with nothing to lose who will not compromise, ultimately enforce the rules. Miners follow the rules and the market. They do not get to write them.
The plebs, he says, are the network's greatest strength: big pools, exchanges, and Wall Street entrants do not want to play chicken with consensus against people who will not blink. It is also why the price tends to rip during these ugly fights. When it becomes obvious no faction can force its will on everyone else, the market reads that as Bitcoin being rock hard.
There is a cultural version too. His worry is not that a single JPEG kills Bitcoin overnight. It is that once you start rearranging the furniture to accommodate scammers, they move in, run nodes, influence the next round of development, and the culture drifts until one day it is just crypto with a Bitcoin logo. A network with no shared sense of what it is becomes a network you can talk into anything, and the people holding the fundamentals line see themselves as the immune system against exactly that.
Here is where I stop nodding along, and I want to be precise, because the disagreement is narrower than the Twitter version suggests.
I share the worldview. Bitcoin is money. Ordinals and BRC-20 and the rest are, in my view, economic noise, a casino that wandered over from a land where it would have been laughed out of the room and now cosplays as legitimate because Bitcoin's brand launders it. I do not want to relay that garbage either. The store-of-value-only crowd that treats the payment network as an afterthought is making a real mistake. On the fundamentals, we are on the same team.
Where I get off is the mechanism, because I think the thing the fundamentals camp fears most already happened, and Bitcoin already won.
Look at what the fee market did. At the 2024 halving block, 840,000, users spent a record 37.6 BTC, about $2.4 million, in fees fighting to inscribe rare sats and mint Runes. That was the top. Manias burn themselves out. The spammers paid enormous sums, and then the behavior collapsed under its own weight. Mechanic, to his credit, says the quiet part out loud in the second episode: the blockchain is now a ghost town, and the spam that hit fever pitch around the halving "just dwindled and it seems to be dying." He reads that as a cultural problem. I read it as the fee market working exactly as designed. Same facts, different conclusion.
That is the crux of my hesitation about changing consensus to filter data. The moment you bend the rules to punish a class of users you have decided you dislike, you have conceded the property that makes Bitcoin worth anything. Credible neutrality is not a bug to be patched when somebody uses block space in a way you find distasteful. It is the entire feature. The 21 million cap and the refusal to judge whose transaction is worthy are what let a dissident and a Michael Saylor use the same rails with the same confidence. Start deciding which uses are legitimate at the consensus layer and you are on Ethereum's road, where a motivated in-group reshapes the base layer around what it wants this quarter. I will not walk that road even for a cause I agree with.
And I can say all that without treating Mechanic as the enemy, because he is not dogmatic about it. He is the first to say a soft fork is the wrong tool for spam, that using consensus to swat data is like swatting a fly with a nuclear bomb, and that BIP-110's own text concedes we are right back to ordinary spam filters the day after it expires. He built in the one-year expiry and grandfathered every existing coin because he has been burned advocating for "perfect" upgrades before. Even Jameson Lopp, no fan of the proposal, walks through how it is a low-threshold user-activated soft fork with real chain-split risk. His warning that "there is nothing more permanent than a temporary solution" is one I take seriously in both directions.
So here is the honest landing. On the fundamentals, hold the line, no apologies. Bitcoin is money, nodes are sovereign, arbitrary data degrades the mission, and the people running Knots out of conviction are not the problem. On the mechanism, there is a live, unresolved argument between three answers: change consensus with something like BIP-110, trust the fee market that already broke the mania once, or fight it at the node and mempool policy layer without touching consensus. I lean hard toward the latter two. Mechanic keeps all three on the table. Bitcoiners who agree on everything that matters disagree here, and that tension is not a crisis. It is the immune system doing its job. A money that no faction can capture, not the spammers, not the developers, not the miners, not even the well-meaning filter advocates, is a money worth holding. The fight itself is the proof of work.
BIP-110, the Reduced Data Temporary Softfork, is a proposed consensus change that temporarily limits arbitrary data on Bitcoin. Per the BIP text, it caps OP_RETURN outputs at 83 bytes, limits standard outputs to 34 bytes, and restricts several Taproot features used by inscriptions, all expiring roughly a year after activation, with pre-existing coins grandfathered so nobody's funds get frozen. It uses a 55% miner signaling threshold, with a signaling window opening in early August 2026 and activation targeted around September 1. It first circulated as BIP-444 under the pseudonym Dathon Ohm.
The sound-money camp argues the opposite. Censorship resistance means that even if almost the whole network tries to block your transaction, you can still get into a block and win. Spam filtering is the mirror image: you only need one clean block for the filter to have worked. Declining to relay data you find objectionable is you exercising your own resources, not preventing anyone else from transacting. Removing the OP_RETURN limit does not censor anyone either, which is why Bitcoin Core framed its version 30 change around neutrality. Both sides claim the censorship-resistance mantle, which should tell you the word is doing too much work in this debate.
The fundamentals answer is node runners. Miners produce blocks and follow incentives, but the rules are enforced by the users who validate every block and reject anything that breaks them. The clearest historical proof is BIP-148 in 2017, when node operators forced SegWit activation despite miner foot-dragging. The catch is that this only holds while mining stays decentralized enough that no single pool can bully the network, which is why efforts like OCEAN's DATUM protocol matter here.
It is where TFTC parts with the pro-BIP-110 position while sharing its worldview. The inscription and Runes mania peaked at the 2024 halving with a record $2.4 million fee block and then collapsed on its own, fees falling back to almost nothing. The spammers paid dearly and the behavior burned out, no rule change required. The counterargument is that low fees today are a cultural problem, not a victory, and the trend could reverse. Fair. But the market disciplining it once, without anyone touching consensus, is a strong reason to be cautious about touching consensus.
We hold the fundamentals it is defending: Bitcoin is money, arbitrary data degrades that mission, and node sovereignty is non-negotiable. We do not endorse the specific mechanism of changing consensus rules to filter data, because our read is that the fee market already broke the spam mania and that bending the rules to punish disfavored users risks the credible neutrality that makes Bitcoin valuable. We would rather fight this at the node-policy and fee-market layers than at consensus. That is a disagreement about method between people who agree on the goal, which is a sign of a healthy network, not a broken one.
The affirmative case here is drawn primarily from Bitcoin Mechanic's two appearances with Peter McCormack. If you want his argument in full, unfiltered by me, start there.
Primary and reference sources:
Hold the fundamentals. Argue about the mechanism in good faith. Stay humble, stack sats. We're going to win.
