The Dangers of CBDC: What Is Documented, What Is Speculative

How this page sorts the question

The question of CBDC dangers produces three kinds of statements. Most bad coverage mixes them into one. This page keeps them separate. A documented design claim is a commitment an issuing authority has made in writing. A stated position is an assertion a government has signed. A speculative harm is a scenario someone fears. No document stands behind it. Each section below carries its label. The label is the content.

The old version of this page failed exactly this test. It presented control and surveillance fears as fact about projects that exist. The research behind this rewrite found no primary source supporting those fears as facts of any live project. The rewrite carries that finding in the open.

The concern stated at the highest level

One government has put its concern in an executive order. Executive Order 14178 was published 31 January 2025 ^[3]. It states the US administration’s position. CBDCs threaten the stability of the financial system, individual privacy, and the sovereignty of the United States ^[3]. It directs measures toward prohibiting one in the US jurisdiction ^[3].

This page records that as what it is. The stated position of a US administration, from the primary text. It is not proof about what CBDCs do. A position’s weight is its author’s authority to hold it. The content remains the author’s statement, not a measurement. Readers who want the project-stage record can check the definition page. The US stands alone in the banked set with this posture.

What issuers have committed to in writing

The strongest evidence about CBDC privacy is the issuers’ own written commitments. Those are the documents a project would have to break.

The European Central Bank has made two commitments. The Eurosystem would not identify people based on their payments ^[1]. And personal transaction details from offline digital euro payments would be known only to the payer and the payee ^[1]. The offline privacy design is specific. It is published. It is checkable against the FAQ text.

The Bank of England’s commitments run to control. Neither the Bank nor the Government would be able to program digital pounds ^[2]. Nor restrict how users spent them ^[2]. Users themselves could program their own payments ^[2]. On privacy, the Bank’s position is legislative. Future laws on a digital pound would guarantee users’ privacy ^[2]. They would guarantee that neither the Bank nor the Government could control how the money is spent ^[2]. These are design commitments. They belong to a project not yet approved for issuance ^[2]. They are stated here with exactly that status.

Two further issuer statements inform the programmability debate. The Reserve Bank of India operates a sandbox. It tests interoperability, programmability, and new business models ^[4]. A documented testing fact. The People’s Bank of China describes e-CNY as convenient, safe, inclusive, and privacy-friendly ^[7]. That is the issuer’s characterization of its own project. Carried as such.

The documented structural concern: disintermediation

The concern with the deepest paper trail is not surveillance. It is disintermediation. What happens to commercial banks if holders move deposits en masse. Central bank literature treats this seriously as a design consideration. The design responses are visible in the projects themselves.

The mitigations have names. Distribution is intermediated. Banks and payment providers stay in the loop ^[1]. Accounts do not move to the central bank. And holding limits are proposed as a guardrail. The Bank of England’s rationale is on record. Limits would give the Bank time. Time to understand the instrument’s impact on the financial system. Time to avoid disruption ^[2]. This section states a documented concern and its documented mitigations. It does not rate the risk. The authorities publishing the designs do not rate it either.

The speculative harms, labeled

Then there is the class of claims the old page traded in. Governments could switch off your money. Track every purchase. Force balances to expire. Stated as mechanics of projects that exist, these claims have a verification problem. The research behind this page found no primary source supporting any of them as fact. Not about any live project. Not about any approved one. The launched projects publish wallets held at banks and authorized providers ^[5]. They publish exchange at par for notes and coins ^{[5] [6]}. The design projects publish privacy commitments ^{[1] [2]}.

None of that makes the fears irrational. A reader who distrusts commitments tied to future legislation has read the Bank of England’s framing correctly ^[2]. Its privacy guarantee rests on laws not yet passed. The point is narrower and stricter. A fear is a possibility statement. A design claim is a document. A page that prints the first as the second is not covering a debate. It is taking a side while pretending to inform.

Why the sorting matters

Every tier on this page can change. An issuer can break a commitment. The document it broke would be the evidence. An administration can change its position. The new order would be the record. A speculative harm can become documented. The day a primary source documents it. What cannot honestly change is the tier a claim sits in. Not without new evidence arriving. That is the discipline this page holds. Readers who want the same discipline applied to private issuers will find it in the stablecoin risks page. It sorts issuer risk the same way. By what documents exist.

Where this page sits

The definition page holds what a CBDC is and where projects stand. The comparison page sets the sovereign instrument against the private one. The regulation hub frames the regimes. The stablecoin intro defines the private instrument this page’s concerns are so often compared against.