The American Non-Decision - Political Paralysis and Privacy
Learning Objectives
Explain why the US has not launched a CBDC despite Federal Reserve technical research and global competitor activity
Analyze the "strange bedfellows" coalition opposing CBDC from both conservative and progressive perspectives
Evaluate stablecoins as CBDC substitutes and their privacy implications compared to government-issued digital currency
Assess US legal and constitutional constraints unique to American CBDC development
Predict likely US digital currency trajectories including the probability of federal CBDC versus regulated stablecoin regime
China has deployed eCNY to hundreds of millions of users. Europe is legislating the Digital Euro. Smaller nations from Nigeria to the Bahamas have launched CBDCs. The United States—the world's largest economy and issuer of the global reserve currency—has done... studies.
The Federal Reserve has published research papers. The Treasury has expressed concerns about stablecoins. Congress has held hearings. But no CBDC pilot exists. No legislation has passed. No Federal Reserve CBDC wallet is available to American citizens.
This non-decision is itself a decision—and it reveals something important about privacy.
Unlike China (where the CCP decided) or Europe (where technocrats are negotiating), America's CBDC fate is contested in democratic politics. And in that contestation, privacy arguments have found unusual potency, uniting libertarian conservatives worried about government surveillance with progressive advocates concerned about marginalized communities.
This lesson examines why America has produced paralysis rather than a CBDC—and what this reveals about the relationship between democracy, privacy, and digital currency.
What the Fed Has Done
FEDERAL RESERVE ACTIVITY:
RESEARCH:
├─ Multiple working papers on CBDC design
├─ Boston Fed + MIT: "Project Hamilton" technical research
├─ Analysis of privacy-preserving architectures
├─ International CBDC coordination (BIS, etc.)
└─ Staff expertise development
PROJECT HAMILTON FINDINGS (2022):
├─ Demonstrated 1.7M TPS throughput possible
├─ Explored privacy-preserving options
├─ Did NOT recommend specific design
├─ Did NOT recommend implementation
└─ Technical capability proven, policy question open
OFFICIAL POSITION (Fed Chair Powell):
"We would need clear support from the executive branch
and from Congress, ideally in the form of a specific
authorizing law."
FED'S SELF-LIMITATION:
├─ Will not proceed without authorization
├─ Will not advocate for CBDC
├─ Sees role as technical analysis only
├─ Defers policy decision to elected officials
└─ Institutional caution dominates
Executive Branch Stance
TREASURY DEPARTMENT:
Biden Administration (2021-2025):
├─ Executive Order 14067 (March 2022)
├─ Directed CBDC research
├─ Emphasized financial inclusion
├─ Privacy mentioned but not prioritized
├─ No implementation decision made
└─ Studies but no action
TREASURY CONCERNS:
├─ Stablecoin risks to financial stability
├─ Dollar dominance in digital era
├─ Financial inclusion opportunities
├─ Privacy as consideration (not priority)
└─ Regulatory framework gaps
ACTUAL OUTCOME:
├─ Multiple reports published
├─ No legislation proposed
├─ No clear recommendation
├─ Effectively: Kick the can
└─ No political will to decide
TRUMP ADMINISTRATION (2017-2021, 2025-):
├─ No CBDC priority in first term
├─ Second term: Explicitly opposed
├─ Executive Order banning CBDC development
├─ Pro-cryptocurrency positioning
└─ "Financial freedom" framing
Legislative Landscape
CONGRESSIONAL POSITIONS:
REPUBLICAN OPPOSITION (majority position):
├─ "CBDC is government surveillance"
├─ "Threat to financial freedom"
├─ Anti-Fed sentiment (some members)
├─ Pro-cryptocurrency positioning
├─ Legislation to BAN CBDC proposed
- CBDC Anti-Surveillance State Act (2023, 2024)
- "No Digital Dollar" provisions
- State-level CBDC bans (Florida, etc.)
DEMOCRATIC AMBIVALENCE:
├─ Some interest in financial inclusion
├─ Some concern about surveillance
├─ Some want to compete with China
├─ No unified position
├─ Progressive wing: Privacy concerns
├─ Establishment wing: Dollar competition concerns
- No Democratic champion for CBDC
- Privacy concerns cross party lines
- Financial inclusion arguments haven't mobilized support
BIPARTISAN STABLECOIN INTEREST:
├─ More consensus on regulating stablecoins
├─ Less controversy than CBDC
├─ Industry support (Coinbase, Circle)
├─ Possible path forward
└─ Multiple bills proposed
Right-Wing CBDC Opposition
CONSERVATIVE PRIVACY FRAMING:
CORE ARGUMENT:
"A CBDC would give government unprecedented power
to surveil and control citizens' financial lives."
SPECIFIC CONCERNS:
GOVERNMENT OVERREACH
PROGRAMMABLE CONTROL
FINANCIAL FREEDOM
FEDERAL RESERVE SKEPTICISM
- Sen. Ted Cruz (R-TX): CBDC ban legislation
- Rep. Tom Emmer (R-MN): Anti-CBDC advocacy
- Ron Paul: Consistent Fed/CBDC opposition
- Heritage Foundation: Policy papers opposing
- Cato Institute: Libertarian opposition
POLITICAL POSITIONING:
CBDC opposition = defending freedom from government
Aligns with anti-establishment conservative sentiment
Cryptocurrency = freedom; CBDC = control
```
Left-Wing CBDC Concerns
PROGRESSIVE PRIVACY FRAMING:
CORE ARGUMENT:
"CBDC surveillance would disproportionately
harm marginalized communities already
over-policed and over-surveilled."
SPECIFIC CONCERNS:
CIVIL LIBERTIES
MARGINALIZED COMMUNITIES
REPRODUCTIVE RIGHTS
LABOR ORGANIZING
- ACLU: Civil liberties concerns
- Electronic Frontier Foundation: Surveillance critique
- Some progressive Democrats: Privacy caucus
- Reproductive rights organizations: Post-Dobbs concerns
POLITICAL POSITIONING:
CBDC opposition = protecting marginalized from surveillance
Aligns with civil liberties left
Cryptocurrency complicated (environmental concerns)
```
Unlikely Alliance Analysis
COALITION DYNAMICS:
WHY IT WORKS:
├─ Privacy concern transcends left/right
├─ Distrust of government transcends left/right
├─ Different reasons, same opposition
├─ Creates blocking coalition in Congress
└─ Neither party can override
- Suspicion of centralized financial power
- Historical examples of targeting (both cite)
- Desire to preserve cash or cash-like options
- Fear of programmable money
- Distrust of current institutions
- View of cryptocurrency (freedom vs. environmental harm)
- Solutions preferred (deregulation vs. regulation)
- Other policy priorities
- Long-term vision for financial system
COALITION EFFECTIVENESS:
├─ Successfully blocked CBDC legislation
├─ Created political cost for CBDC advocacy
├─ Normalized privacy concerns in CBDC debate
├─ Made "CBDC is surveillance" mainstream argument
└─ Paralysis is the coalition's victory
LIMITS:
├─ Can block but not create
├─ No consensus on alternative
├─ Stablecoin regulation may split coalition
├─ Crisis could override concerns
└─ Coalition is negative, not positive
Bank Lobby Against CBDC
BANKING INDUSTRY POSITION:
STATED CONCERNS:
├─ "CBDC could cause bank runs"
├─ "Disintermediation threatens financial stability"
├─ "Current system works well"
├─ "Innovation should come from private sector"
└─ Privacy mentioned but not emphasized
ACTUAL CONCERNS:
├─ Loss of deposits to Fed accounts
├─ Reduced lending capacity
├─ Customer relationship disruption
├─ Competitive threat to core business
└─ Profit impact from digital dollar
LOBBYING ACTIVITY:
├─ American Bankers Association: Skeptical positions
├─ Individual bank lobbying
├─ Think tank funding (some)
├─ Congressional relationships
└─ Significant influence
PRIVACY ARGUMENT USE:
Banks use privacy arguments opportunistically
"We protect customer privacy better than government would"
Not their primary concern but useful framing
Aligns with anti-CBDC coalition
Crypto's Mixed Stance
CRYPTOCURRENCY INDUSTRY:
ANTI-CBDC ARGUMENTS:
├─ "CBDCs are surveillance coins"
├─ "Bitcoin/crypto is real digital freedom"
├─ "Government digital money is competition"
├─ Privacy-preserving alternatives exist
└─ Decentralization > centralization
PRO-STABLECOIN ARGUMENTS:
├─ "Regulate us, don't create CBDC"
├─ "Private stablecoins can serve same function"
├─ "Innovation should come from private sector"
└─ Lobbying for stablecoin framework
- Coinbase: Anti-CBDC, pro-stablecoin regulation
- Circle (USDC): Pro-stablecoin regulation
- Tether: Less engaged in US politics
- Bitcoin maximalists: Anti-CBDC, anti-stablecoin too
INDUSTRY LOBBYING:
├─ Significant and growing
├─ Campaign contributions both parties
├─ Think tank funding
├─ Grassroots mobilization
└─ Increasingly influential in DC
PRIVACY POSITIONING:
Some genuinely care (Bitcoin ethos)
Some use opportunistically (business interest)
Complicates clean "privacy coalition" narrative
Technology Company Positions
BIG TECH STANCE:
GENERALLY QUIET:
├─ Meta (Facebook): Burned by Libra/Diem failure
├─ Google: No public CBDC position
├─ Apple: Focus on Apple Pay, not currency
├─ Amazon: No significant engagement
└─ Learned: Digital currency is political minefield
WHY QUIET:
├─ Libra backlash taught lesson
├─ Don't want to be target
├─ Regulatory relations more important
├─ Let others take political risk
└─ Wait and see positioning
POTENTIAL INTERESTS:
├─ Payment system access
├─ Data from transactions
├─ Infrastructure provision
├─ Competitive dynamics
└─ But not worth political cost now
- Different privacy concerns
- Corporate vs. government surveillance
- Data monetization questions
- Antitrust implications
---
How Stablecoins Function as Digital Dollars
STABLECOIN REALITY:
WHAT THEY ARE:
├─ Private-issued tokens
├─ Pegged to dollar (supposedly 1:1)
├─ Backed by reserves (quality varies)
├─ Operate on various blockchains
└─ Effectively private digital dollars
- Tether (USDT): ~$100B+ market cap
- Circle (USDC): ~$30B+ market cap
- Others: Smaller but growing
USE CASES:
├─ Crypto trading pairs
├─ Cross-border payments
├─ DeFi applications
├─ Remittances
└─ Some commercial payments
SCALE:
├─ Combined market cap: $150B+
├─ Daily transaction volume: Billions
├─ Users: Tens of millions globally
├─ Growing despite regulatory uncertainty
└─ De facto private CBDC already exists
Privacy Comparison
STABLECOIN VS. CBDC PRIVACY:
STABLECOIN PRIVACY:
On-Chain Visibility:
├─ Blockchain transactions are public
├─ Pseudonymous (addresses, not names)
├─ Chain analysis can link addresses
├─ Not anonymous, but not named either
Issuer Visibility:
├─ Circle/Tether know major holders
├─ KYC required for direct redemption
├─ But most users don't interact with issuer
└─ Indirect holding through exchanges
Law Enforcement Access:
├─ Subpoena issuer for records
├─ Blockchain analysis firms assist
├─ Less real-time than CBDC would be
├─ But not truly private either
HYPOTHETICAL CBDC PRIVACY:
Likely Design (given US politics):
├─ Full identity linkage
├─ Complete transaction visibility
├─ Real-time monitoring capability
├─ Programmability possible
└─ Less private than stablecoins currently
COMPARISON:
Stablecoins currently: Pseudonymous, some friction to deanonymize
Likely US CBDC: Fully identified, complete government visibility
Stablecoins offer MORE privacy than likely CBDC design
This is part of their appeal
```
Likely Stablecoin Regulation
REGULATORY PATH:
LIKELY FRAMEWORK:
├─ Federal licensing for issuers
├─ Reserve requirements (Treasury/cash equivalents)
├─ Regular audits and disclosures
├─ Consumer protection requirements
├─ Bank-like supervision
└─ AML/KYC requirements (already exist)
WHAT REGULATION WOULD REQUIRE:
├─ Identity verification for large users
├─ Suspicious activity reporting
├─ Records available to law enforcement
├─ Possibly: Transaction monitoring
└─ Reduced privacy from current state
POLITICAL DYNAMICS:
├─ More bipartisan support than CBDC
├─ Industry prefers to CBDC
├─ Banks can participate (issue own stablecoins)
├─ Less politically charged than CBDC
└─ Path of least resistance
PROBABILITY ASSESSMENT:
Federal stablecoin framework: 70% by 2027
Federal CBDC: 25% by 2030
Neither (continued ambiguity): 30% ongoing
[Note: Probabilities don't sum to 100% due to sequential/conditional nature]
US CBDC Political Economy
STAKEHOLDER MATRIX:
| SUPPORT CBDC | OPPOSE CBDC | NEUTRAL
--------------------|--------------|-------------|----------
Federal Reserve | No | No | YES (defer)
Treasury | Mild | No | Lean support
Republicans | No | YES (strong)| No
Democrats | Mixed | Mixed | YES
Banks | No | YES | No
Crypto Industry | No | YES | No
Privacy Advocates | No | YES | No
Big Tech | No | No | YES (quiet)
General Public | No | No | YES (unaware)
COALITION ANALYSIS:
Pro-CBDC: Treasury (mild), some Democrats
Anti-CBDC: Republicans, banks, crypto, privacy advocates
Neutral: Fed (deliberately), Big Tech (strategically), public
RESULT: Anti-CBDC coalition dominates
No political path for CBDC currently
Would require major shift in dynamics
US Digital Currency Futures
SCENARIO 1: STABLECOIN REGIME (45% probability)
Timeline: 2025-2028
Outcome: Federal stablecoin framework passes
Privacy: Moderate (regulated but not CBDC-level)
Path: Bipartisan bill, industry support, Fed passive
Implication: No government CBDC, private digital dollars
SCENARIO 2: CONTINUED PARALYSIS (30% probability)
Timeline: Ongoing
Outcome: No comprehensive framework
Privacy: Status quo (varies by product)
Path: Political gridlock continues
Implication: Patchwork regulation, legal uncertainty
SCENARIO 3: CBDC DEVELOPMENT (15% probability)
Timeline: 2028-2032 (if at all)
Outcome: Federal CBDC authorized
Privacy: Unknown (would be contested)
Path: Requires Democratic trifecta + political will
Implication: Major shift from current trajectory
SCENARIO 4: STATE-LEVEL ACTION (10% probability)
Timeline: 2025-2030
Outcome: State-issued digital currencies
Privacy: Varies by state
Path: Some states experiment, constitutional questions
Implication: Fragmented landscape
MOST LIKELY: Stablecoin regime with no federal CBDC
Privacy outcome: Better than full CBDC surveillance
Worse than privacy-preserving CBDC design
```
Catalysts for Different Outcomes
WHAT COULD PRODUCE CBDC:
- Dollar under serious threat
- Flight to safety overwhelms banks
- Fed needs direct consumer access
- Emergency powers invoked
- eCNY gains international traction
- Dollar dominance threatened
- National security framing
- Bipartisan "compete with China" moment
- Major stablecoin fails (Tether?)
- Consumer harm widespread
- Government alternative demanded
- "Only fed can be trusted" narrative
- Privacy coalition fractures
- New arguments gain traction
- Different administration priority
- Congressional composition shift
WHAT COULD STRENGTHEN STABLECOIN PATH:
- Successful regulation elsewhere
- Industry self-regulation success
- Consumer adoption growth
- Bank participation (their own stablecoins)
- Continued CBDC political toxicity
WHAT COULD PRODUCE TRUE PARALYSIS:
- Continued partisan gridlock
- No crisis to force action
- Status quo "good enough"
- Competing priorities dominate
Privacy Implications of Likely Trajectory
IF STABLECOIN REGIME EMERGES:
PRIVACY CHARACTERISTICS:
├─ Pseudonymous baseline (blockchain)
├─ KYC requirements for larger users
├─ SAR reporting (suspicious activity)
├─ Law enforcement access via subpoena
├─ No real-time government visibility
└─ Better than CBDC, worse than cash
COMPARED TO ALTERNATIVES:
Better than: eCNY (much better)
Better than: Likely US CBDC design
Comparable to: Current banking (maybe slightly better)
Worse than: Physical cash
Worse than: Privacy-preserving CBDC
IF NO ACTION (CONTINUED PARALYSIS):
Current landscape persists:
├─ Stablecoins lightly regulated (state level)
├─ Crypto pseudonymity preserved
├─ Cash remains option
├─ No comprehensive surveillance
└─ Privacy by regulatory gap
RISK:
├─ Enforcement actions ad hoc
├─ Legal uncertainty deters legitimate use
├─ Offshore alternatives more attractive
├─ Consumer protection gaps
└─ Not sustainable long-term
```
Why Paralysis Produces Privacy
AMERICAN PRIVACY PARADOX:
OBSERVATION:
US has weak legal privacy protection (third-party doctrine)
But strong de facto privacy protection (no CBDC)
Democratic contestation blocking surveillance infrastructure
MECHANISM:
├─ Weak law → Surveillance legal IF infrastructure exists
├─ But infrastructure requires political authorization
├─ Political authorization blocked by coalition
├─ Result: No infrastructure, no surveillance
└─ Privacy protected by gridlock, not law
CONTRAST WITH EUROPE:
EU has strong legal privacy protection
But Digital Euro will have surveillance capability (PSP visibility)
Law constrains but doesn't prevent infrastructure
Better law, maybe worse outcome?
1. Legal protection necessary but insufficient
2. Political contestation matters
3. Democracy can protect privacy (through blocking)
4. But democracy can't build privacy-respecting alternatives
5. Paralysis is not sustainable solution
HONEST ASSESSMENT:
US protected by dysfunction, not design
Not a model to emulate
Works until it doesn't
Crisis would override gridlock
✅ No US CBDC will launch without congressional authorization. The Federal Reserve has explicitly stated it won't proceed without clear legislative authority. The Fed's institutional caution creates a hard constraint.
✅ A cross-partisan coalition effectively blocks CBDC. Conservative anti-government sentiment and progressive civil liberties concerns create unusual alliance that has prevented CBDC advancement in Congress.
✅ Stablecoin regulation is more politically feasible. More bipartisan support exists for regulating private stablecoins than creating government digital currency. This is the path of least resistance.
✅ Current stablecoins offer more privacy than likely US CBDC would. Pseudonymous blockchain transactions provide more privacy than the fully-identified, real-time-visible design a US CBDC would likely have given surveillance state precedents.
⚠️ Whether the anti-CBDC coalition will hold. Crisis, political realignment, or changed circumstances could fracture the coalition. Its durability is uncertain.
⚠️ What form stablecoin regulation will take. Privacy implications depend on specific requirements. Heavy-handed regulation could reduce privacy; lighter touch could preserve it.
⚠️ How long paralysis can last. If US falls behind on digital currency infrastructure, pressure for action will grow. Status quo may not be sustainable.
⚠️ What privacy features any eventual CBDC would have. If a CBDC is ever authorized, its privacy architecture would be heavily contested. Outcome impossible to predict now.
🔴 US is protecting privacy through dysfunction, not design. The absence of CBDC preserves privacy, but this isn't a deliberate privacy-protecting policy—it's gridlock. Not sustainable or replicable.
🔴 No pathway to privacy-respecting digital currency infrastructure. The coalition can block but not build. There's no political path to a genuinely privacy-preserving digital currency option in the US.
🔴 Crisis could override all constraints. Financial crisis, national security event, or major stablecoin failure could create emergency conditions where surveillance infrastructure is rapidly authorized.
🔴 Third-party doctrine means any CBDC would have weak legal protection. If a CBDC is ever built, existing constitutional doctrine suggests minimal privacy protection for transactions. Architecture would be the only protection.
The United States has stumbled into privacy protection through political dysfunction rather than deliberate policy. The anti-CBDC coalition, uniting libertarians and civil libertarians, has effectively blocked surveillance infrastructure that legal doctrine would permit.
This is not a model to celebrate. Privacy protected by gridlock is fragile—vulnerable to crisis, political realignment, or changed circumstances. The US has neither the surveillance infrastructure of China nor the privacy-protecting legal framework of Europe. It has paralysis.
For privacy advocates, this creates an odd strategic situation: the absence of a decision is currently the best achievable outcome, but it's not a victory. The coalition can only block, not build. A genuinely privacy-respecting digital dollar remains politically impossible.
Assignment: Model three scenarios for US digital currency development with privacy implications of each.
Requirements:
Part 1: Scenario Construction (40%)
Develop three scenarios with 5-year time horizons:
What would have to happen for this to occur?
What would the likely architecture be?
What privacy features would it have?
Who would support/oppose?
Probability assessment with justification
What regulation would pass?
What privacy requirements would be imposed?
How would this differ from CBDC?
Who would support/oppose?
Probability assessment with justification
What prevents resolution?
What would the landscape look like?
What privacy implications?
Is this sustainable?
Probability assessment with justification
What events could trigger Scenario A (CBDC)?
What events could trigger Scenario B (Stablecoin)?
What maintains Scenario C (Paralysis)?
How should investors/analysts monitor for shifts?
Part 3: Privacy Assessment (25%)
Who has transaction visibility?
What legal protections exist?
What technical privacy features?
Compare to status quo, eCNY, Digital Euro
Overall privacy rating (1-10 scale with justification)
How should privacy-conscious users prepare?
What positioning makes sense for each scenario?
What hedging strategy across scenarios?
What would change your probability assessments?
Quality of scenario construction (30%)
Realism of trigger event analysis (20%)
Rigor of privacy assessment (25%)
Thoughtfulness of implications (15%)
Integration of lesson concepts (10%)
Time investment: 4-5 hours
Value: Scenario analysis is essential for navigating uncertain futures. This framework applies to any jurisdiction's digital currency trajectory.
Submission format: Document of 2,500-3,000 words
Knowledge Check
Question 1 of 5(Tests Coalition Understanding):
- Federal Reserve, "Money and Payments: The U.S. Dollar in the Age of Digital Transformation" (2022)
- Boston Fed & MIT, "Project Hamilton" technical papers
- Fed Chair Powell testimonies and speeches on CBDC
- CBDC Anti-Surveillance State Act (multiple versions)
- House Financial Services Committee hearings on CBDC
- Senate Banking Committee testimonies
- Brookings Institution, "The Politics of Central Bank Digital Currency"
- Atlantic Council CBDC Tracker (US section)
- Cato Institute, "Should the Federal Reserve Create a Digital Currency?"
- American Bankers Association CBDC positions
- Chamber of Digital Commerce advocacy
- Coinbase, Circle policy positions
- ACLU on CBDC surveillance concerns
- Electronic Frontier Foundation digital currency positions
- Heritage Foundation, "Why a CBDC Would Be Bad for America"
For Next Lesson:
In Lesson 9, we examine emerging market CBDC approaches, where the balance tips dramatically toward financial inclusion over privacy. Nigeria, India, Brazil, and others present different trade-offs and serve as test cases for how developing nations navigate CBDC privacy challenges.
End of Lesson 8
Total words: ~6,300
Estimated completion time: 55 minutes reading + 4-5 hours for deliverable
Key Takeaways
No US CBDC will launch without congressional authorization, creating a political bottleneck.
The Federal Reserve's institutional caution means CBDC requires legislative action, giving Congress (and its gridlock) effective veto power.
A strange-bedfellows coalition unites libertarian conservatives and progressive civil libertarians against CBDC.
Different reasons (anti-government vs. protecting marginalized) but same conclusion: CBDC is surveillance, oppose it.
Stablecoins are emerging as de facto CBDC substitute with better privacy.
Private digital dollars (USDC, USDT) offer pseudonymous transactions without real-time government visibility—more privacy than a US CBDC would likely provide.
US privacy is protected by political dysfunction, not deliberate design.
The absence of CBDC preserves privacy, but this is gridlock, not policy. It's fragile and doesn't produce privacy-respecting alternatives.
Most likely trajectory: regulated stablecoin regime without federal CBDC.
45% probability of stablecoin framework by 2028; only 15% probability of federal CBDC by 2032. Privacy outcome: moderate, better than CBDC, worse than cash. ---