Emerging Market Models - Financial Inclusion vs. Surveillance

Legitimate Inclusion Arguments

FINANCIAL INCLUSION REALITY:

UNBANKED POPULATIONS:
├─ Sub-Saharan Africa: ~57% unbanked
├─ South Asia: ~30% unbanked
├─ Latin America: ~45% unbanked
├─ Middle East/North Africa: ~50% unbanked
└─ Global: ~1.4 billion adults

WHY UNBANKED:
├─ Lack of documentation (no ID, no address proof)
├─ Geographic distance (no bank branches)
├─ Cost barriers (minimum balances, fees)
├─ Distrust of institutions
├─ Informal employment (no payroll access)
└─ Cultural/gender factors

CBDC POTENTIAL:
├─ Mobile phone as wallet (phone penetration > bank penetration)
├─ Lower KYC requirements (tiered system)
├─ No minimum balance requirements
├─ Direct government payment receipt
├─ Lower transaction costs than cash
└─ Geographic accessibility via mobile network

Cash Economy Challenges

CASH-DOMINANT ECONOMY PROBLEMS:

COSTS:
├─ Printing and distribution: 1-2% of GDP in some nations
├─ Cash handling for businesses: Significant labor cost
├─ Security risks: Theft, counterfeit
├─ Wear and replacement: Constant expense
└─ Informal economy: Lost tax revenue

MEASUREMENT:
├─ Economic statistics unreliable
├─ Policy making based on partial data
├─ Crisis response hampered
├─ Development planning difficult
└─ International comparison complicated

POLICY TRANSMISSION:
├─ Interest rate policy ineffective (cash outside banking)
├─ Stimulus difficult to target
├─ Subsidies leak to non-intended recipients
├─ Monetary policy channels broken
└─ Central bank effectiveness limited

CBDC PROMISE:
├─ Reduced cash handling costs
├─ Better economic data
├─ Improved policy transmission
├─ Targeted subsidy delivery
└─ Formalization of economy

Political Economy of Emerging Market CBDCs

WHY PRIVACY ISN'T PRIORITY:

- "Helping the unbanked" is unassailable
- Privacy concerns seem like rich-world problem
- International development community emphasizes inclusion
- Easy political messaging

- Informal economy = lost revenue
- CBDC enables formalization
- Surveillance is feature, not bug
- Finance ministries drive design

- Privacy advocates less resourced
- Civil society weaker
- Middle class smaller (who cares most about privacy)
- No political cost for surveillance

- IMF/World Bank emphasize formal economy
- Technical assistance often surveillance-oriented
- China offers CBDC assistance (with strings)
- Privacy not donor priority

- Courts less independent
- Press less free
- Opposition parties weaker
- Abuse easier to get away with

---

eNaira Overview

LAUNCH:
├─ October 2021 (one of first African CBDCs)
├─ Central Bank of Nigeria (CBN) initiative
├─ Ambitious adoption targets
├─ Significant government promotion
└─ Intended to increase financial inclusion

ADOPTION REALITY (2024):
├─ ~10 million wallets created (vs. 200M+ population)
├─ Low active usage rates
├─ Transaction volumes disappointing
├─ Most wallets inactive after creation
└─ Largely failed to achieve inclusion goals

