CBDC Pilots Are Failing. That's Why They're Speeding Up.

A central bank digital currency pilot is supposed to answer a simple question: will people voluntarily use a digital form of central bank money if it is offered alongside existing private-sector alternatives? Every significant CBDC pilot conducted in a democratic jurisdiction over the last three years has answered that question in the same way.

No.

Nigeria's e-Naira, launched with considerable fanfare in 2021, reached less than 0.5% of the Nigerian population by active usage by late 2024. The government has since pushed multiple initiatives to force adoption, including cash withdrawal limits and preferential access to subsidies through e-Naira wallets. Usage remains negligible. The e-Naira is a policy embarrassment the Nigerian government does not know how to retire.

The European Central Bank's digital euro preparation phase has produced detailed reports, extensive technical specifications, consumer research confirming high skepticism, and no clear path to voluntary adoption. When surveyed, Eurozone consumers report that they are satisfied with existing payment options and do not see what a digital euro adds to their life. Merchants asked about acceptance report that they do not want to maintain another payment rail when SEPA Instant already handles most of their needs.

China's e-CNY, the most technically mature of the major CBDCs, has seen slow and geographically uneven adoption despite extensive government promotion, integration with municipal services, and direct transfers of welfare benefits in e-CNY. Transaction volume remains small relative to Alipay and WeChat Pay. The private Chinese digital payment networks dominate the market the PBOC created the e-CNY to challenge.

The pattern holds across pilots. Voluntary CBDC adoption does not happen, because the product solves no consumer problem that is not already solved better by something else.

The Response That Matters

A central bank that concluded its CBDC program was failing would have a range of reasonable responses. It could slow the program. It could pivot to wholesale CBDC, which has a clearer institutional use case and fewer consumer privacy implications. It could abandon the retail version entirely and focus on regulation of private-sector payment innovation. These responses exist. They are not the responses being chosen.

Instead, across multiple jurisdictions, the response to voluntary CBDC failure is acceleration toward institutional integration and gradual mandatory adoption. The political calculation appears to be that the project has enough sunk cost, institutional commitment, and strategic value that retreat is not acceptable, and that the only path forward is to make CBDCs mandatory in contexts where individual users cannot opt out.

This acceleration is visible in several forms.

First, integration with welfare and subsidy disbursement. The fastest way to get CBDC into circulation is to pay benefits in it. Several pilot jurisdictions have begun or are planning to require that specific social benefits, tax refunds, or subsidy programs be disbursed through CBDC wallets. Recipients retain the theoretical option to convert out of CBDC to bank deposits or cash, but the default becomes CBDC. For users at the lower end of the income distribution, "default" is a strong word.

Second, integration with public services and government transactions. Some jurisdictions are moving toward requiring CBDC for specific government payments, licensing fees, or public transit. Users who want to interact with the state are routed through CBDC infrastructure regardless of what their private payment preferences might be.

Third, reserve requirements and wholesale integration. Commercial banks are being positioned to offer CBDC as a default customer option, with non-adoption becoming more expensive for the bank than adoption. The commercial banking sector is being quietly drafted into the distribution channel the CBDCs could not build themselves.

Fourth, programmatic features designed to discourage deposit holding. Several CBDC frameworks include holding limits, negative interest features, or expiration dates on specific use cases. These features are sold as monetary policy tools. They function as adoption pressure. If holding CBDC is structurally more expensive than holding a bank deposit, users hold CBDC only when they cannot avoid it, and the network effect the central banks need cannot form. So the features shift toward forcing usage rather than incentivizing it.

Why Voluntary Adoption Was Always Going to Fail

The consumer problem a retail CBDC is supposed to solve is not obvious. In most jurisdictions, consumers already have access to fast, cheap, reliable digital payments through private sector networks. Debit cards work. Bank transfers work. Contactless payments work. In countries with advanced fintech sectors, instant payment systems like the UK's Faster Payments, Brazil's Pix, India's UPI, and the EU's SEPA Instant have made real-time digital payment the default experience. Against this baseline, a CBDC that replicates existing functionality adds nothing visible to the user.

The features that would differentiate a CBDC are mostly features users do not want. Programmable restrictions on what can be purchased. Direct central bank visibility into transaction details. Holding limits. Interest-rate controls at the individual wallet level. These are features from the perspective of policy makers. They are costs from the perspective of users.

The CBDC advocacy case has attempted to paper over this mismatch with vague appeals to financial inclusion, innovation, and monetary sovereignty. None of these appeals translates into consumer demand at the point of sale, which is where voluntary adoption would have to happen. Consumers do not adopt payment technologies for abstract policy reasons. They adopt payment technologies because specific transactions are easier, cheaper, or more useful with one option than another. No CBDC has cleared this bar.

The Real Target

If voluntary adoption is not the goal, what is?

The most honest answer is that CBDCs are being built primarily as infrastructure, not as consumer products. The infrastructure is useful to central banks and governments for reasons that are orthogonal to consumer preferences. It provides direct visibility into economic activity at the transaction level. It enables fine-grained monetary policy transmission. It creates an option to implement capital controls, sanctions, and other policy tools at the individual wallet level. It provides a backup distribution channel for government payments that does not depend on the private banking system.

These are real policy goods from the perspective of the institutions building CBDCs. They are also real policy concerns from the perspective of the people they are being built on top of. The tension between these two views is what voluntary adoption was supposed to resolve. It failed to resolve it, so the resolution now has to happen through compulsion or through structural features that remove the choice.

The Exit the Design Assumes

The CBDC frameworks being rolled out do not formally abolish cash, ban private payment networks, or prohibit alternative assets. What they do is make the non-CBDC options incrementally more friction-laden. Cash withdrawal limits. Higher transaction fees on private networks. Reporting requirements on cash-intensive businesses. Transaction scanning on private digital payments. The design assumes that users who face slightly higher costs on every alternative will migrate to the CBDC not because it is better, but because it is less punished.

Bitcoin, self-custody wallets, and private-key-controlled cryptographic payment systems are the exits the CBDC design does not fully account for. They are technically resistant to the incremental friction strategy because the friction has to be applied at the point of interaction with regulated intermediaries, and self-custody minimizes those interaction points. A Bitcoin transaction between two self-custody wallets does not route through a bank, does not pass through a payment processor, and does not surface at any of the choke points the CBDC rollout depends on.

This is why the regulatory discussion around self-custody wallets has intensified in parallel with CBDC acceleration. The two trends are the same trend.

What Accelerating Failure Looks Like

The CBDC pilots are failing at their stated objective and advancing toward their unstated objective. That is not a contradiction. The failure is the reason for the acceleration. If voluntary adoption had worked, central banks would have time. Without it, they need to cement the infrastructure before the opposition consolidates.

The window in which individual users can make their own decisions about which monetary rails to use is closing in multiple jurisdictions at once. It is worth understanding which assets and networks are being designed to function outside that narrowing channel, because those are the assets and networks whose strategic value will be most visible on the other side of the current transition.

Bitcoin is on that list. Nothing else on it is comparable in size, liquidity, or institutional maturity.

The CBDC rollouts are telling you what comes next. The speed of the rollouts is telling you how soon.