Ecash 2.0, Inalienable Private and Quantum-Resistant
Ecash 2.0, Inalienable Private and Quantum-Resistant
paper cash while protecting society against criminal use far better than
paper money ever could. In particular, it provides each holder, though
their payments are anonymous, with the ability to allow irrefutable
tracing of any of their payments—and this ability is “inalienable” in that it
simply cannot be given or taken away. This improved control by persons
over the privacy of their own payments further allows the adoption of
privacy where it might otherwise be blocked by regulation. Without such
inalienability, moreover, it is believed that payment privacy intended for
particular persons may be taken from them, by malware for instance, and
used to protect the privacy of aggregated payments made by others.
The supply of currency is completely controlled by its issuer, and the
currency is provably protected against counterfeiting even by a quantum
computer. Optionally, a blockchain, or individual customer choice of
public blockchain, can bring the advantages of such chains, including
transparency of the total amount of unspent digital cash outstanding. The
design builds on several well-established cryptographic protocols, like
public-key digital blind signatures and mix networks, as well as some new
eCash 2.0
cryptographic techniques of its own. Its improved privacy and quantum
resistance, when combined with its Visa- or PayPal-like scalability,
make it an ideal candidate for central bank digital currency (CBDC).
M
to counterfeiting ost central banks are currently exploring the issuance of central bank
digital currencies (CBDCs), and a recent BIS survey on the topic found
that central banks collectively representing a fifth of the world’s popula-
tion are likely to launch retail CBDCs in the next three years [1]. Many central banks
David Chaum are investigating “wholesale” CBDC, that is, for payments between banks and oth-
XX NETWORK er institutions. CBDC schemes that meet strong enough requirements, like those
used as the example here, can be used for both. Also, the G7 has recently published
a set of Public Policy Principles for Retail Central Bank Digital Currencies (CBDC)
Thomas Moser [2] alongside a G7 Finance Ministers and Central Bank Governors’ Statement on
SWISS NATIONAL BANK CBDCs and digital payments, which emphasize the importance of “rigorous pri-
vacy, accountability for the protection of users’ data, and transparency on how
information will be secured and used, to command trust and confidence by users.”
[3]. This view is echoed in the July 2021 People’s Bank of China report on its CBDC
in development, “The Progress of Research & Development of E-CNY in China”:
“E-CNY follows the principle of ‘anonymity for small value and traceable for high
value,’ and attaches great importance to protecting personal information and pri-
vacy.” [4] The importance of privacy and its potential impact on design choices
was also stressed in the second joint report of a group of central banks and the BIS
[5]. The protection of privacy in CBDC design is also a key public demand. A recent
whitepaper on digital currency by the World Economic Forum notes: “Of the 8,200
comments received by the European Central Bank (ECB) during its consultation
period on the potential for a Euro-denominated CBDC, 41% of all replies centred
around privacy.” [6]. Similarly, public feedback to the Bank of England’s March
2020 Discussion Paper on CBDC emphasized the importance that users place on
01
having privacy in their transactions [7]. It is hard to imagine that that are withdrawn “blinded” and so only entered in a central
a CBDC that would allow government to track every payment database when deposited. This provided what was called “one-
would be welcomed and widely adopted by citizens, especially if way privacy,” making the system unsuitable for uses such as
there were a superior alternative. extortion and bribery. [11] The example of a CBDC architecture
T
illustrated here structurally differs from that of earlier eCash, but
his legitimate interest in protecting privacy must be bal- preserves these properties. It is structured so that all consumer
anced against the equally legitimate interest in prevent- and merchant interaction is with commercial banks, while mon-
ing crime. To address these needs, it has been suggested ey creation and the database of deposited money are provided
that privacy be limited somehow to low-value transactions, as exclusively by the central bank behind the scenes. Commercial
in the PBOC report on e-CNY. A substantial proportion of the banks authenticate their customers and monitor the extent of
Eurosystem Report’s finance-professional respondents concur: withdrawals and deposits, but otherwise the presence of these
“A quarter support selective privacy under which transactions intermediaries does not affect the underlying cryptographic
below a given amount would stay private (mostly credit institu- protocols.
tions and PSPs).”[8] Such an approach would also seem to be
C
consistent with international standards on combating money onsumers are first enrolled, ideally, via a visit to the
laundering and terrorist financing, according to which occasional branch of a commercial bank where they are known or
cash transactions or wire transfers whose value remains below identified (see Figure 1). Thereafter, withdrawal can be
a certain threshold require no or only simplified verification of as simple as withdrawing paper cash via an automated teller
customer and recipient information. It has additionally been pro- machine (ATM) but might typically be conducted online. Because
posed that consumer withdrawal and holding amounts of CBDC each transaction is separate, system resources scale linearly
be limited, which would also serve as a measure to control the to- with growth in transaction volume. Moreover, as validated by the
tal volume of a CBDC in circulation. For example, the Eurosystem earlier practical deployment of eCash 1.0, operational robust-
Report notes: “Almost half of citizen respondents mention a need ness, cost, and throughput speed are all attractive. Two other
for holding limits, tiered remuneration, or a combination of the differences are that eCash 2.0 is secure against counterfeiters,
two, to manage the amount of digital euro that would be in cir- even those with access to quantum computing; and eCash 2.0
culation. A similar share of professional respondents agree.”[9] can optionally but flexibly extend to public blockchains and
H
hence bring their various advantages. A way to adapt eCash 2.0
owever, these proposals leave open the loophole that
to offline use has been proposed. It uses smartphones in combi-
multiple such small amounts can be aggregated to make
nation with a new type of non-chip physical card to allow secure
large but untraceable transfers of value. The CBDC solu-
payments where no online connection is available. [12]
tion introduced here, eCash 2.0, prevents this possibility. eCash
2.0 is anonymous—yet aggregating amounts larger than those
issued each user is thwarted. Anonymity is obtained via the
Anonymity and Misuse Prevention
T
“blind signature” technique used by the original eCash (as further
he eCash 2.0 CBDC introduced here can be considered
detailed below). New here, however, is that each user is given, as
“software only,” as it requires no special hardware
part of enrolling in the system, an irrevocable ability to undo the
devices. Merchant or consumer users, if their secret
anonymity of any value withdrawn from their account—even if
cryptographic key were to be compromised, would stand to
the user wishes to give this ability up. This makes aggregation
lose only the amount of money they are holding in the system.
of value obtained from multiple user accounts very risky. With
To protect their keys against attack, some users and merchants
peer-to-peer payments, if the value issued to a user has already
may choose commercially available key protection devices, such
been spent by someone else, a criminal aggregator for instance,
as the digital custody now built into consumer hardware like
the user can at least reveal where it was spent. But if the value is
smartphones. Banks can be expected to continue to use current
not already spent, the user can spend it first, thereby preventing
commercially available hardware devices to protect their keys.
anyone from spending it later. Together, these properties greatly
Transactions remain quite fast, even if their number becomes
reduce the risk of criminal aggregation and of subsequent abuse
large, because additional transaction volume can be efficiently
of the privacy afforded.
T
routed to essentially independent but appropriate processing
he system builds on and improves the eCash technology resources, giving the system the kind of linear scalability enjoyed
used by some major commercial banks in the 1990s. [10] by typical large transaction-processing systems like Visa or
This technology introduced “digital bearer instruments” PayPal today.
02
W M
ith eCash 2.0, a user can make payments to ore technical aggregation attacks that could be
merchants while remaining anonymous, even if the widely applicable, but are also thwarted here, include
merchant and the user’s bank try to discover the payments for undelivered goods and false refund
user’s identity from all payment information they can obtain. transactions. The threat model of the protocols presented
accordingly includes such apps and user behavior, and thus
The commercial banks are in turn assumed to comply with so- requires a structural solution. When CBDC is thought of as
called “Know Your Customer” and “Anti-Money Laundering” an electronic replacement for banknotes, the precedents by
regulations (KYC/AML). However, if a single user could control analogy are once again familiar. For instance, clearly nobody
large amounts of CBDC, the KYC/AML provisions could be should be able to withdraw cash from your bank account but you.
circumvented completely. Preventing aggregation of CBDC In this respect, eCash 2.0 is already superior to paper money,
implies, at least, that no user should be able to withdraw too large since, as will be explained, withdrawal is just as quick and simple
an amount of spendable CBDC, as a few users might be leaders as taking cash from a virtual ATM, but far more secure. Similarly, if
or minions of criminal organizations. This is easily addressed by a bad actor were somehow able to take cash from your account,
monitoring or limiting amounts withdrawn per user. Again, an you would want the notes’ serial numbers to be known so that
analogy with paper money would be the ATM withdrawal limits on the miscreant could be tracked, if not apprehended. On the one
most consumer cards. hand, banknotes today don’t allow such tracing, but CBDC can.
H
On the other, CBDC can be used more easily than banknotes
owever, such restrictions, common to several other by criminals, in part because it can more easily be hidden when
CBDC proposals, are only the beginning of preventing stored or transported but also because it can be used to pay
criminal misuse by aggregation, not the end. Much more remotely. But if large sums of truly privacy-protected CBDC were
insidious and fundamental potential threats could seek to allow at the disposal of criminal organizations—the problem solved
a single person or organized criminal group to control a large fundamentally here—the privacy afforded users could limit ways
sum of CBDC. Malware on smartphones, something that has to stop or apprehend them, and their operations could be greatly
proven impractical to stop, could for instance simply allow all facilitated and protected.
A
withdrawal transactions to be with keys centrally controlled by
simple example procedure for when a user initially signs
those who created the malware. As to transaction size triggering
up to get CBDC (say, by opening a CBDC facility as part
the suspension of anonymity, such prohibited transactions could
of a current account with a commercial bank) involves a
be accomplished via numerous smaller payments between what
user creating a passphrase that will provide access to the user’s
appear to be separate accounts but that are in fact controlled
private key and can be used to create a corresponding public key.
by criminal individuals or organizations, whether though user
The user enters the passphrase into an app on their phone, but
collaboration or covertly via malware.
also has it memorized.
I
n some scenarios, for example, nobody would notice the At the commercial bank branch, the user is asked to write the
diversion of fully untraceable money if, once it was spent passphrase down and then answer a few questions about it.
from compromised phones, it was retrieved and diverted The user’s phone app and the bank’s system together randomly
from compromised retail sites. These sites could be one or pick the questions about the passphrase from what is in effect
more popular payment destinations that are unaware that they a very large list. The app in the user’s phone communicates the
themselves have also been compromised. Alternatively, the sites passphrase to the bank’s system, but with each word encrypted.
could be gray-market or black-market sites that perhaps only The banker asks the questions randomly arrived at by the
accept payments from phones running the modified software, customer’s phone app and the bank’s system. The banker or
so the user could be incentivized to install the malware on their bank software then enters the answers provided by the user
phone in order to be able to use these sites. It’s even possible that into the bank’s system. The system, by communicating with
parties paid by the aggregator could verify that they themselves the user’s offline phone app digitally over Bluetooth or the like,
control the untraceability of the payments they then would make obtains a zero-knowledge proof1 that everything is as it should
with funds received from an aggregator. be and registers the user’s public key.
1
A so-called zero-knowledge proof is a cryptographic technique a computer can use to convince another computer that some underlying data
“cleartext” possesses specific properties while the cleartext remains encrypted. In the example of Fig. 1, it allows the user’s smartphone to convince
the the bank’s tablet that the user’s passphrase is in effect the user’s private key--yet the tablet learns essentially nothing about either the passphrase
or the private key.
03
O
f course, neither the user nor their phone has given the user’s phone knows the passphrase, but it cannot keep the
enough information to the bank to allow it to obtain user from memorizing and/or recording it elsewhere or otherwise
the user’s secret key. The crucial thing is that in the ever take that knowledge away from the user.
passphrase as a whole, the user retains the secret (private) key (See Figure 1.)
and the ability to obtain it at any point in the future. The app on
Please write
your passphrase --
from memory --
on the form.
...with
your phone
out of view.
Public key;
letter-by-letter commit
to passphrase; and proof
that passphrase is the
private key.
I can see that writing
is from memory, but I
cannot read it.
yes
I’ll shred
Proof that the form.
all answers
are correct.
T
o make this work digitally behind the scenes, OCRed it correctly. The phone then computes the public key for
cryptographic protocols are employed. It works as the user based on the passphrase; and it encrypts, by a special
follows: The user chooses their passphrase and shows blinding,2 each letter position of the passphrase separately.
it to their smartphone camera, making sure that the phone has
2
“Blinding”: Imagine a randomly numbered card inside an opaque envelope that is stamped from the outside with a seal like the signets once used to
seal letters with wax. The impression of the seal embosses the card inside with the signature, but when the envelope is removed, the signer has no way
to determine which specific number was on the card signed. Blinding is a cryptographic technique that conceals a cleartext number by transforming it
into cyphertext in such a way that it can be digitally “embossed” with a signature. Removing the envelope in the analogy is equivalent to the cyphertext
later being decrypted [unblinded] to obtain the now signed form of the cleartext number. This technique, termed “digital blind signature,” was developed
to create the banknote-like anonymity property of eCash 1.0, whereby the bank would apply a signature with a certain fixed monetary value to a blinded
“note” formed by the customer’s device and the customer could later unblind and untraceably spend the note.
04
B
oth public key and encrypted positions are provided follows: during each withdrawal transaction, the user’s phone
over Bluetooth to the bank tablet along with a zero- prepares a message that includes a quantum-secure hash3 of
knowledge proof that the positions together comprise the spendable form of the coin being withdrawn.
O
the private key. Cryptographic “coin flips” between the phone
and tablet select the choice of queries from a very large space of nly the central bank can allow this prepared message to
predefined possibles. The banker asks each selected query, the be included as input to a mix batch of such messages
phone provides a zero-knowledge proof that the list of encrypted corresponding to the respective denomination.
positions—and thus the customer public key, which has already Hence, the corresponding output batch of the mix contains, for
been shown can be reconstructed by the customer from the each coin that can be spent, a quantum-secure authentication
passphrase—is consistent with the customer’s answers. that can automatically be verified when the coin is revealed in
payment. Moreover, the mix maintains the unlinkability between
Quantum-Level Security user account and payment information. (See Figures 4 and 5 and
below on the proposed use of a mix network.)
Against Counterfeiting
I W
hile a blockchain is not strictly needed as a place
f a CBDC were to be counterfeited, as with counterfeiting of to publish the hashes that are output by the mix, it
banknotes, the potential for systemic harm would depend does provide a robust store that can be infeasible
on scale and detectability. With eCash 1.0, such an attack in practice to corrupt. Moreover, if each coin is in effect its own
could be accomplished clandestinely, without triggering an “wallet ID” on the blockchain, then the CBDC could be allowed to
alarm until statistical outflows make the situation evident. For be transferred between wallet IDs on the blockchain. This would
instance, counterfeiters could somehow compromise the central in turn allow use not only of so-called “smart contracts” but also
bank’s computing resources that have access to signing keys. of Liquifinity technology [13].
The central bank could at that point suspend the money, require
customers to deposit all unspent money, and then re-issue new
money, temporarily disrupting the economy.
The Bigger Picture
H T
he decentralization of control over digital currency by
owever, if counterfeiters were to use a quantum computer
the “user-irrevocably-knows-keys” approach introduced
to back-derive the bank’s signing keys from its public
here is related to the decentralization of power by voting
keys, then the replacement system could not simply be
in democracies. Both involve privacy—of voter choice or of who
another eCash 1.0 instance with different keys, as the quantum
spent which cash—but the connection runs deeper. In voting,
computer could break the new keys in effect instantly. Thus, if the
voters may or may not want their vote to be private, such that they
system were not quantum-resistant, the mere claim of a quantum
control who can see how they vote. But society has an interest
attack could arguably require removal of the privacy feature, as
in a stronger property, technically often called “ballot secrecy,”
well as causing even more serious economic disruption.
which is that even if voters want to show others how they voted,
T
they should not be able to do so. This ballot secrecy property is
he solution proposed here need not affect use of
typically enforced by the mandatory physical presence of voters
the system by consumers or commercial banks. The
in booths, visually verified by poll workers and other voters. It
additional protective measures are performed by the
thwarts so-called “improper influence” of voters, which includes
central bank only. The approach even brings with it the potentially
vote buying and coercion.
S
useful advantage of connecting the currency to a blockchain that
can be public. (In any system with this architecture, a commercial imilarly, a user may of course wish to have privacy about
bank can have a separate “out of band” secure channel with where they spend their cash. But society has an interest
the central bank, which would allow it to periodically check a in users themselves always having the keys needed to
hash of the withdrawals and deposits made on its behalf at the
2
spend, recognize, and trace their cash. The techniques presented
central bank and thereby ensure that false requests are not being here allow society to ensure that nobody can improperly usurp
injected.) The essential concept of the quantum resistance is as any user’s access to the keys conferring those abilities.
3
A “cryptographic hash” is the fixed-size output of a standardized cryptographic hash algorithm when it is applied to specific cleartext data. The holder
of the cleartext can easily compute the hash and provide it to the recipient; the holder can also later provide the recipient with the cleartext so that the
recipient can easily check that the hatches match. But the recipient cannot reverse-engineer the cleartext from the hash without breaking the hash
algorithm.
05
System Architecture
A
withdrawal of CBDC by a user would proceed as follows
O
(see Figure 2): Overall, the process is analogous to a
ne primary objective of the overall architecture of the customer withdrawing physical cash from an ATM. A
CBDC scenario mentioned is ensuring that central banks customer authenticates to their commercial bank using that
do not have to interact directly with customers. Rather, particular bank’s authentication and authorization procedures,
authentication is delegated to commercial banks who have the including demonstrating their knowledge of their account keys. The
necessary infrastructure (presumably today including KYC/AML customer’s computer (mobile or otherwise) then computes both the
coin and the blinding factor that cryptographically conceals the coin
support) already in place. Withdrawal and payment protocols are
from the banks. Next, the customer sends the blinded coin to the
the only two that reach the central bank, each through a commercial
commercial bank via an established secure channel together with an
bank as intermediary. Thus, before the central bank signs a coin into
authorization to withdraw the coin and debit the customer’s account.
existence for a commercial bank customer, that customer has been
The commercial bank debits the coin value from the customer’s
authenticated and the corresponding amount withdrawn from the current account and digitally authenticates its authorization of the
customer’s bank account. request on the blinded coin it forwards to the central bank for signing.
N
The central bank deducts the value of the coin from the commercial
ext, we present an architectural-level description of the bank’s account at the central bank, signs the coin, and returns the
workings of the system through the lens of an actual still blinded signature to the commercial bank. Then the commercial
withdrawal transaction, and then, separately, an actual bank forwards the blind signature to the customer’s electronic wallet.
payment transaction. It will be assumed but not shown explicitly that Finally, the customer’s wallet unblinds the signature and stores the
infrastructure providing authentication between banks is in place. newly minted electronic cash in its database. (See Figure 2.)
1 1
2 2
3 3
4
4
2 3 4 5 6
Prepare Send Debit customer Authorize request Deduct from balance of
blinded coins blinded coins account commercial bank and
sign blinded coins
-1
-1
9 8 7
Unblind Forward Return
signed coins signed but still signed but still
blinded coins blinded coins
06
W
hen a user spends CBDC, the process is few hundred milliseconds: The merchant’s commercial bank
analogous to paying a merchant in cash: the
validates that this is one of its merchant customers and forwards
merchant deposits the cash in the merchant’s
the digital coins to the central bank. Since a corrupted customer
own account at a commercial bank and the commercial bank
can deposit the cash in its own account at the central bank. device might attempt to spend the same coins more than once,
the central bank verifies the signature but also checks for
M
ore specifically, the spending of CBDC proceeds as double-spending in its own database(s). If everything is in order,
follows: The customer selects goods they wish to
the central bank credits the commercial bank’s account at the
buy, and the customer’s phone transmits coins in the
central bank and sends confirmation to the commercial bank.
payment amount to the merchant. The merchant’s system then
validates the payment details and passes the coins (together Next, the commercial bank credits the merchant’s account and
with the merchant’s account information) to the merchant’s informs the merchant, so the merchant can release the product
commercial bank. From this point, the process need take only a to the customer. (See Figure 3.)
0 1 2 3 4
Send Check Validate Validate Check for double
payment payment and forward and forward spending
10 9 8 7 6 5
Receive Provide Return Credit Return Credit commercial
goods goods confirmation merchant confirmation bank balance
purchased
+1 +1
07
Overview of the Basic an adversary to compute fractional powers on images under f
Cryptographic Protocol without access to the randomly chosen information used to form
T
c.)
he cryptography that defines the basic system
H
is shown in simplified form in Figure 4. Current ere, the value of 1¢ is assigned public exponent 3 in
standards-based best practices for general use the RSA system with modulus c. The value of 2¢ is
of cryptography, such as for establishing authenticated/ assigned exponent 5, 4¢ exponent 7, 8¢ exponent
private sessions are, however, omitted for clarity, as is 11, and so on; each successive power-of-two denomination
customary in describing higher-level protocols like this.
value is represented by the corresponding next prime number
T
as an exponent, all under modulus c. Thus, 13¢ (13 = 1+4+8)
he eCash 2.0 protocol, introduced here in simplified
corresponds to denominations 1, 4, and 8 cents and exponents
form, is based on the well-known and longstanding
RSA cryptosystem. In RSA, each party creates a public 3, 7, and 11. Since only the bank can form the fractional powers
key by multiplying two very large suitable primes of their own 1/3, 1/7, and 1/v, when the bank is presented with x, y, and z and
secret choice; factoring these two numbers apart is believed x1/3, y1/5 and z1/11, it knows this should be worth 13¢—but of course
infeasible (at least without the help of a quantum computer, it needs to check that x, y, and z have not been deposited before.
a topic covered elsewhere here). The central bank’s public Put differently, the 13-cent example uses a binary number of only
key, c, which it formed in this way, is used to certify CBDC in three bits in length; for each additional bit (corresponding to an
the system. While anyone can raise any number to a counting additional bank secret fractional power) the number of possible
number power modulo the modulus c, only the central bank can payments that can be made doubles. Just by selecting one or
raise numbers to fractional powers modulo c, conferring on it
zero of each of 16 fractional powers, payments of up to $655.36
the exclusive ability to form its digital signature. Such modular
can be made in exact cents. This is because 216 = 65536 cents.
arithmetic, sometimes called clock arithmetic, based on a public
A
modulus c, simply defines “modulo c” as the remainder after
s summarized earlier, blind signatures are used here
dividing out all multiples of c. It allows anyone to verify signatures
to protect user privacy. A user’s smartphone or other
merely by raising them to a public counting-number power.
device can simply “blind” a desired number f(x) by
F
multiplying it by a random number b that it chooses and raises to
or simplicity, user and merchant are here assumed
a denomination power, for example b3 for a 1¢ coin. This blinded
to have a banking relationship with a single commercial
bank of their choice and to be able to move money value f(x)b3 (mod c) can, in exchange for a 1¢ withdrawal, then be
between CBDC and their accounts at that bank. Though not signed in blinded form by the central bank. The central bank uses
made explicit in the architectural discussion above, each user its unique ability to compute the fractional power 1/3, resulting
here also has their own inalienable “secret signing account in {f(x)b3}1/3 (mod c). Because exponentiation distributes over
key” to digitally sign requests for transfer between their multiplication, what the user’s phone gets back equals {f(x)}1/3b
accounts. Such digital signatures authenticate ownership of the (mod c). And since the phone knows b, it can unblind simply by
corresponding account public key and provide durable proof dividing b out, leaving the 1/3 power on f(x) and yielding what
of the withdrawal instruction details and their authorization.
turns out, because of the underlying structure of the modular
A
arithmetic, to be a perfectly unlinkable, unblinded 1¢ coin x| f(x)1/3
pair of numbers worth one cent in the system, x |
that can then be used in payment (See figure 4). After the payment,
f(x)1/3 (mod c), can be verified by anyone simply raising
the second number to the power 3 modulo c and which account the value was withdrawn from remains perfectly
checking that the result equals what is obtained by applying hidden because of the blinding; however, since the payer knows
the public one-way function f() to the first number of the pair, x, the payer can always reveal x (or a property cryptographically
x. (The cryptographic assumptions are that it is infeasible for hidden in x) to allow the beneficiary of the payment to be traced.
08
(1) The customer’s device prepares a blinded coin
with value of 1¢ as follows: (a) it generates x as a
secret random value; (b) it applies the public one-
Customer’s Commercial Bank way function f to x, yielding f(x); (c) it generates a
second secret random value b; (d) it raises b to the
1 f(x)b3 (mod c) power 3 (modulo c), yielding b3 (modulo c); and
(e) it “blinds” the coin by multiplying f(x) times b3
WITHDRAWAL (modulo c). The customer’s device then sends this
2 f(x)1/3b (mod c)
blinded coin to the commercial bank (not shown),
Customer
which forwards it to the central bank. The central
bank cryptographically signs the blinded coin by
raising it to a fractional power of 1/3, which only
Central Bank it can do. (2) The central bank then returns the
3 x | f(x)
1/3
(mod c) signed but still blinded coin to the customer, via
the commercial bank. The customer’s device
PAYMENT unblinds the now signed (valuated) coin by dividing
4 “Payment Accepted”
out b. Later, the customer spends (3) the coin with
a merchant that sends it on to its bank, which
Merchant
forwards it in turn to the central bank. Because
the customer retains the private key formed
Merchant’s Commercial Bank
along with the coin, the customer can always
reveal and prove where they spent that coin. This
greatly reduces the potential for criminal abuse of
Figure 4: The Basic eCash 2.0 Protocol the coin. The spent form includes two numbers,
shown separated by a “|”. The first number is x and
the second is the unblinded signed coin f(x) 1/3
(mod c). The central bank applies f to the first number and cubes the second number
and then verifies that the two results are equal (modulo c). The bank also checks to make sure that the coin has not been previously
spent by consulting a “double-spending database,” not shown, that it maintains by updating to include the x as already spent. Finally
(4) the central bank sends back through the commercial bank and merchant the message that the payment has been accepted.
This blind-signature protocol was invented by the first named author in 1982. In the 1990s, DigiCash implemented it and provided
it to commercial banks, such as Deutsche Bank, that deployed it online connected to their customer’s current accounts [10].
Quantum Resistance and smart contracts or Liquifinity.) Because there are practical one-
A
sense, even quantum computing cannot be used to forge a coin
lso invented by the first named author even earlier, in
already on the list, since the counterfeiter cannot find x from the
1979 [14], was the concept of mix networks, which make
published f(x). This also means that even if a quantum computer
it possible to send virtually untraceable communications.
Here, a mix network is used to preserve privacy while addressing reverse-computes the bank’s private denomination-signing keys
the threat of a quantum computer being used in counterfeiting. from its public keys, it cannot create spendable coins using those
Every coin formed using a one-way function f by any user’s private keys. Only by somehow inserting false payloads into the
device is forwarded through a mix network to be checked against
mix that are not noticed in random checking by customers, could
a database of spent coins by the central bank. Optionally, the
counterfeiters get images in the output database for which they
coin can also be published on a blockchain so that any user can
know the pre-image x. (See Figure 5.) Thus, the total amount of
also check for it (see Fig. 5). (As mentioned earlier, since users
control the hashes of their blinded, unspent coins on that chain, CBDC outstanding becomes a matter of public record on the
they can make peer-to-peer payments directly on chain or use blockchain(s).
09
Customer’s Commercial Bank
1
blockchain
f(x)b3 (mod c) | m1(m2(...(mn[f(x)])...)
WITHDRAWAL
2 f(x)1/3b (mod c) mix network
Customer Combined quantum- f(x)
resistance and double-
spending database
A
Central Bank
"f is applied to
3 x | f(x)1/3 (mod c) x received”
f(x)?
B
PAYMENT “f(x) is searched
4 “Payment Accepted” for in the database”
f(x)
C
Merchant
“If f(x) found,
payment allowed
Merchant’s Commercial Bank and f(x) deleted
from database"
Scalability, Availability, user bases today, like Visa or the major social media platforms.
This is because each transaction coming into the central bank can
and Recoverability be recognized almost immediately as relating to one of several
T
hree questions have interrelated answers: How easy is separate servers that can fully process it, and it can immediately
it to scale the system to accommodate demand as the be dispatched directly to such a server. Fundamentally, what
number of transactions per second needed grows? How makes this possible is that the transactions processed can
can the system be prevented from becoming unavailable and be kept independent of each other. The result is what may be
blocking people from making purchases? What happens if the considered, at least in principle, orders of magnitude more
central bank’s secret signing key were to be compromised by efficient when compared to solutions requiring every transaction
whatever means? to result in consensus of many nodes on a single blockchain. (By
S
contrast, the xx network’s approach to mixing allows the security
calability can use the same transaction-processing benefits of the large number of nodes in its network, but only
“dispatcher,” database “sharding” or website “load requires replication of the computation by five nodes and offers
balancing” techniques employed by systems with large end-to-end latency of roughly two seconds.)
10
S Conclusion
ince the solution is software-only and its use of
A
cryptography modest, the cost of processing an
individual transaction can be low. Performance is also retail CBDC should preserve at least low-value cash-
not an issue: computers of the 1990s were able to handle the like transactions as a privacy-friendly commons
transaction speeds and database sizes in the production eCash under citizens’ individual control. With eCash 2.0,
central banks can provide the privacy consumers have
systems. The valid coins are stored only until spent. Since
shown they care deeply about, while preventing large-scale
transactions are essentially independent of each other, the
abuse, with all the advantages of a state-of-the-art CBDC
amount of additional processing power and bandwidth needed and quantum-resistant security against counterfeiting.
grows by the same amount for each additional spend or deposit
transaction per second. This additional power is simply achieved References
by adding more hardware and sharding; and with so-called
[1] Boar, C. and Wehrli, A. (2021). Ready, steady, go?: Results of the
consistent hashing, hardware additions need not be disruptive. third BIS survey on central bank digital currency, BIS Papers No. 114.
Any underlying database technology can be used, whether
[2] G7. Public policy principles for retail central bank digital currencies
conventional or distributed. (14 October, 2021).
P
[3] G7. Finance Ministers and Central Bank Governors Statement on
ayments can be urgent, withdrawals less so. Each Central Bank Digital Currencies (CBDCs) and Digital Payments (13
October 2021).
payment has one or more digitally signed “serial
numbers” (called x elsewhere here) and so these parts [4] People’s Bank of China. The progress of research & development
of E-CNY in China (July 2021), 3.2.5.
can in principle be checked for “double-spending” by separate
portions of the network. No network can withstand unlimited [5] Bank of Canada, Bank of England, Bank of Japan, European
Central Bank, Federal Reserve, Sveriges Riksbank, Swiss National
attack. But if the network can be divided into parts, and each part Bank, and BIS. Central bank digital currencies: System design and
interoperability (September 2021).
can process some portion of the transactions’ serial numbers,
then transactions can be routed to the parts that can handle their [6] World Economic Forum, Privacy and confidentiality options for
central bank digital currency (November 2021) citing European Central
serial numbers as mentioned. This provides for a kind of graceful Bank Eurosystem. Eurosystem report on the public consultation on a
digital euro. (April 2021).
degradation of service, compared to an all-or-nothing failure,
and can take advantage of geographically distributed servers. [7] Bank of England. Responses to the Bank of England’s March 2020
discussion paper on CBDC. (June 2021).
W
ithdrawals may not be extremely urgent, but they [8] Eurosystem report on the public consultation on a digital euro, op.
cit., p. 19.
provide the bedrock security against counterfeiting.
They can be made a matter of record and available [9] ibid., p. 4 .
to the account owner, so that the owner can recover their [10] See https://chaum.com/ecash/ (webpage with a timeline and
money from their private key. But otherwise, this data should be documents of the development and implementation of eCash 1.0 by
Digicash).
protected doubly, by the commercial bank and the central bank.
[11] Chaum, D., Fiat, A., and Naor, M. Untraceable electronic cash
After double encryption, for instance, the data can be backed up
(extended abstract) Presented at CRYPTO 88 (February 1990).
in multiple media and locations.
[12] Chaum, D. (forthcoming paper) Offline eCash 2.0: Robust offline
I
payments onlineable later. .
f the central-bank signing key(s) is ever compromised,
[13] This technology, developed by the first named author, allows
such as by a quantum computer, a physical attack on data- cryptocurrencies to be traded securely between any two chains peer
center vaults, or perhaps some new algorithm, the combined to peer, without smart contracts or any third-party intermediary. See
https://liquifinity.com/.
double-spending and quantum-security database detailed with
reference to Figure 5 above will prevent counterfeits from being [14] Chaum, D. Untraceable electronic mail, return addresses, and
digital pseudonyms. Communications of the ACM, vol. 24 no. 2,
accepted. February 1981. (Also as UCB/ERL M79/9 22 February 1979.)
11