WHY ADOPTION FAILED:
├─ Existing mobile money (Paga, OPay) more trusted
├─ User experience inferior
├─ Merchant acceptance limited
├─ Internet connectivity required
├─ Trust deficit with CBN after cash restrictions
└─ No compelling use case vs. alternatives
```

Coercive Adoption Attempt

NAIRA CASH RESTRICTION (2022-2023):

WHAT HAPPENED:
├─ CBN redesigned naira notes
├─ Old notes demonetized rapidly
├─ Cash withdrawal limits imposed
├─ ATM access restricted
├─ Stated goal: Force digital adoption

POPULATION IMPACT:
├─ Cash shortages nationwide
├─ Businesses couldn't operate
├─ Protests and civil unrest
├─ Supreme Court intervention
├─ Disproportionate impact on poor/rural
└─ Humanitarian crisis elements

OUTCOME:
├─ Policy partially reversed
├─ eNaira adoption barely increased
├─ Public trust in CBN damaged
├─ Informal economy persisted
├─ Cash demand returned when available
└─ Demonstrated: Can't force CBDC adoption

- Coercive measures backfire
- Trust matters more than mandate
- Poor population bears cost
- Digital alternatives must be better, not just available

eNaira Privacy Assessment

eNAIRA PRIVACY ARCHITECTURE:

IDENTITY REQUIREMENTS:
├─ Tier 1: Phone + NIN (National ID) required
├─ Tier 2: Bank verification required
├─ Tier 3: Full KYC required
├─ No truly anonymous tier
└─ All linked to biometric national ID

CBN VISIBILITY:
├─ Complete transaction visibility
├─ Real-time monitoring capability
├─ No privacy layer in architecture
├─ Central database of all transactions
└─ Similar to eCNY model

INSTITUTIONAL CONSTRAINTS:
├─ Nigerian courts: Some independence but limited
├─ Privacy law: Weak (NDPR exists but poorly enforced)
├─ CBN independence: Politicized institution
├─ History: Currency manipulation, capital controls
└─ Risk level: HIGH for surveillance abuse

HONEST ASSESSMENT:
eNaira = Full surveillance architecture
No meaningful privacy protection
Weak institutional constraints on abuse
Trust deficit makes adoption unlikely anyway

---

Digital Rupee Overview

LAUNCH:
├─ Wholesale pilot: November 2022
├─ Retail pilot: December 2022
├─ Reserve Bank of India (RBI) initiative
├─ Cautious, phased approach
└─ Still in pilot phase (2024)

PILOT CHARACTERISTICS:
├─ Limited cities (initially 4, expanded)
├─ Limited banks participating
├─ Limited use cases
├─ Low transaction volumes
├─ Learning-focused, not deployment-focused

SCALE CONSIDERATIONS:
├─ 1.4 billion population
├─ Massive existing digital payment infrastructure (UPI)
├─ Diverse financial inclusion landscape
├─ Complex regulatory environment
└─ Scale deployment would be unprecedented

COMPETITIVE CONTEXT:
├─ UPI already successful (billions of transactions monthly)
├─ Digital rupee must compete with working system
├─ Unclear value proposition vs. UPI
├─ May become interbank settlement tool
└─ Retail adoption uncertain
```

India's Existing Digital Payment Success

UPI (UNIFIED PAYMENTS INTERFACE):

WHAT IT IS:
├─ Real-time interbank payment system
├─ Mobile-phone based
├─ Near-zero transaction cost
├─ Massive adoption (10B+ transactions/month)
└─ Global model for payment innovation

PRIVACY CHARACTERISTICS:
├─ Bank account based (full bank visibility)
├─ Government can access records
├─ Not anonymous
├─ But: Decentralized across banks
└─ Similar to card payments elsewhere

DIGITAL RUPEE COMPARISON:
├─ Both: Full identity linkage
├─ Both: Transaction records exist
├─ Difference: CBDC could be more centralized
├─ UPI: Records distributed across banks
├─ Digital Rupee: Could centralize at RBI
└─ Privacy implications: Similar or worse

KEY INSIGHT:
India already has digital payments (not anonymous)
Digital rupee doesn't change privacy landscape much
But COULD centralize visibility at RBI vs. distributed banks
Incremental surveillance risk, not transformation
```

Digital Rupee Privacy Analysis

DIGITAL RUPEE PRIVACY ARCHITECTURE:

DESIGN APPROACH:
├─ Token-based (claimed)
├─ Bank wallet distribution
├─ RBI as issuer
├─ Tiered wallets proposed
└─ Offline payments mentioned

STATED PRIVACY FEATURES:
├─ "Cash-like anonymity" for small transactions (claimed)
├─ Tiered identity requirements
├─ Offline capability (limited)
└─ But: Details remain vague

INSTITUTIONAL CONTEXT:
├─ India: World's largest democracy
├─ Independent judiciary (somewhat)
├─ Free press (somewhat)
├─ BUT: Increasing executive power
├─ BUT: Internet shutdowns common
├─ BUT: Surveillance capacity growing (Aadhaar)
├─ Risk level: MEDIUM-HIGH

AADHAAR INTEGRATION CONCERN:
├─ Aadhaar = biometric national ID
├─ Already linked to many services
├─ Digital rupee + Aadhaar = comprehensive tracking
├─ Privacy advocates concerned
└─ Surveillance infrastructure grows

HONEST ASSESSMENT:
Details still emerging from pilot
Architecture suggests surveillance capability
Institutional constraints weakening
Better than Nigeria, worse than Europe

---

DREX Overview

LAUNCH:
├─ Pilot: 2023-2024
├─ Banco Central do Brasil initiative
├─ Built on Hyperledger Besu (private Ethereum)
├─ Focus: Programmability and smart contracts
└─ Tokenization of financial assets

UNIQUE APPROACH:
├─ Not primarily retail CBDC
├─ Platform for tokenized assets
├─ DeFi-like capabilities (controlled)
├─ Interoperability focus
└─ More wholesale/institutional initially

USE CASES TARGETED:
├─ Tokenized government bonds
├─ Programmable corporate payments
├─ Collateral management
├─ Smart contract settlements
└─ NOT primarily consumer payments
```

