A CBDC is Literally Beyond the Government’s Capability

We’ve discussed the negative political and social implications of a US central bank digital currency (CBDC) at length. And we’ve noted how the more people learn about these implications, the more they are against a Federal Reserve CBDC.

A new article at Bitcoin Magazine today looks at the practicality of the Fed issuing a CBDC, and the bottom line is it’s just not feasible in terms of scalability, technology and service.

Their own report specifically mentions more efficiency as a payments platform, faster cross-border payments, economic growth and stability (easier monetary policy control), protecting against cyber and operational risks (security breaches of financial institutions), safeguarding the privacy of sensitive data and minimizing the risk of illicit financial transactions. So in other words they want to have total insight into your entire financial activity, have the ability to directly deposit money into people's accounts for stimulus and monetary policy purposes and be able to arbitrarily block "illicit activity," which as we know these days is a quickly shifting target that means who knows what next year.

In 2017 your average adult made 41 economic transactions a month, with about 12.4 of them taking place with cash. That would mean looking at these figures that approximately 3,192,200,000 cash transactions occur in the United States each month. To compare with Bitcoin with some napkin math ignoring the efficiencies gained through transaction batching and other optimizations, the Bitcoin blockchain processes somewhere around 3000 transactions a block on average, getting to somewhere in the figure of 13 million transactions a month. So just to replace the average volume of cash transactions alone a CBDC would need to process 246 times more transactions each month than Bitcoin. And that is just replacing cash, not eating into debit or credit card payments, or absorbing some of the payment volume of fintech apps like PayPal and Cashapp.

Such a system would need the kind of uptime that we currently see with payment systems like Visa and Mastercard. Think about how often basic digital government services fail and go offline. Have you ever had a tax year where IRS payment portals did not get overloaded and crash? Does anyone remember the massive debacle of the Obamacare website and constant crashing and failure? Do you really think that the federal government could handle building and maintaining a system independently to facilitate the types of payment volumes necessary to offer a digital alternative to cash without massive failures? What happens when users suffer fund losses? Lose their phones? Things break? Massive companies such as PayPal and major banking institutions who have had years, decades in some cases, building customer support systems to handle such failures and issues regularly drop the ball, take forever to respond to people and drag the entire process out into a long and frustrating ordeal before actually solving the problem. Do you think the federal government could handle such a task? No. Even considering that a realistic possibility is frankly laughable in my mind.

Now let's look at the financial effects of such a CBDC system eating into the current financial system. The idea ostensibly is to have a system operated by the Federal Reserve (or potentially the Treasury?) that provides financial services and capabilities directly to consumers. That is the role that private banks and financial service providers fill in the economy currently. The Federal Reserve does not offer any directly consumer facing tools or services, they provide accounts to the financial institutions that do so in order for them to hold reserve money with the Federal Reserve and to settle transactions amongst themselves using the Fedwire system. To introduce a CBDC that is directly consumer facing would begin an inevitable disintermediation of these private entities in the financial services market, and given that financial services make up ~7.4% of the U.S. GDP, that process would have a huge implication for the U.S. economy depending on how deeply the CBDC bit into that market. How many people would choose to use a CBDC over Cashapp or PayPal? Over their bank at JP Morgan? If it was a significant amount of people this would have a huge negative effect on the financial sector. Every person who chose to withdraw their money from those institutions and instead hold in a CBDC would be someone pulling their deposits from the bank and leaving them with less reserves to conduct business with.

What about cross-border payments? How would that mechanically work? Connections to legacy systems such as SWIFT? Simply sending the CBDC token directly to someone in a foreign jurisdiction? If you are simply going to use SWIFT or other international transfer systems, how does a CBDC in any way improve the speed of cross-border payments? If you are going to directly facilitate the transfer of the CBDC itself internationally, how do you enforce KYC and AML? Does that not require directly identifying foreign citizens making use of the system? This would result in the expansion of both data collection and direct financial controls of the U.S. government into foreign territories.

So let's recap: the technical effort to implement a system such as this is immense, and well beyond the capabilities of the government to handle themselves. Deploying such a system would directly eat into private financial companies' bottom line, and cause a massive hit to the U.S. economy if successful. Attempting to deploy this as a cross-border payments tool would either make no difference whatsoever, or come with massive political implications in doing so. So what is the reality? An American CBDC as it is predominantly envisioned is just never going to happen. It is completely impractical on a technological level and would usher in a very destructive restructuring of the U.S. financial services sector if adopted at any serious level.