The Fed's Central Bank Digital Currency Report Falls Flat
from the why-do-we-need-this-again? dept
It took nearly a year, but the Federal Reserve has finally released its report on central bank digital currencies (CBDCs). The report fails to live up to the Fed's hype. If anything, it shows a CBDC is a solution in search of a problem.
The 40-page report contains so little information, it makes you wonder what the Fed has been working on for all this time. To be fair, the report does offer an idea of how the Fed envisions a CBDC taking shape, but their vision is a bad one. The Fed may have finally made good on its promise to deliver a report, but it has a long road ahead if it intends to deliver a CBDC.
The Fed's desired approach is for a CBDC that would be "privacy-protected, intermediated, widely transferable, and identify-verified." That might sound good at first glance, but a closer look reveals that this approach is really quite unfortunate.
Protecting the privacy of the American people has been one of the greatest concerns around the design of a CBDC. So it makes sense that privacy was listed first. However, at the opposite end of the list, the Fed hedges on that promise with just two words: "identity verified." Essentially, this means the Fed has abandoned the idea of crafting a CBDC that would act as a digital form of cash. It means people will need to have their identities verified before using the CBDC so that the Fed can keep a record of their transactions. Where cash offers Americans the freedom to make financial decisions in private -- a freedom that should be protected by the Fourth Amendment -- the Fed's CBDC would likely be another avenue for information collection.
What's more, it's unclear what real benefits the Fed's CBDC would have for consumers. In the report, the Fed stated that a CBDC could improve the speed of payments, financial inclusion, and the dollar's international status. But those are all areas that are being fixed through other endeavors -- endeavors that will likely be completed before a CBDC reaches the market.
For example, both the private and public sectors have been developing networks to speed up payments. For financial inclusion, survey data from the FDIC has found that the number of unbanked households decreases every year as technology makes banking more accessible. That rate of improvement will likely only increase as private sector initiatives to help the unbanked (e.g., BankOn) continue to get off the ground. Finally, every positive step for the dollar will improve its international status. A CBDC might help the United States keep up with the Joneses, but it's not unique in its ability to improve the dollar's status. More so, it is highly unlikely that a "CBDC" is a necessary requirement to compete on the world's stage. People are not going to flock to the Chinese yuan or the Nigerian naira simply because they've "gone digital."
A CBDC may be an exciting prospect for central banks, but the Fed is going to need a much more robust set of benefits if it is going to justify experimenting with the money in people's wallets.
Just before the report's release, Fed Chair Jerome Powell wrote to Senator Toomey (R-PA) saying, "One critical question is whether a CBDC would yield benefits more effectively than alternative methods." By all accounts, it seems the answer to that question is no. Both the Fed and Congress will have a long road ahead if either one intends to justify the supposed need for a CBDC to the American people.
Nicholas Anthony is the Manager of the Cato Institute's Center for Monetary and Financial Alternatives and a contributor with Young Voices.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: cbdc, central bank, central bank digital currencies, cyrptocurrency, federal reserve, monetary policy
Reader Comments
Subscribe: RSS
View by: Time | Thread
If it's digital, non-anonymous, and controlled by the government, it can also be instantly and unilaterally seized by the government.
This does not sound like a good idea.
[ link to this | view in chronology ]
Re:
The Chinese CBDC initiative is exactly that, and not simply a digital wallet linked solely to your bank account.
[ link to this | view in chronology ]
Essentially, this means the Fed has abandoned the idea of crafting a CBDC that would act as a digital form of cash.
Was anyone expecting something different? It is quite literally illegal to do anything other than what was proposed here, the law is very clear. If anything, it's a good thing that the Fed didn't decide to go rogue and waste taxpayer money on facially illegal policy proposals. If only Georgia would have followed suit.
[ link to this | view in chronology ]
It's technically possible today to have a digital currency where the government can verify the identity of someone without actually getting any information at all about the person, it's a concept called "zero-knowledge proofs". Note though, technically possible isn't necessarily the same as feasible or practical.
Of course, implementing something like that hinges on that the government really wants the users of a digital currency to have privacy.
[ link to this | view in chronology ]
Re:
Yet another name for Remote Trust My Statement.... err...Remote I am Not a Bank Robber.... errr.... Remote Attestation.
From the wikipedia article on it:
So it's a claim of knowledge of a password without any other evidence being given. The actual knowledge is never able to be verified. Rather, we have to assume a result. This is worthless for actual verification of anything, and indeed the wikipedia article's own example admits as such:
So the rules make the results impossible to actually verify for the participants, and any observers present during the "verification" process. Meanwhile, we've thrown crypto into yet another worthless and expensive calculation. Cue this being used everywhere as some legal / business requirement's security theater.
For those that don't see the link to Remote Attestation: The entire concept of Remote Attestation is trustworthy verification of a statement of fact about an unauthenticated source made by said unauthenticated source. The biggest example of which is easily found via a quick google search: Trusted Computing.
According to the wikipedia article on that:
In other words a claim of the state of a system (the signed certificate) is being made without any other evidence being given. The actual state of the system is never able to be verified. Rather, we have to assume a result. How is this signature made? According to the wikipedia article:
So in "Trusted" Computing, the secret is stored in a TPM, however that TPM is in the unchecked physical possession of a party that may be hostile to the entire ecosystem. There's no way to actually verify that the secret is in fact secure from hostile actors. The rules require us to assume that the secret is secure. Or to put it another way:
So the rules make the results impossible to actually verify for the participants, and any observers present during the "verification" process. Meanwhile, we've thrown crypto into yet another worthless and expensive calculation. Cue this being used everywhere as some legal / business requirement's security theater. (Which as of Windows 11, it is.)
At the end of the day, all security boils down to:
"If an authenticated someone is authorized then do this otherwise do that." Which is why how those authentications are generated is important. We have enough problems with someone just spoofing a signature somewhere or changing the instructions to "Always to this." We don't need the additional issue of effectively worthless security designs to contend with.
As for a government using such a broken design for "private" monetary transactions, it will happen. One of the requirements is that the talented crooks can easily bypass the few checks, or lack there of, against abuse and money laundering. A system where even the words of the conversation cannot be verified, let alone the dollar amounts and account numbers, easily passes that requirement.
[ link to this | view in chronology ]
Re: Re:
Of course, the flip side of it is that the owner of the secret desperately wants to secure it from hostile actors. Which, as you've shown, includes the owner of the hardware. Which leads to the trust issue being flipped: if the source of the secret cannot be inspected by the untrusted party, they have to assume that the mechanism itself is secure ... and does only what it has been advertised to do.
Which leads to the corollary security issue of some other party gaining access to the mechanism and subverting it. All that trust goes out the window, and all that you are left with is a security hole you can't fix.
[ link to this | view in chronology ]
Re: Re: Re:
Of which, the safest and easiest means of doing that is to never give the hostile actor the secret in the first place. That won't allow the owner of said secret to make a crap ton of money selling access to a completely arbitrary lock however.
So we wind up with a situation where the individual has no security and is considered hostile by their own equipment, all for ever increasing corporate profits.
That's not a gain for society or even the individual paying for the damn equipment, and should be, in my opinion, verboten by law.
The secure method of doing this would be to have the individual define what the secret is. Then they have skin in the game, and thus have a reason to protect it. In addition to having them ensure secrecy by allowing them to replace a compromised secret with one that is not.
Except that assumption is a false statement for the very reasons I gave above. It's impossible to verify that a given secret is secure from hostile actors. Which means that the assumption about "does only what it has been advertised to do." is false because that assumption is supposed to be "confirmed" by the secret whose secrecy is unverifiable. The chain of trust is broken from the start. The only safe assumption to make in this case is that you are compromised by a security hole you are not allowed to fix.
Total compromise by default is not a state that society, or the world in general, should be held in for any reason.
[ link to this | view in chronology ]
Re: Re:
It's always nice to see people quoting things while leaving out large parts that are very inconvenient for their argument.
You also conflate TPM with zero-knowledge proofs, which is two distinctly different things, but hey, it let you go on a rant.
The above means you aren't trustworthy in your argument.
[ link to this | view in chronology ]
Re: Re:
Accurate as far as it goes.
Though I have to say that's taking the long way around rather than saying "The guy who builds and maintains the lock will always have the keys to that lock."
[ link to this | view in chronology ]
Re:
That can be done with Chaumian digital cash, invented in 1983. It's both "identity-verified" and anonymous, designed such that one's identity is only revealed if one tries to spend their own cash twice ("counterfeiting", effectively). This guarantee comes from mathematics, not the government or bank running the currency. But I doubt that's what the Fed is thinking about.
People have proposed ways to use more modern zero-knowledge proofs, such as ZK-STARKs, to prove more specific things—for example, that American taxes have been paid on all money in one's account. I don't expect this is what the Fed is planning either.
[ link to this | view in chronology ]
Hey, kids, don't make me stop this car
I thought the point of the report was totally clear: for consumers, anything a CBDC can do, a normal bank account can do. Banks will be able to do instant payments with Fednow, and they can provide low-cost easy to use accounts if they can be a little less greedy. On the other hand, in a CBDC account the deposits would all go to the Fed rather than being usable by the bank, which is known as narrow banking, something the Fed has never wanted.
So the message is, hey, banks get your act together and provide fast, cheap, flexible accounts. ''Cuz if you don't, we will, and you wouldn't like that.
[ link to this | view in chronology ]
Maybe people can carry the identity verification with them,
like on their right hands or on their foreheads. Perhaps they could even give it some kind of star rating.
[ link to this | view in chronology ]
another point of view on this
It makes it so much easier for several interested parties.
1) Every transfer automatically has sales tax added - both from the "sellers" location and the "buyers" location, thus doubling tax revenue for states.
2) Every sellers transaction is automatically tracked for the new year-end 1099 reporting requirements. Thus increasing IRS revenue. Up to the seller to find receipts for every transaction to prove the actual profit/loss.
Turning everyone into a business in the eyes of the government for increased tax regulation and auditing data. Allowing instant seizure of any funds whose source can not be tracked.
So we get tax wins for states, tax win for IRS, and tons of work for CPAs. What's not to love?
[ link to this | view in chronology ]