DREX Privacy Analysis

DREX PRIVACY CHARACTERISTICS:

ARCHITECTURE:
├─ Private blockchain (permissioned)
├─ Validators controlled by BCB
├─ Transaction visibility to validators
├─ Enterprise focus initially
└─ Retail implications unclear

PROGRAMMABILITY IMPLICATIONS:
├─ Smart contract capability = control capability
├─ Conditional payments possible
├─ Automatic enforcement possible
├─ Privacy implications of programmability
└─ Depends on how capabilities used

INSTITUTIONAL CONTEXT:
├─ Brazil: Democracy with strong institutions
├─ Independent judiciary
├─ Free press
├─ BUT: Political polarization
├─ BUT: History of inflation/currency manipulation
├─ Risk level: MEDIUM

PRIVACY ASSESSMENT:
Wholesale focus limits consumer privacy impact
But retail expansion possible
Programmability creates control infrastructure
Better institutional constraints than most emerging markets

---

Recognizing the Pattern

PATTERN IDENTIFICATION:

STEP 1: INCLUSION FRAMING
"We need CBDC for financial inclusion"
"Helping the unbanked is our priority"
"Development requires digital payments"

STEP 2: SURVEILLANCE ARCHITECTURE
Built with complete visibility
No privacy-preserving technology
"Compliance by design"

STEP 3: JUSTIFICATION
"We need visibility to prevent crime"
"Tax compliance requires transparency"
"Fraud prevention demands monitoring"

STEP 4: IMPLEMENTATION
Full surveillance deployed
Privacy never actually prioritized
Inclusion remains incomplete
Surveillance capability permanent

- Inclusion talked about extensively
- Privacy barely mentioned
- Architecture reveals priorities
- Same pattern across jurisdictions

HONEST ASSESSMENT:
Inclusion is real goal for some
Surveillance is primary goal for others
Architecture reveals true priority
Inclusion arguments provide political cover

What Determines Abuse Risk

INSTITUTIONAL CONSTRAINT FACTORS:

JUDICIAL INDEPENDENCE:
├─ Can courts review surveillance?
├─ Will judges challenge government?
├─ Are rulings enforced?
└─ Score: High/Medium/Low

PRESS FREEDOM:
├─ Can media expose abuse?
├─ Are journalists protected?
├─ Does exposure create accountability?
└─ Score: High/Medium/Low

POLITICAL COMPETITION:
├─ Is there viable opposition?
├─ Can opposition protect constituents?
├─ Is surveillance a political issue?
└─ Score: High/Medium/Low

CIVIL SOCIETY:
├─ Are advocacy groups active?
├─ Can they influence policy?
├─ Is there privacy constituency?
└─ Score: High/Medium/Low

LEGAL FRAMEWORK:
├─ Does privacy law exist?
├─ Is it enforced?
├─ Are remedies available?
└─ Score: High/Medium/Low

OVERALL ASSESSMENT:
High constraints: Surveillance limited even if capability exists
Medium constraints: Abuse possible but checkable
Low constraints: Surveillance likely to be abused

Country Assessments

INSTITUTIONAL CONSTRAINT MATRIX:

| Judicial | Press | Political | Civil    | Legal
                  |          |       | Compet.   | Society  |
------------------|----------|-------|-----------|----------|-------
Nigeria           | Low      | Med   | Med       | Low      | Low
India             | Med      | Med   | Med       | Med      | Low
Brazil            | Med-High | High  | High      | Med      | Med
The Bahamas       | Med      | Med   | Med       | Low      | Low
Jamaica           | Med      | Med   | Med       | Low      | Low

