President Biden’s March 2022 Executive Order on “Ensuring Responsible Development of Digital Assets” was, as the Financial Times said at the time, short on policy detail. Similarly, crypto billionaire Sam Bankman-Fried said that “I don’t think it moves the needle that much”. There order called for a commitment to “reinforce US leadership in the global financial system” through means including “the responsible development of payment innovations and digital assets” and so on, but it also included an order for the Director of the Office of Science and Technology Policy (OSTP) and the Chief Technology Officer (CTO) of the United States submit a report on central bank digital currency (CBDC) to the President.
This report on the “Technical Evaluation For A U.S. Central Bank Digital Currency System” has just been published by the OSTP and it makes interesting reading for those of us who think that digital currency is on the way although. The report (spoiler alert) doesn’t make any recommendations as to what a U.S. CBDC should be, it merely sets out some choices and their likely impact on architecture. Which, in my opinion, is a good thing since we are some way away from having stakeholders agree what the final set of requirements, goals and constraints should be.
There’s a lot in it. The report looks at the design choices for a U.S. CBDC to see how these choices would impact policy objectives and considers the feasibility of building a minimum viable product (MVP) based on those design choices. It also looks a how a CBDC might impact government processes (looking at issues such as welfare, privacy and security), an aspect I found particularly interesting given some of my own early work in this area.
What I found most interesting was the attempt to enumerate and clarify the high-level objectives since it is obvious that no worthwhile discussions about implementation can proceed until these objectives are in place. The OSTP sets out eight policy objectives:
- Provide benefits and mitigate risks for consumers, investors, and businesses. Well, yes, of course.
- Promote economic growth and financial stability and mitigate systemic risk. Well, yes, of course.
- Improve payment systems. There are many critics of the U.S. payment system (eg, me) who think that bringing in competition from digital currency, rather than regulation, would be the best way to both reduce costs and spur innovation and, as I have consistently pointed out, it is important for the CBDC infrastructure to be developed in parallel with, not on top of, the existing electronic money infrastructure.
- Ensure the global financial system has transparency, connectivity, and platform and architecture interoperability or transferability. In particular, they said that the CBDC facilitate transactions with cash and other CBDCs. They also note that the CBDC system should be designed to avoid risks of harm to the international monetary system (IMS).
- Advance financial inclusion. Within this policy objectives, the OSTP specifically and clearly states that “offline capability should be incorporated”, a subject I will return to shortly.
- Protect national security, including compliance with anti-money laundering (AML) and combating the financing of terrorism (CFT) requirements as well as, of course, sanctions. Intriguingly, and presumably for political reasons, the policy objectives is for the CBDC system to “allow for the collection of information necessary to fulfill these requirements, but not more”, which I took to mean that the CBDC itself will not implement AML, CTF and sanctions. I note also that within the context of national security, the report says that CBDC should support “U.S. leadership in the global financial system, including the global role of the dollar”, an area that I highlighted in my 2020 book on the subject, “The Currency Cold War.”
- The CBDC system should be able to incorporate technical protections that prevent the use of CBDC in ways that violate civil or human rights. The CBDC system should also be “protected from abuse during periods of high political volatility.”
- Align with democratic and environmental values, including privacy protections. I am not qualified to comment on the environmental values, but and (I think) qualified to offer an opinion of the OSTPs view that the system should maintain privacy and protect “against arbitrary or unlawful surveillance.” In short, I agree. Without rehashing all of the arguments about anonymity, I will only say that the bogus comparison between electronic cash and physical cash leads to calls for anonymity that would be disastrous. CBDC should indeed be private, but not unconditionally anonymous.
All things considered, this is useful set of objectives to work with and while it is of course a significant amount of work to gather, refine and translate these objectives down into the specifications for the procurement and development of a population-scale CBDC, they certainly provide a useful framework to facility communication between stakeholder groups.
Inclusion
Christopher Waller, a member of the Board of Governors of the Federal Reserve System, said earlier this year he was sceptical that a Federal Reserve CBDC “would solve any major problem confronting the U.S. payment system”. He is right to say that there is no “burning platform” for a retail central bank digital currency in the United States, but that doesn’t mean that the system is a good as it could possibly be and serves consumers, businesses and government as best it can. Banks may well be content with the status quo — an illustrative reaction to the original executive order was the The Bank Policy Institute’s view that “CBDCs would pose considerable and unavoidable costs to the financial system and economy while producing few, if any, tangible benefits” — but the views of banks must of course be considered alongside the views of a much wider range of stakeholders.
It is true that the private sector can satisfy some of demands of the new economy without a CBDC. Appropriately-regulated private sector “stablecoins”, for example, could be used to satisfy the demands of the decentralised finance (“defi”) sector for money that can be algorithmically-traded for cryptographic assets. Having said that, it is not obvious that the long-term goals of such stablecoins would be congruent with wider public policy goals around money and payments. President Biden’s order included a mention of the potential for a US digital dollar “to foster greater access to the financial system” but when it comes to financial inclusion, I have to say that it is not at all clear to me how a CBDC could deliver greater access unless there is greater access to the digital wallets in which such currency might be stored. If these wallets can only be provided by banks, and the same customer due diligence (CDD) rules will apply as for bank accounts, then there won’t be any progress (hence my view that this is primarily a digital identity problem, not a digital money problem.)
This why that fifth objective, about financial inclusion, caught my eye. The Bank for International Settlements (BIS) published a good paper about the potential for CBDCs to improve inclusion earlier in the year, setting out that while CBDCs are not “magic bullet” in this regard, they are certainly a tool to promote financial inclusion if this objective is part of the architecture.The authors note that central banks are considering design options around promoting innovation in the two-tiered financial system (eg, allowing for non-bank payment service providers), facilitating enrolment and education (via simplified due diligence and electronic know your customer, fostering interoperability (both domestically and across borders) and offering a robust technology platform with, crucially in my view, offline payments.
The OSTP report defines offline transactions as exchanges of CBDC that occur when the exchanging parties can communicate with each other, but they cannot communicate with the transaction processor. In other words, offline transactions must be possible when there is no internet, no mobile signal and no electricity. That is, the transaction counterparties must be able to connect their devices directly via local interfaces. In which case one design choice set out in the OSTP report is to use trusted execution environments (TEEs) for individuals to verify to each other that they have the CBDC they claim to have, and to facilitate the transaction securely.
The choice to use some form of secure hardware in a CBDC has implications, since it means that inclusion will require access to this hardware, but I do not see this as the barrier it once was. After all, smartphone penetration in the U.S. is already