Hillebrand on Central Bank Digital Currencies

“Central Bank Digital Currencies combine all three intervention types into a unified control mechanism. CBDCs are programmable money enabling comprehensive surveillance and control, not simple digital versions of existing currency.”

— Max Hillebrand, The Praxeology of Privacy Ch. 10 §10.5 “Central Bank Digital Currencies as Total Intervention”

What a CBDC Is

A central bank digital currency is a direct liability of the central bank held by the public, unlike the money most people use today — commercial-bank deposits, which are private liabilities the bank owes you. That distinction is the whole architecture. A euro in a bank account is a claim on a bank; a digital euro would be a claim on the European Central Bank itself, with the central bank as counterparty to every balance. Designs divide along two axes: retail (held by households and firms) versus wholesale (interbank settlement only), and account-based (identity-linked) versus token-based (bearer-like). The projects that alarm privacy advocates are retail, account-based systems — the digital euro, China’s e-CNY, and the scores of pilots the Bank for International Settlements tracks. Hillebrand’s chapter is about that design choice, not about digitization as such: money has been digital for decades, but a retail CBDC changes who holds the ledger and what the ledger can do.

The Three Interventions in One Stack

Hillebrand’s chapter maps the CBDC architecture onto Rothbard’s Power and Market trichotomy — the classification a dedicated article, Rothbard’s taxonomy of intervention, sets out in full. Autistic intervention is embedded in the medium itself — “CBDC rules can prohibit transactions directly through what amounts to autistic intervention embedded in the monetary infrastructure. The currency itself refuses to execute disfavored payments.” Binary intervention becomes free at point of use because the central bank is the counterparty to every balance: “the state extracts transaction data directly, and every economic act is reported instantly to the monetary authority.” Triangular intervention is preserved as the merchant-facing leg — the medium compels third parties to verify customer compliance before transacting. The three types collapse into one stack, which is why Hillebrand calls it total intervention: previous tools reached one leg at a time, and a CBDC welds all three into the settlement rail.

Programmability Is the Design, Not a Feature

The programmability layer is the load-bearing distinction from prior digital money. Hillebrand catalogues it directly: “Money can be programmed to expire, forcing spending and preventing saving; this implements negative interest rates without the zero lower bound. Money can be programmed to work only in specified regions… Money can refuse purchase categories… Money can be programmed to activate only when conditions are met: vaccination status, social credit score, tax compliance, political loyalty tests.” Holding caps, inactivity expiries, geographic fences, category blocks, and conditional release are not deployment options bolted onto a neutral payment rail — they are the rail. This is the sense in which a CBDC differs in kind, not degree, from a bank deposit or a stablecoin: those can be frozen or seized by a party acting on the money, but programmable central-bank money enforces policy from inside the unit itself, without an intermediary to petition or route around.

Not Sound Money

The verdict follows: “Money that can be surveilled and controlled is not sound money; it is a mechanism of intervention.” The framing trick Hillebrand objects to is treating the surveillance and control surfaces as incidental to digitization. They are constitutive of the design choice. A CBDC could replicate cash — anonymous, bearer-based, unrestricted — but “that central banks consistently choose surveillance-enabling designs reflects institutional incentives, not technical necessity.” A CBDC is thus the endpoint of fiat as an engineered system: where fiat already lets the issuer expand supply at will, a programmable CBDC lets it also dictate how, where, when, and by whom each unit may be spent.

The Case For, and Why Hillebrand Rejects It

The point is not that CBDC proponents have no argument. Central banks and their economists advance a real case: payment efficiency (instant, final settlement without card-network rents), financial inclusion (an account for the unbanked without a commercial intermediary), monetary-policy transmission (rates that reach households directly), resilience (a public option if private payment rails fail), and monetary sovereignty (a defense against private stablecoins and foreign CBDCs displacing the national unit). Retail-CBDC designs also typically promise privacy safeguards, holding caps to protect bank funding, and offline modes.

Hillebrand’s answer is not that these benefits are fake but that they are separable from the surveillance-and-control architecture, and yet never separated. Every efficiency or inclusion goal a CBDC serves could be met by a bearer-based, privacy-preserving design — cash already delivers inclusion and finality with no intermediary. That central banks reach instead for account-based, programmable, identity-linked systems is, on his reading, the tell: the “benefits” are the marketing, and the observation-and-control surface is the point. The honest disagreement, then, is empirical and institutional — will deployed CBDCs actually exercise the control their architecture permits? — and it is the same live contest that runs through the wiki’s treatment of the digital euro, where an explicit ban on “programmable money” sits atop plumbing that would enable it. Confidence here is medium: the architecture is documented, its exercise is a forecast.

Place in the Money Map

CBDCs are the newest instrument in the money-and-banking hub’s taxonomy of extraction, and the sharpest current front in the privacy-and-cryptography thread. They are the mirror image of the wiki’s sound-money project: where Monero and self-custody push financial privacy and control toward the individual, a retail CBDC pushes both toward the state. That symmetry is why the two topics meet here — the CBDC is what the parallel economy is built to route around.

See Also

• Rothbard’s Taxonomy of Intervention — the autistic/binary/triangular classification the CBDC folds into one stack
• Power and Market — Rothbard’s source for that typology
• Digital Euro — the concrete retail-CBDC case, with a “programmable money” ban atop enabling plumbing
• Fiat as an Engineered System — the policy-money order a CBDC completes
• The Praxeology of Privacy — book source (Ch. 10 §10.5)
• Max Hillebrand — author reference
• Praxeology of Privacy — Hillebrand’s broader frame the CBDC chapter applies
• State Power and Intervention — the broader intervention frame
• Money and Banking — the money hub CBDCs sit inside as the newest extraction instrument
• The Parallel Economy — the privacy stack built to route around programmable state money
• Surveillance Capitalism — the corporate analogue of the same observation logic
• Biopower
• Hayek on the Rule of Law
• Man, Economy, and State
• Privacy and Cryptography

Sources

• The Praxeology of Privacy: Economic Logic in Cypherpunk Implementation — Ch. 10 §10.5 “Central Bank Digital Currencies as Total Intervention” (autistic/binary/triangular mapping; the programmability catalogue; the “not sound money” verdict). CBDC-design specifics (retail/wholesale, account/token, direct-liability structure, the proponents’ efficiency/inclusion case, the digital-euro and e-CNY landscape) are widely documented common knowledge, not drawn from this source.