OVERALL RISK ASSESSMENT:
Nigeria: HIGH abuse risk
India: MEDIUM-HIGH abuse risk  
Brazil: MEDIUM abuse risk
Bahamas: MEDIUM abuse risk
Jamaica: MEDIUM abuse risk

NOTE: These are assessments of institutional capacity to constrain abuse,
not predictions that abuse will occur. Weak constraints = higher risk.

How Emerging Market CBDCs Shape Global Norms

STANDARD-SETTING DYNAMICS:

- Early implementations become templates
- Technical designs get copied
- "It works in X" becomes argument
- eCNY pattern spreading via this mechanism

- China offers CBDC technical assistance
- Belt and Road digital infrastructure
- Surveillance architecture embedded
- Recipients lack capacity to modify

- IMF/World Bank CBDC guidance
- BIS technical standards
- If emerging market CBDCs set precedent
- Standards may follow practice

- Companies build for early adopters
- Surveillance features become standard
- Privacy features not developed
- Market economics favor majority

IMPLICATION:
Emerging market CBDC designs matter globally
Surveillance-oriented designs becoming normalized
Privacy-preserving alternatives marginalized
Standards race to bottom, not top

---

Cross-Country Privacy Comparison

EMERGING MARKET CBDC PRIVACY COMPARISON:

| Central Bank | Identity | Offline | Institutional
| Visibility | Requirements| Privacy | Constraints

------------------|--------------|-------------|---------|---------------
Nigeria (eNaira) | Complete | National ID | None | Weak
India (e₹) | TBD (likely) | Aadhaar | Limited | Medium
Brazil (DREX) | Complete | Bank-based | N/A | Medium-Strong
Bahamas (Sand $) | Complete | ID required | None | Medium
Jamaica (JAM-DEX) | Complete | ID required | None | Medium

