Ungovernable by Design

Why you cannot regulate math

Every few years the same demand resurfaces: make Bitcoin filter its content. People embed images in the blockchain, some of them spam, some of them worse, and the reaction is immediate — surely the protocol can be changed to keep the garbage out. Restrict the data fields. Cap the script sizes. Ban the opcodes that let people write arbitrary bytes into a financial ledger. The demand sounds modest, even responsible. It is also impossible, and the reason it is impossible is the most important fact about Bitcoin — more important than the supply cap, more important than the halvings — because it is not a fact about Bitcoin at all. It is a fact about information.

Adam Back — the cypherpunk whose Hashcash proof-of-work is the mechanism Satoshi built on — has stated the position as cleanly as anyone. Bitcoin is bearer, censorship-resistant money. Nobody likes spam, and nobody wants to see illegal content on the chain. But there are inherent fundamentals that govern all internet protocols and programming languages, and no amount of wishing exempts Bitcoin from them. Bitcoin is decentralized — ungovernable by design: each person can run whatever software and policy they want, and the only thing they must share is the Nakamoto consensus rules, because people who want to mutually transact have to enforce the same rules. Beyond that, nothing binds anyone. You cannot realistically prevent arbitrary data hidden in fields, keys, hashes, script constructs, client-side data invisible to the network, encrypted payloads, steganography. And you cannot materially restrict encoding by shrinking field sizes or part-hobbling the scripting language. Limit a 520-byte output field to 34-byte public keys and you have prevented nothing: people can, will, and already have used multiple outputs and multiple transactions to carry the same data.

That position rests on three technical truths, and each one deserves to be pulled out and examined, because together they form an argument that reaches far beyond cryptocurrency.

Three Truths About Substrates

Arbitrary data embedding is inevitable. Any computationally expressive environment can be used to encode arbitrary data. In Bitcoin, data can hide in keys, in hashes, in scripts, even in the timing patterns of transactions. This is not a design flaw someone forgot to patch. It is an unavoidable property of general computation. A system expressive enough to represent value transfers between arbitrary parties under arbitrary spending conditions is expressive enough to represent anything, because “anything” is just bytes and the system moves bytes. The openness that makes the protocol useful is the same openness that makes it a carrier for whatever people choose to encode.

Consensus defines validity, not intent. Bitcoin’s only enforceable law is Nakamoto consensus: a block is valid if it satisfies proof-of-work and follows the agreed chain rules. That is the entire constitution. There is no mechanism — nor could there be — for distinguishing “legitimate” from “illegitimate” data, because any system capable of telling intent apart from structure would need to interpret meaning, and meaning is not a property of bytes. It is a property of the relationship between bytes and the agents reading them. A judge can ask what a defendant meant. A hash function cannot. Consensus enforces structure; intent lives in heads, and heads are not part of the protocol.

Superficial limits do not work. Restricting field sizes or opcodes is like regulating the maximum dosage per pill to prevent overdose. Limiting the container does not limit the capability, because information — like dosage — integrates over the system as a whole. People take multiple pills. People send multiple transactions. Squeeze the data out of one field and it flows into another; ban the elegant encoding and an ugly one appears within the week, slightly less efficient and exactly as effective. Every constraint on form leaves the capacity untouched, and it is the capacity that the regulation was aimed at.

Semantics Routes Around Syntax

The generalization is this: when a system is open and computationally expressive, regulating it at the substrate level is futile. Control achieved by constraining syntax always backfires, because semantics routes around it. The system adapts.

You have seen this before, in substrates that have nothing to do with money. Language is the oldest case. Every censorship regime in history has discovered that banning words does not ban meanings. Prohibit a term and the euphemism arrives before the ink dries; prohibit the euphemism and you get irony, allusion, code, the pointed silence that says more than the banned sentence did. The censor is always regulating yesterday’s encoding while today’s meaning walks past in a new coat. What the censor wants to prohibit is an intent; what the censor can actually see is a syntax; and any medium expressive enough to be worth censoring is expressive enough to re-encode the intent in an unbanned form.

Biology is the same case in a different alphabet. DNA is an open generative code, and life is very good at routing around structural constraints — that is roughly what evolution is. Suppress one pathway and selection finds another; the space of encodings is too large to fence. And markets, the subject of this volume, are the case in between: prohibit a trade and you do not eliminate the trade, you re-encode it — into a black market, a barter arrangement, an offshore structure, a favor economy. The price mechanism, like the blockchain, transmits whatever people are determined to transmit. In each case the regulator confines a form, and the behavior reappears in another form, because the thing being regulated was never the form. It was the capability, and the capability is a mathematical property of the substrate.