COMPARISON TO DEVELOPED MARKETS:
Emerging market CBDCs uniformly more surveillance-oriented
eCNY model dominant pattern
Digital Euro aspirations not replicated
Privacy is luxury good in CBDC design
```

Who Bears the Privacy Cost

IMPACT ON VULNERABLE POPULATIONS:

INFORMAL SECTOR WORKERS:
├─ Currently invisible (cash economy)
├─ CBDC forces visibility
├─ Tax exposure increases
├─ No matching social protection increase
└─ Worse off if formalization = taxation only

POLITICAL OPPOSITION:
├─ Donations traceable
├─ Organizing visible
├─ Account freezing possible
├─ In weak-institution environments: HIGH risk
└─ Democracy implications serious

MARGINALIZED COMMUNITIES:
├─ Already over-policed
├─ Financial surveillance adds layer
├─ Arbitrary enforcement risk
├─ Historic discrimination enabled
└─ Intersection with other oppressions

WOMEN IN CONSERVATIVE CONTEXTS:
├─ Financial independence visible to family
├─ Secret savings impossible
├─ Domestic abuse implications
├─ Cultural control reinforced
└─ Inclusion benefits offset by visibility costs

MIGRANT WORKERS:
├─ Remittances fully traceable
├─ Tax exposure both ends
├─ Immigration enforcement implications
├─ Networks visible
└─ Already vulnerable population further exposed

The Difficult Truth

EMERGING MARKET CBDC REALITY:

GENUINE INCLUSION BENEFITS:
├─ Some will gain financial access
├─ Direct payments can reach remote areas
├─ Reduced cash costs are real
├─ Economic data improvement real
└─ Benefits exist and matter

GENUINE SURVEILLANCE RISKS:
├─ Weak institutions mean abuse likely
├─ Privacy protections absent
├─ Vulnerable populations exposed
├─ Political control enabled
└─ Risks exist and matter

THE TRADE-OFF:
├─ Benefits accrue to some populations
├─ Costs fall on other populations
├─ Overlap is partial
├─ Those making decisions often not those bearing costs
└─ Trade-off is real, not hypothetical

- Provide some inclusion benefits (real)
- Enable significant surveillance (real)
- With weak constraints on abuse
- And vulnerable populations bearing costs
- While designers claim benefits justify costs
- Not clearly net positive for most marginalized

---

✅ Emerging market CBDCs uniformly prioritize surveillance over privacy. Every major emerging market CBDC examined has complete central bank visibility, identity requirements, and no meaningful privacy layer. This is consistent pattern, not cherry-picked examples.

✅ Financial inclusion benefits are real but limited. CBDCs can provide financial access, reduce cash costs, and enable direct payments. These benefits are genuine, though adoption challenges (Nigeria) show benefits don't automatically materialize.

✅ Institutional constraints are the main privacy determinant. Given uniform surveillance architecture, whether surveillance is abused depends on institutional factors: judicial independence, press freedom, political competition, civil society strength.

✅ The "inclusion as surveillance justification" pattern is widespread. Inclusion framing provides political cover for surveillance architecture. The pattern is recognizable across jurisdictions and should trigger skepticism.

⚠️ How much inclusion CBDCs actually deliver. Nigeria's experience suggests adoption is difficult even with government push. Whether inclusion benefits materialize at scale is unproven.

⚠️ Whether institutional constraints will hold. Medium-constraint environments (India, Brazil) could trend either direction. Surveillance infrastructure creates temptation; whether institutions resist is uncertain.

⚠️ How emerging market designs will influence global standards. Early movers shape norms, but counter-examples (Digital Euro) also exist. Which pattern dominates long-term is uncertain.

⚠️ What happens when surveillance is used politically. Clear examples of CBDC-enabled political targeting haven't emerged yet. When they do, reaction could shift dynamics—or normalize practice.

🔴 Privacy is treated as luxury good. Emerging market populations—who often have the weakest institutional protections—get CBDCs with the least privacy protection. This is backwards from a risk perspective.

🔴 Vulnerable populations bear disproportionate costs. Informal workers, opposition supporters, marginalized communities, and women in conservative contexts face surveillance costs while inclusion benefits are uncertain.

🔴 Pattern may become global standard. If surveillance-oriented designs dominate emerging markets (where most CBDC deployment is happening), this becomes the de facto standard that vendors build for and international organizations endorse.

🔴 Democratic input is minimal. In most emerging market CBDC deployments, public consultation was limited, privacy advocates marginalized, and technical decisions made by central banks with surveillance incentives.

Emerging market CBDCs represent a concerning pattern: surveillance architecture justified by inclusion rhetoric, deployed in environments with weak institutional constraints, affecting populations least able to resist abuse.

The inclusion benefits are real but uncertain in magnitude. The surveillance risks are real and structurally guaranteed by design. The trade-off is not clearly positive for the most vulnerable populations supposedly being helped.

Sophisticated analysts should be skeptical of "financial inclusion" framing that doesn't address privacy architecture. Architecture reveals priorities better than rhetoric.

---

Assignment: Select one developing nation CBDC project and analyze privacy protections, institutional constraints, and realistic outcomes for citizens.

Requirements:

• CBDC name, launch date, current status

• Issuing authority

• Stated objectives (official rationale)

• Current adoption statistics

• Identity requirements (tiered?)

• Central bank visibility (complete or limited?)

• Offline payment capability

• Data retention policies

• Comparison to eCNY and Digital Euro models

• Judicial independence rating with evidence

• Press freedom rating with evidence

• Political competition assessment

• Civil society strength assessment

• Overall institutional constraint score

• How would informal workers be affected?

• How would political opposition be affected?

• How would marginalized communities be affected?

• Any gender-specific implications?

• Are inclusion benefits likely to materialize?

• Are privacy risks likely to materialize?

• Net assessment for most vulnerable citizens

• What would improve the design?

• Accuracy of technical description (20%)

• Rigor of privacy architecture analysis (25%)

• Quality of institutional assessment (25%)

• Thoughtfulness on vulnerable populations (15%)

• Honest overall assessment (15%)

Time investment: 5-6 hours
Value: Emerging market CBDCs are where most deployment is happening. This analysis framework applies to evaluating any developing nation's digital currency trajectory.

Submission format: Document of 2,500-3,000 words with citations

---

For Next Lesson:
In Lesson 10, we examine Ripple's CBDC Platform and XRPL to understand where XRP and Ripple technology fit in the privacy landscape. We'll assess what privacy features Ripple's CBDC Platform actually offers—and doesn't—and evaluate claims about XRP's potential role in privacy-respecting CBDC interoperability.

---

End of Lesson 9

Total words: ~6,200
Estimated completion time: 55 minutes reading + 5-6 hours for deliverable