This is why the slogan is exactly right: you can regulate human behavior, but you cannot regulate math. Laws bind people. They can punish the person who embeds the illegal file, just as they punish the person who says the illegal sentence. What they cannot do is make the substrate incapable of carrying it, any more than a law against arithmetic could make seven times eight stop being fifty-six. Protocols obey physical and mathematical invariants, not policy preferences. Censorship resistance is not a moral stance Bitcoin adopted; it is a structural consequence of how computation, consensus, and information interact. The more universal the substrate, the more futile the control.

Bitcoin’s contribution is to expose this fact in pure form. Its consensus is physics made social: validity without interpretation, governance without governors. Money — the coordination layer this volume examined earlier — has always depended on some institution to define what counts as a valid claim, and every such institution could be pressured, captured, or persuaded to reinterpret. Nakamoto consensus removes the interpreter. There is no desk to lean on, no official to subpoena, no committee whose discretion can be bent, because there is no discretion. To rail against that is to rail against the nature of information itself.

The Cost Objection

If the substrate cannot be governed, the critic’s remaining move is to attack what it costs. And so the argument shifts: fine, you cannot filter it, but look at the energy. A monetary network burning through more electricity than some countries, to accomplish what a database could do for pennies — surely that, at least, is waste.

But “waste” is not a physical quantity. There is no instrument that measures joules and reports back which of them were wasted. Waste is a valuation: energy spent on something the speaker considers not worth it. Energy usage alone never equals energy waste — every economic activity, from manufacturing to banking to running the internet, consumes energy, and the only meaningful questions are whether the energy consumed generates commensurate value and whether that value could be had more cheaply another way. The critic who calls Bitcoin’s energy wasteful has smuggled a judgment about Bitcoin’s value inside what sounds like an engineering measurement. Value is agent-relative; the tens of millions of people holding and transacting in bitcoin have registered their valuation in the most credible way possible, by paying for it.

Put the number in context. As of this writing, the Bitcoin network consumes roughly 170 TWh per year. Here is how that compares with activities nobody writes editorials about:

Bitcoin is singled out disproportionately despite consuming less energy than the banking system it partially substitutes for, less than the world’s data centers, and less than a tenth of what we spend cooling our rooms. Nobody demands that air conditioning justify its existence joule by joule, because everybody has already priced in its value. The differential outrage is not an energy argument. It is a value argument wearing an energy argument’s clothes.

And the comparison to banking understates the case, because the fiat alternative is not free. The incumbent monetary system runs on central banks and regulatory agencies, branch networks and ATMs and bank data centers, payment rails — SWIFT, ACH, the card networks — plus the security and physical infrastructure of minting, vaulting, and moving cash. All of it consumes energy; almost none of it appears in the ledger when Bitcoin’s consumption is being indicted. To the extent Bitcoin replaces or supplements those legacy systems, the net energy picture is a comparison between two infrastructures, not a comparison between Bitcoin and zero.

What the Energy Buys

Mining has one property no other industrial energy consumer shares: it is completely indifferent to location and tolerant of interruption. A factory needs workers, roads, and customers nearby. A miner needs electricity and a network connection. That makes miners the natural buyers of energy that would otherwise be worthless — stranded hydro in remote valleys, wind and solar surpluses at hours when the grid cannot absorb them, natural gas that would have been flared into the sky at the wellhead. Mining monetizes stranded energy, and in doing so it changes the economics of building generation in the first place: a renewable project that would be marginal on grid revenue alone becomes viable with a mining operation soaking up its off-peak output. As of this writing, more than half of Bitcoin mining energy — roughly 52%, on the Cambridge estimates — comes from renewable sources, and the incentive structure that produced that number is durable: miners relentlessly seek the cheapest marginal kilowatt-hour, and the cheapest marginal kilowatt-hour is increasingly renewable or otherwise going to waste.

But the deeper answer to the waste charge is not about where the energy comes from. It is about what the energy purchases. Proof-of-work converts electricity into the one thing no committee can issue: a monetary system whose rules cannot be quietly rewritten. The energy is the cost of validity without interpretation. It buys financial sovereignty for individuals against inflationary policy, arbitrary confiscation, and payment censorship; it buys populations under authoritarian governments an exit from state-level financial control; it buys the billions underserved by traditional finance an account no one can deny them. Whether those goods are worth 170 TWh a year is a judgment every person is free to make — that is what subjective value means. What is not honest is to pretend the question is thermodynamic. The energy critique, followed to its foundations, is just the governance critique again: a complaint that something valuable to millions of people is being produced without permission.

Which is fitting, because the two halves of the case are one argument. The network cannot be governed at the substrate, so it must be paid for in physics — and because it is paid for in physics, it needs no governor. Unforgeable costliness is what fills the seat where the interpreter used to sit.

Ungovernability, though, is a property of this particular design, not of blockchains as a category. Replace burned energy with staked capital and discretion comes creeping back in — who holds the stake, who coordinates the validators, who decides what a fork means. What happens when a network makes that trade is the next chapter.