From 015cf8201907942b6f80dae6a9724e2e8d4aa46c Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Wed, 9 Sep 2015 20:33:34 +0200
Subject: edits

---
 doc/paper/taler.tex | 188 ++++++++++++++++++++++++++++------------------------
 1 file changed, 100 insertions(+), 88 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 706cf70f3..a728471c0 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -18,9 +18,9 @@
 %       'transaction' already when we talk about taxable
 %        transfers of Taler coins and database 'transactions'.
 % - wallet = coins at customer
-% - reserve = currency entrusted to mint waiting for withdrawl
+% - reserve = currency entrusted to mint waiting for withdrawal
 % - deposit = SEPA to mint
-% - withdrawl = mint to customer
+% - withdrawal = mint to customer
 % - spending = customer to merchant
 % - redeeming = merchant to mint (and then mint SEPA to merchant)
 % - refreshing = customer-mint-customer
@@ -403,11 +403,11 @@ information leakage is outside of the scope of this work.
 The customer may use an anonymous communication channel for the
 communication with the mint to avoid leaking IP address information;
 however, the mint will anyway be able to determine the customer's
-identity from the (SEPA) transfer that the customer initiates to
-obtain anonymous digital cash.  The scheme is anonymous
-because the mint will be unable to link the known identity of the
-customer that withdrew anonymous digital currency to the {\em
-  purchase} performed later at the merchant.
+identity from the wire transfer or some other authentication process
+that the customer initiates to withdraw anonymous digital cash.  The
+scheme is anonymous because the mint will be unable to link the known
+identity of the customer that withdrew anonymous digital currency to
+the {\em purchase} performed later at the merchant.
 %  All the mint will be
 %able to confirm is that the customer is {\em one} of its patrons who
 %previously obtained the anonymous digital currency --- and of course
@@ -466,17 +466,22 @@ private {\em master signing key} of the mint and possibly the auditor.
 
 Before a customer can withdraw a coin from the mint, he has to pay the
 mint the value of the coin, as well as processing fees.  This is done
-using other means of payments, such as SEPA transfers~\cite{sepa}.
-The subject line of the transfer must contain {\em withdrawal
-  authorization key}, a public key for digital signatures generated by
-the customer.  When the mint receives a transfer with a public key in
-the subject, it adds the funds to a {\em reserve} identified by the
-withdrawl authorization key.  By signing the withdrawl messages using
-the withdrawl authorization key, the customer can prove to the mint
-that he is authorized to withdraw anonymous digital coins from the
-reserve.  The mint will record the withdrawl messages with the reserve
-record as proof that the anonymous digital coin was created for the
-correct customer.
+using other means of payments, such as wire transfers~\cite{sepa} or
+by having a personal {\em reserve} at the mint (which is equivalent to
+a bank account with a positive balance).  Taler assumes that the
+customer has a {\em withdrawal authorization key} to identify himself
+as authorized to withdraw funds from the reserved.  By signing the
+withdrawal request messages using the withdrawal authorization key,
+the customer can prove to the mint that he is the individual
+authorized to withdraw anonymous digital coins from the reserve.  The
+mint will record the withdrawal messages with the reserve record as
+proof that the anonymous digital coin was created for the correct
+customer.  We note that the specifics of how the customer
+authenticates to the mint are orthogonal to the rest of the system,
+and multiple methods can be supported. To put it differently, unlike
+modern cryptocurrencies like BitCoin, Taler's design simply
+acknowledges that primitive accumulation~\cite{engels1844} predates
+the system and that a secure method to authenticate owners exists.
 
 After a coin is minted, the customer is the only entity that knows the
 private key of the coin, making him the \emph{owner} of the coin.  The
@@ -495,16 +500,11 @@ private key.  A merchant can then transfer this permission of the
 coin's owner to the mint to obtain the amount in traditional currency.
 If the customer is cheating and the coin was already spent, the mint
 provides cryptographic proof of the fraud to the merchant, who will
-then refuse the transaction.
-%  The mint is typically expected
-%to transfer the funds to the merchant using a SEPA transfer or similar
-%methods appropriate to the domain of the traditional currency.
+then refuse the transaction.  The mint is typically expected to
+transfer the funds to the merchant using a wire transfer or by
+crediting the merchant's individual account, depending on what is
+appropriate to the domain of the traditional currency.
 
-%The mint needs to ensure that a coin can only be spent once.  This is
-%done by storing the public keys of all deposited coins (together with
-%the deposit request and the owner's signature confirming the
-%transaction).  The mint's state can be limited as coins signed with
-%expired coin sigining keys do not have to be retained.
 
 \paragraph{Partial spending.}
 
@@ -514,13 +514,13 @@ spending of coins.  Consequently, the mint the must not only store the
 identifiers of spent coins, but also the fraction of the coin that has
 been spent.
 
-%\paragraph{Online checks.}
-%
-%For secure transactions (non-microdonations), the merchant is expected
-%to perform an online check to detect double-spending. In the simplest
-%case, the merchant simply directly confirms the validity of the
-%deposit permission signed by the coin's owner with the mint, and then
-%proceeds with the contract.
+\paragraph{Online checks.}
+
+For secure transactions, the merchant is expected to perform an online
+check to detect double-spending.  Thus, the merchant must deposit the
+coin with the mint (and validate the signature from the mint
+confirming the validity of the transaction) before proceeding with its
+business logic.
 
 
 \subsection{Refreshing Coins}
@@ -569,13 +569,14 @@ in relation to the value of the melted coins.
 
 % In this section, we describe the protocols for Taler in detail.
 
-For the sake of brevity, we do not specifically state that the
-recipient of a signed message always first checks that the signature
-is valid.  Also, whenever a signed message is transmitted, it is
-assumed that the receiver is told the public key (or knows it from the
-context) and that the signature contains additional identification as
-to the purpose of the signature (such that it is not possible to
-use a signature from one protocol step in a different context).
+For the sake of brevity, we assume that a recipient of a signed
+message always first checks that the signature is valid, even though
+this is not explicitly stated below.  Also, whenever a signed message
+is transmitted, it is assumed that the receiver is told the public key
+(or knows it from the context) and that the signature contains
+additional identification as to the purpose of the signature (such
+that it is not possible to use a signature from one protocol step in a
+different context).
 
 When the mint signs messages (not coins), an {\em online message
   signing key} of the mint is used.  The mint's long-term offline key
@@ -584,7 +585,7 @@ message signing key of the mint.  The mint's long-term offline key is
 assumed to be well-known to both customers and merchants, for example
 because it is certified by the auditors.
 
-As we are dealing with financial transactions, we explicitly state
+As we are dealing with financial transactions, we explicitly describe
 whenever entities need to safely commit data to persistent storage.
 As long as those commitments persist, the protocol can be safely
 resumed at any step.  Commitments to disk are cummulative, that is an
@@ -665,7 +666,7 @@ $\widetilde{C} := S_K(C_p)$:
   assume that one coin is sufficient.)
 
   The customer then generates a \emph{deposit-permission} $\mathcal{D} :=
-  S_c(\widetilde{C}, m, f, H(a), H(p,r), M_p)$ 
+  S_c(\widetilde{C}, m, f, H(a), H(p,r), M_p)$
   and sends $\langle \mathcal{D}, D_i\rangle$ to the merchant,
   where $D_i$ is the mint which signed $K$.
 \item The merchant gives $(\mathcal{D}, p, r)$ to the mint, revealing his
@@ -722,7 +723,7 @@ execute the coin refreshing protocol with the mint.
 %\end{figure}
 
 
-\subsection{Refreshing}
+\subsection{Refreshing} \label{sec:refreshing}
 
 The following protocol is executed in order to refresh a coin $C'$ of
 denomination $K$ to a fresh coin $\widetilde{C}$ with the same
@@ -784,40 +785,48 @@ This allows the owner of the old coin to also obtain the private key
 of the new coin, even if the refreshing protocol was illicitly
 executed by another party who learned $C'_s$ from the old owner.
 
+\subsection{Refunds}
+
+The refresh protocol offers an easy way to enable refunds to
+customers, even if they are anonymous.  Refunds can be supported
+by including a public signing key of the mechant in the transaction
+details, and having the customer keep the private key of the spent
+coins on file.
+
+Given this, the merchant can simply sign a {\em refund confirmation}
+and share it with the mint (and the customer).  Assuming the mint has
+a way to recover the funds from the merchant (or simply not performed
+the wire transfer yet), the mint can simply add the value of the
+refunded transaction back to the original coin, re-enabling those
+funds to be spent again by the original customer.
+
+The (anonymous) customer -- but nobody else -- can then use the
+refresh protocol to melt the refunded coin and create a fresh coin
+that is unlinkable to the refunded transaction.
+
 
 \section{Discussion}
 
 \subsection{Offline Payments}
 
-Chaum's original proposals for anonymous digital cash avoided the
-locking and online spending steps detailed in this proposal by
+Chaum's original proposals for anonymous digital cash avoided the need
+for online interactions with the mint to detect double spending by
 providing a means to deanonymize customers involved in
 double-spending.  We believe that this is problematic as the mint or
 the merchant will then still need out-of-band means to recover funds
 from the customer, which may be impossible in practice.  In contrast,
 in our design only the mint may try to defraud the other participants
-and disappear.  While this is still a risk, this is likely manageable,
-especially compared to recovering funds via the court system from
-customers.
-
-
-\subsection{Bona-fide microdonations}
-
-Evidently the customer can ``cheat'' by aborting the transaction in
-Step 3 of the microdonation protocol if the outcome is unfavourable ---
-and repeat until he wins.  This is why Taler is suitable for
-microdonations --- where the customer voluntarily contributes ---
-and not for micropayments.
-
-Naturally, if the donations requested are small, the incentive to
-cheat for minimal gain should be quite low.  Payment software could
-embrace this fact by providing an appeal to conscience in form of an
-option labeled ``I am unethical and want to cheat'', which executes
-the dishonest version of the payment protocol.
-
-If an organization detects that it cannot support itself with
-microdonations, it can always choose to switch to the macropayment
-system with slightly higher transaction costs to remain in business.
+and disappear.  While this is still a risk, and regular financial
+audits are required to protect against it, this is more manageable and
+significantly cheaper compared to recovering funds via the court
+system from customers.
+
+Chaum's method for offline payments would also be incompatible with
+the refreshing protocol (Section~\ref{sec:refreshing}) which enables
+the crucial feature of giving unlinkable change.  The reason is that
+if the owner's identity were embedded in coins, it would be leaked to
+the mint as part of the reveal operation in the cut-and-choose
+operation of the refreshing protocol.
 
 \subsection{Merchant Tax Audits}
 
@@ -872,25 +881,12 @@ transactions.
 In this appendix we detail various optional features that can
 be added to the basic protocol.
 
-\subsection{Refunds}
-
-The refresh protocol offers an easy way to enable refunds to
-customers, even if they are anonymous.  Refunds can be supported
-by including a public signing key of the mechant in the transaction
-details, and having the customer keep the private key of the spent
-coins on file.  
-
-Given this, the merchant can simply sign a {\em refund confirmation}
-and share it with the mint (and the customer).  Assuming the mint has
-a way to recover the funds from the merchant (or simply not performed
-the transfer yet), the mint can simply add the value of the refunded
-transaction back to the original coin, re-enabling those funds to be
-spent again by the original customer.
-
-The (anonymous) customer -- but nobody else -- can then use the
-refresh protocol to melt the refunded coin and create a fresh coin
-that is unlinkable to the previous transaction.
-
+However, we note that Taler's transaction costs are expected to be so
+low that these features are not particularly useful, as they are about
+reducing interactions with the mint to reduce costs.  In particular,
+we expect that transactions with amounts below Taler's transaction
+costs to be economically meaningless.  Nevertheless, we document
+various ways how this could be achieved.
 
 \subsection{Incremental spending}
 
@@ -1079,7 +1075,7 @@ coin by offering a coin that has already been spent.  This kind of
 fraud would only be detected if the customer actually lost the coin
 flip, and at this point the merchant might not be able to recover from
 the loss.  A fradulent anonymous customer may run the protocol using
-already spent coins until the coin flip is in his favor.  
+already spent coins until the coin flip is in his favor.
 
 As with incremental spending, lock permissions could be used to ensure
 that the customer cannot defraud the merchant by offering a coin that
@@ -1112,4 +1108,20 @@ The following steps are executed for microdonations with upgrade probability $p$
     with $H(r_c)$.
 \end{enumerate}
 
+Evidently the customer can ``cheat'' by aborting the transaction in
+Step 3 of the microdonation protocol if the outcome is unfavourable ---
+and repeat until he wins.  This is why Taler is suitable for
+microdonations --- where the customer voluntarily contributes ---
+and not for micropayments.
+
+Naturally, if the donations requested are small, the incentive to
+cheat for minimal gain should be quite low.  Payment software could
+embrace this fact by providing an appeal to conscience in form of an
+option labeled ``I am unethical and want to cheat'', which executes
+the dishonest version of the payment protocol.
+
+If an organization detects that it cannot support itself with
+microdonations, it can always choose to switch to the macropayment
+system with slightly higher transaction costs to remain in business.
+
 \end{document}
-- 
cgit v1.2.3


From 497f8471ea61a14896559a72a67f44e4dff345e2 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Wed, 9 Sep 2015 20:35:27 +0200
Subject: edits

---
 doc/paper/taler.tex | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index e3fb83592..fb03fb36b 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -938,14 +938,16 @@ protocol may finally enable modern society to upgrade to proper
 electronic wallets with efficient, secure and privacy-preserving
 transactions.
 
-\subsection*{Acknowledgements}
+% commented out for anonymized submission
+%\subsection*{Acknowledgements}
 
-This work was supported by a grant from the Renewable Freedom Foundation.
+%This work was supported by a grant from the Renewable Freedom Foundation.
 % FIXME: ARED?
-We thank Tanja Lange and Dan Bernstein for feedback on an earlier
-version of this paper, Nicolas Fournier for implementing and running
-some performance benchmarks, and Richard Stallman, Hellekin Wolf,
-Jacob Appelbaum for productive discussions and support.
+%We thank Tanja Lange and Dan Bernstein for feedback on an earlier
+%version of this paper, Nicolas Fournier for implementing and running
+%some performance benchmarks, and Richard Stallman, Hellekin Wolf,
+%Jacob Appelbaum for productive discussions and support.
+
 
 \bibliographystyle{alpha}
 \bibliography{taler}
-- 
cgit v1.2.3


From fa27e3f204d56ff23df11c9bf7f25b66dd3a457b Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Wed, 16 Sep 2015 09:37:47 +0200
Subject: ref

---
 doc/paper/taler.tex | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index fb03fb36b..f954d1cc7 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -11,7 +11,8 @@
 \usetikzlibrary{positioning}
 \usetikzlibrary{calc}
 
-
+% Relate to:
+% http://fc14.ifca.ai/papers/fc14_submission_124.pdf
 
 % Terminology:
 % - SEPA-transfer -- avoid 'SEPA transaction' as we use
-- 
cgit v1.2.3


From a8816b77702876bf89f0c0c5f98261d1e63da79a Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Thu, 24 Sep 2015 11:40:23 +0200
Subject: edits to Taler paper, trying to clarify/improve writing/structure

---
 doc/paper/taler.tex | 378 +++++++++++++++++++++++++++++-----------------------
 1 file changed, 214 insertions(+), 164 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index f954d1cc7..199de85e4 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -50,19 +50,18 @@
 This paper introduces Taler, a Chaum-style digital currency using
 blind signatures that enables anonymous payments while ensuring that
 entities that receive payments are auditable and thus taxable.  Taler
-differs from Chaum's original proposal in that customers can never defraud anyone,
-merchants can only fail to deliver the merchandise to the customer,
-and mints can be fully audited. Consequently, enforcement of honest
-behavior is better and more timely than with Chaum, and is at least as
-strict as with legacy credit card payment systems that do not provide
-for privacy.  Furthermore, Taler allows fractional and incremental
-payments, and even in this case is still able to guarantee
-unlinkability of transactions via a new coin refreshing protocol.
-Finally, Taler also supports microdonations using probabilistic
-transactions.  We argue that Taler provides a secure digital currency
-for modern liberal societies as it is a flexible, libre and efficient
-protocol and adequately balances the state's need for monetary control
-with the citizen's needs for private economic activity.
+differs from Chaum's original proposal in that customers can never
+defraud anyone, merchants can only fail to deliver the merchandise to
+the customer, and mints can be fully audited. Consequently,
+enforcement of honest behavior is better and more timely than with
+Chaum, and is at least as strict as with legacy credit card payment
+systems that do not provide for privacy.  Furthermore, Taler allows
+fractional payments, and even in this case is still able to guarantee
+unlinkability of transactions via a new coin refreshing protocol.  We
+argue that Taler provides a secure digital currency for modern liberal
+societies as it is a flexible, libre and efficient protocol and
+adequately balances the state's need for monetary control with the
+citizen's needs for private economic activity.
 \end{abstract}
 
 \section{Introduction}
@@ -79,14 +78,50 @@ states where economic activity is based largely on coins, paper money
 or even barter.  Here, the state is often unable to effectively
 monitor or tax economic activity, and this limits the ability of the
 state to shape the society.  As bribery is virtually impossible to
-detect, it is widespread and not limited to social elites.
+detect, corruption is widespread and not limited to social elites.
 ZeroCoin~\cite{miers2013zerocoin} is an example for translating such
 an economy into the digital realm.
 
-Taler is supposed to offer a middleground between an authoritarian
-state in total control of the population and weak states with almost
-anarchistic economies.  Specifically, we believe that a liberal
-democracy needs a payment system with the following properties:
+This paper describes Taler, a simple and practical payment system for
+a modern social-liberal society, which is not be served well by
+current payment systems which enable either an authoritarian state in
+total control of the population, or create weak states with almost
+anarchistic economies.
+
+The Taler protocol is havily based on ideas from
+Chaum~\cite{1983blind} and also follows Chaum's basic architecture of
+customer, merchant and mint (Figure~\ref{fig:cmm}). The two designs
+share the key first step where the {\em customer} withdraws digital
+{\em coins} from the {\em mint} with unlinkability provided via blind
+signatures.  The coins can then be spend at a {\em merchant} who {\em
+  deposits} them at the mint.  Taler uses online detection of
+double-spending, thus assuring the merchant instantly that a
+transaction is valid.
+
+\begin{figure}[h]
+\centering
+\begin{tikzpicture}
+ \tikzstyle{def} = [node distance= 5em and 7em, inner sep=1em, outer sep=.3em];
+ \node (origin) at (0,0) {};
+ \node (mint) [def,above=of origin,draw]{Mint};
+ \node (customer) [def, draw, below left=of origin] {Customer};
+ \node (merchant) [def, draw, below right=of origin] {Merchant};
+ \node (auditor) [def, draw, above right=of origin]{Auditor};
+
+ \tikzstyle{C} = [color=black, line width=1pt]
+
+ \draw [<-, C] (customer) -- (mint) node [midway, above, sloped] (TextNode) {withdraw coins};
+ \draw [<-, C] (mint) -- (merchant) node [midway, above, sloped] (TextNode) {deposit coins};
+ \draw [<-, C] (merchant) -- (customer) node [midway, above, sloped] (TextNode) {spend coins};
+ \draw [<-, C] (mint) -- (auditor) node [midway, above, sloped] (TextNode) {verify};
+
+\end{tikzpicture}
+\caption{Taler's system model for the payment system is based on Chaum~\cite{chaum1983blind}.}
+\label{fig:cmm}
+\end{figure}
+
+Taler was designed for use in a modern social-liberal society, which we
+believe needs a payment system with the following properties:
 
 \begin{description}
   \item[Customer Anonymity] It must be impossible for mints, merchants
@@ -103,7 +138,7 @@ democracy needs a payment system with the following properties:
     %Taxation is neccessary for the state to
     %provide legitimate social functions, such as education.  Thus, a payment
     %system must facilitate sales, income and transaction taxes.
-    This specifically means that it must be able to audit merchants (or
+    This specifically means that the state must be able to audit merchants (or
     generally anybody receiving money), and thus the receiver of
     electronic cash must be easily identifiable.
     %non-anonymous, as this would enable tax fraud.
@@ -126,7 +161,7 @@ democracy needs a payment system with the following properties:
  %   protocols such as HBCI/FinTAN.
     The digital currency should be
     tied 1:1 to existing currencies (such as EUR or USD) to avoid
-    exposing users to unnecessary risks from currency fluctuations.
+    exposing citizens to unnecessary risks from currency fluctuations.
     Moreover, the system must have a free software reference
     implementation and an open protocol standard.
 %    The protocol should
@@ -135,99 +170,52 @@ democracy needs a payment system with the following properties:
     costs and environmental impact of the payment system, it must
     avoid the reliance on expensive and ``wasteful'' computations
     such as proof-of-work.
-  \item[Large Payments and Microdonations] The payment system needs to
-    handle large payments in a reliable manner.  Furthermore, for
-    microdonations the system should allow sacrificing reliability to
-    achieve economic viability.
+  \item[Fractional payments] The payment system needs to handle both
+    small and large payments in an efficient and reliable manner.
+    Thus, coins cannot just be issued in the smallest unit of currency,
+    and a mechanism to give {\em change} must be provided to ensure
+    that customers with sufficient total funds can always spend them.
+    For example, a customer may want to pay \eur{49,99} using a
+    \eur{100,00} coin.  The system must then support giving change in
+    the form of say two fresh \eur{0,01} and \eur{50,00} coins.  Those
+    coins must be {\em unlinkable}: an adversary should not be able to
+    relate transactions with either of the new coins to the original
+    \eur{100,00} coin or transaction or the other change being generated.
 \end{description}
 
-Taler builds on ideas from Chaum~\cite{chaum1983blind}, who proposed a
-digital currency system that would provide (some) customer anonymity
-while disclosing the identity of the merchants.  Chaum's digital cash
-system had some limitations and ultimately failed to be widely
-adopted.  In our assessment, key reasons include:
-
-\begin{itemize}
- \item The use of patents to protect the technology; a payment system
-   must be libre --- free software --- to have a chance for widespread
-   adoption.
- \item The use of off-line payments and thus deferred detection of
-   double-spending, which could require the mint to attempt to recover
-   funds from customers via the legal system.  This creates a
-   significant business risk for the mint, as the system is not
-   self-enforcing from the perspective of the mint.  In 1983 off-line
-   payments might have been a necessary feature.  However, today
-   requiring network connectivity is feasible and avoids the business
-   risks associated with deferred fraud detection.
- \item % In addition to the risk of legal disputes with fradulent
-   % merchants and customers,
-   Chaum's published design does not clearly
-   limit the financial damage a mint might suffer from the
-   disclosure of its private online signing key.
-% \item Chaum did not support fractional payments, and Brand's
-%   extensions for fractional payments broke unlinkability and thus
-%   limited anonymity.  Chaum also did not support microdonations,
-%   leaving an opportunity for expanding payments into additional areas
-%   unexplored.
-% \item Chaum's system was implemented at a time where the US market
-%   was still dominated by paper checks and the European market was
-%   fragmented into dozens of currencies.  Today, SEPA provides a
-%   unified currency and currency transfer method for most of Europe,
-%   significantly lowering the barrier to entry into this domain for
-%   a larger market.
-\end{itemize}
-
-This paper describes Taler, a simple and practical payment with the
-above goals in mind.  The basic idea is to use Chaum's model of
-customer, merchant and mint (Figure~\ref{fig:cmm}) where the customer
-withdraws digital currency from the mint with unlinkability provided
-via blind signatures.  In contrast to Chaum, Taler uses online
-detection of double-spending, thus ensuring the merchant instantly
-that a transaction is valid.  Instead of using cryptographic methods
-to enable fractional payments, the customer can simply include
-the fraction of a coin's value that is to be paid to the merchant in
-his message to the merchant.
-
-
-\begin{figure}[h]
-\centering
-\begin{tikzpicture}
- \tikzstyle{def} = [node distance= 5em and 7em, inner sep=1em, outer sep=.3em];
- \node (origin) at (0,0) {};
- \node (mint) [def,above=of origin,draw]{Mint};
- \node (customer) [def, draw, below left=of origin] {Customer};
- \node (merchant) [def, draw, below right=of origin] {Merchant};
- \node (auditor) [def, draw, above right=of origin]{Auditor};
-
- \tikzstyle{C} = [color=black, line width=1pt]
-
- \draw [<-, C] (customer) -- (mint) node [midway, above, sloped] (TextNode) {withdraw coins};
- \draw [<-, C] (mint) -- (merchant) node [midway, above, sloped] (TextNode) {deposit coins};
- \draw [<-, C] (merchant) -- (customer) node [midway, above, sloped] (TextNode) {spend coins};
- \draw [<-, C] (mint) -- (auditor) node [midway, above, sloped] (TextNode) {verify};
-
-\end{tikzpicture}
-\caption{Taler's system model for the payment system is based on Chaum~\cite{chaum1983blind}.}
-\label{fig:cmm}
-\end{figure}
+Instead of using cryptographic methods like restrictive blind
+signatures to achieve divisiblity, Taler's fractional payments use a
+simpler, more powerful mechanism.  In Taler, a coin is not simply a
+unique random token, but a private key.  Thus, the transfer of a coin
+can be performed by signing a message using this private key.  Thus,
+the customer can simply specify the fraction of a coin's value that is
+to be paid to the merchant in the cryptographically signed deposit
+message given to the merchant.  A key contribution of Taler is the
+{\em refresh} protocol, which enables a customer to exchange the
+residual value of a coin for fresh coins, thereby providing unlinkable
+change.  Using online checks, the mint can trivially ensure that all
+transactions involving the same coin do not exceed the total value of
+the coin.
 
 Online fraud detection can create problems if the network fails during
 the initial steps of a transaction.  For example, a law enforcement
 agency might try to entrap a customer by offering illicit goods and
-then aborting the transaction after learning the public key of the
-coin.  If the customer were to then later spend that coin on a
-purchase with shipping, the law enforcement agency could link the two
-transactions and might be able to use the shipping to deanonymize the
-customer.  Similarly, fractional payments also lead to the
-possibility of customers wanting to legitimately use the same coin
-twice.  Taler addresses this problem by allowing customers to {\em
-  refresh} coins.  Refreshing means that a customer is able to
-exchange one coin for a fresh coin, with the old and the new coin
-being unlinkable (except for the customer himself).  Taler ensures
-that the {\em entity} of the user owning the new coin is the same as the
-entity of the user owning the old coin, thus making sure that the
-refreshing protocol cannot be abused for money laundering or other
-illicit transactions.
+then cancelling the transaction after learning the public key of the
+coin.  This is equivalent to a benign merchant giving a dissatisfied
+(anonymous) customer a {\em refund} by sending a message affirming
+the cancellation.
+
+If the customer later spends the refunded coin on a purchase with
+shipping, the state can link the two transactions and might be able to
+use the shipping address to deanonymize the customer.  As with support
+for fractional payments, Taler addresses this problem by allowing
+customers to refresh coins, thereby destroying the link between the
+refunded (or aborted) transaction and the coin.
+
+Taler ensures that the {\em entity} of the user owning the new coin is
+the same as the entity of the user owning the old coin, thus making
+sure that the refreshing protocol cannot be abused for money
+laundering or other illicit transactions.
 
 
 \section{Related Work}
@@ -268,24 +256,75 @@ irredeemable problems inherent in these systems:
     currency exchange and exascerbates the problems with currency fluctuations.
 \end{itemize}
 
+GreenCoinX\footnote{\url{https://www.greencoinx.com/}} is a more
+recent AltCoin where the company promises to identify the owner of
+each coin via e-mail addresses and phone numbers.  While it is unclear
+from their technical description how this identification would be
+enforced against a determined adversary, the resulting payment system
+would also merely impose a totalitarian financial panopticon on a
+BitCoin-style money supply and transaction model, thus largely
+combining what we would consider to be the drawbacks of these existing
+systems.
+
 \subsection{Chaum-style electronic cash}
 
+Taler builds on ideas from Chaum~\cite{chaum1983blind}, who proposed a
+digital payment system that would provide (some) customer anonymity
+while disclosing the identity of the merchants.  Chaum's digital cash
+(DigiCash) system had some limitations and ultimately failed to be widely
+adopted.  In our assessment, key reasons for DigiCash's failure that
+Taler avoids include:
+
+\begin{itemize}
+ \item The use of patents to protect the technology; a payment system
+   must be libre --- free software --- to have a chance for widespread
+   adoption.
+ \item The use of off-line payments and thus deferred detection of
+   double-spending, which could require the mint to attempt to recover
+   funds from customers via the legal system.  This creates a
+   significant business risk for the mint, as the system is not
+   self-enforcing from the perspective of the mint.  In 1983 off-line
+   payments might have been a necessary feature.  However, today
+   requiring network connectivity is feasible and avoids the business
+   risks associated with deferred fraud detection.
+ \item % In addition to the risk of legal disputes with fradulent
+   % merchants and customers,
+   Chaum's published design does not clearly
+   limit the financial damage a mint might suffer from the
+   disclosure of its private online signing key.
+ \item Chaum did not support fractional payments or refunds without
+   breaking customer anonymity.
+%, and Brand's
+%   extensions for fractional payments broke unlinkability and thus
+%   limited anonymity.
+% \item Chaum's system was implemented at a time where the US market
+%   was still dominated by paper checks and the European market was
+%   fragmented into dozens of currencies.  Today, SEPA provides a
+%   unified currency and currency transfer method for most of Europe,
+%   significantly lowering the barrier to entry into this domain for
+%   a larger market.
+\end{itemize}
+
 Chaum's original digital cash system~\cite{chaum1983blind} was
-extended by Brands~\cite{brands1993efficient} with the ability to
-perform fractional payments; however, the transactions performed with
-the same coin then become linkable.
+extended by Brands~\cite{brands1993efficient} with the ability to {\em
+  divide} coins and thus spend (certain) fractions of a coin using
+restrictive blind signatures.  Compared to Taler, performing
+fractional payments is cryptographically way more expensive and
+moreover the transactions performed with ``divisions'' from the same
+coin do become linkable.
 %
 %Some argue that the focus on technically perfect but overwhelmingly
 %complex protocols, as well as the the lack of usable, practical
 %solutions lead to an abandonment of these ideas by
 %practitioners~\cite{selby2004analyzing}.
 %
+
 To our knowledge, the only publicly available effort to implement
-Chaum's idea is
-Opencoin~\cite{dent2008extensions}.  However,
-Opencoin seems to be neither actively developed nor used, and it is
-not clear to what degree the implementation is even complete.  Only a
-partial description of the Opencoin protocol is available to date.
+Chaum's idea is Opencoin~\cite{dent2008extensions}.  However, Opencoin
+seems to be neither actively developed nor used, and it is not clear
+to what degree the implementation is even complete.  Only a partial
+description of the Opencoin protocol is available to date.
+
 
 \subsection{Peppercoin}
 
@@ -313,14 +352,14 @@ constructions to provide unlinkability, online fraud detection and
 taxability.
 
 As with Chaum, the Taler system comprises three principal types of
-actors: The \emph{customer} is interested in receiving goods or
-services from the \emph{merchant} in exchange for payment.  When
-making a transaction, both the customer and the merchant must agree on
-the same \emph{mint}, which serves as an intermediary for the
-financial transaction between the two.  The mint is responsible for
-allowing the customer to obtain the anonymous digital currency and for
-enabling the merchant to convert the anonymous digital currency back
-to some traditional currency.
+actors (Figure~\ref{fig:cmm}): The \emph{customer} is interested in
+receiving goods or services from the \emph{merchant} in exchange for
+payment.  When making a transaction, both the customer and the
+merchant must agree on the same \emph{mint}, which serves as an
+intermediary for the financial transaction between the two.  The mint
+is responsible for allowing the customer to obtain the anonymous
+digital currency and for enabling the merchant to convert the
+anonymous digital currency back to some traditional currency.
 
 \subsection{Security model}
 
@@ -362,63 +401,72 @@ After all, without instrusive measures to take away control of the
 computing platform from its users, copying an electronic wallet from
 one computer to another can hardly be prevented by a payment system.
 Furthermore, it would also hardly be appropriate to tax the moving of
-funds between two computers owned by the same individual.  We thus
+funds between two computers owned by the same entity.  We thus
 need to clarify which kinds of transfers we expect to tax.
 
 Taler is supposed to ensure that the state can tax {\em transactions}.
-We define a transaction as the transfer of funds between {\em mutually
-  distrustful} entities.  Two entities are assumed to be mutually
-distrustful if they are unwilling to share control over assets.  If a
-private key is shared between two entities, then both entities have
-equal access to the credentials represented by the private key.  In a
-payment system this means that either entity could spent the
-associated funds.  Assuming the payment system has effective
-double-spending detection, this means that either entity has to
-constantly fear that the funds might no longer be available to it.
-Thus, ``transferring'' funds by sharing a private key implies that
-receiving party must trust the sender.  In Taler, making funds
-available by sharing a private key and thus sharing control is {\bf
-  not} considered a {\em transaction} and thus {\bf not} recorded for
-taxation.
-
 A {\em transaction} is a transfer where it is assured that one entity
 gains control over funds while at the same time another entity looses
-control over those funds.  Taler ensures taxability only when some
-entity acquires exclusive control over digital coins.  For
-transactions, the state can obtain information from the mint (or the
-bank) that identifies the entity that received the digital coins as
-well as the exact value of those coins.  Taler also allows the mint
-(and thus the state) to learn the value of digital coins withdrawn by
-a customer --- but not how, where or when they were spent.  Finally,
-to enable audits, the current balance and profits of the mint are also
-easily determined.
+control over those funds.  We further restrict transactions to apply
+only to the transfer of funds between {\em mutually distrustful}
+entities.  Two entities are assumed to be mutually distrustful if they
+are unwilling to share control over coins.  If a private key is shared
+between two entities, then both entities have equal access to the
+credentials represented by the private key.  In a payment system this
+means that either entity could spent the associated funds.  Assuming
+the payment system has effective double-spending detection, this means
+that either entity has to constantly fear that the funds might no
+longer be available to it.  Thus, sharing coins by copying a private
+key implies mutual trust between the two parties, in which case Taler
+will treat them as the same entity.  In Taler, making funds available
+by copying a private key and thus sharing control is {\bf not}
+considered a {\em transaction} and thus {\bf not} recorded for
+taxation.
+
+Taler ensures taxability only when some entity acquires exclusive
+control over the value of digital coins, which requires an interaction
+with the mint.  For such transactions, the state can obtain
+information from the mint (or the bank) that identifies the entity
+that received the digital coins as well as the exact value of those
+coins.  Taler also allows the mint (and thus the state) to learn the
+value of digital coins withdrawn by a customer --- but not how, where
+or when they were spent.
 
 \subsection{Anonymity}
 
 An anonymous communication channel (e.g. via Tor~\cite{tor-design}) is
 used for all communication between the customer and the merchant.
-Thus, the customer can remain anonymous; however, the system does reveal
-that the customer is one of the patrons of the mint.  Naturally, the
-customer-merchant operation might leak other information about the
-customer, such as a shipping address.  Such purchase-specific
-information leakage is outside of the scope of this work.
+Thus, the customer can remain anonymous limited only by the anonymous
+communication channel; however, the payment system does additionally
+reveal that the customer is one of the patrons of the mint.
+Naturally, the customer-merchant business operation might leak other
+information about the customer, such as a shipping address.
+Information leakage from shipping is in theory avoidable~\cite{apod}.
+Nevertheless, for Taler as a payment system, information leakage
+specific to the business logic is outside of the scope of the design.
 
 The customer may use an anonymous communication channel for the
 communication with the mint to avoid leaking IP address information;
 however, the mint will anyway be able to determine the customer's
 identity from the wire transfer or some other authentication process
-that the customer initiates to withdraw anonymous digital cash.  The
-scheme is anonymous because the mint will be unable to link the known
-identity of the customer that withdrew anonymous digital currency to
-the {\em purchase} performed later at the merchant.
-%  All the mint will be
-%able to confirm is that the customer is {\em one} of its patrons who
-%previously obtained the anonymous digital currency --- and of course
-%that the coin was not spent before.
+that the customer initiates to withdraw anonymous digital cash.  In
+fact, this is desirable as there might be rules and regulations
+designed to limit the amount of anonymous digital cash that an
+individual customer can withdraw in a given time period, similar to
+how states today sometimes impose limits on cash
+withdrawals~\cite{france2015cash,greece2015cash}.  Taler is only
+anonymous with respect to {\em payments}, as the mint will be unable
+to link the known identity of the customer that withdrew anonymous
+digital currency to the {\em purchase} performed later at the
+merchant.  In this respect, Taler provides exactly the same scheme for
+unconditional anonymous payments as was proposed by
+Chaum~\cite{chaum1983blind,chaum1990untraceable} over 30 years ago.
 
 While the customer thus has anonymity for his purchase, the mint will
-always learn the merchant's identity (which is necessary for
-taxation), and thus the merchant has no reason to anonymize his
+always learn the merchant's identity in order to credit the merchant's
+account.  This is also necessary for taxation, as Taler is supposed
+to make information about funds received by any entity transparent
+to the state.  The merchant has thus no reason to anonymize his
 communication with the mint.
 % Technically, the merchant could still
 %use an anonymous communication channel to communicate with the mint.
@@ -934,7 +982,9 @@ We have presented an efficient electronic payment system that
 simultaneously addresses the conflicting objectives created by the
 citizen's need for privacy and the state's need for taxation.  The
 coin refreshing protocol makes the design flexible and enables a
-variety of payment methods.  The libre implementation and open
+variety of payment methods.  The current balance and profits of the
+mint are also easily determined, thus audits can be used to ensure
+that the mint operates correctly.  The libre implementation and open
 protocol may finally enable modern society to upgrade to proper
 electronic wallets with efficient, secure and privacy-preserving
 transactions.
-- 
cgit v1.2.3


From 43ff6d447a62b74e17c7370e7d9cfc0f5b2e5b59 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Thu, 24 Sep 2015 12:22:20 +0200
Subject: expand security discussion in paper

---
 doc/paper/taler.tex | 55 +++++++++++++++++++++++++++++++++++------------------
 1 file changed, 37 insertions(+), 18 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 199de85e4..c504e843f 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -923,6 +923,31 @@ that is unlinkable to the refunded transaction.
 
 \section{Discussion}
 
+Taler's security is largely equivalent to that of Chaum's original
+design without online checks (and without the cut-and-choose
+revelation of double-spending customers for offline spending).  We
+specifically note that the digital equivalent of the ``Columbian Black
+Market Exchange''~\cite{fatf1997} is a theoretical problem for both
+Chaum and Taler, as individuals with a strong mutual trust foundation
+can simply copy electronic coins and thereby establish a limited form
+of black transfers.  However, unlike the situation with physical
+checks with blank recipients in the Columbian black market, the
+transitivity is limited as each participant can deposit the electronic
+coins and thereby cheat any other participant, while in the Columbian
+black market each participant only needs to trust the issuer of the
+check and not also all previous owners of the physical check.
+
+As with any unconditionally anonymous payment system, the ``Perfect
+Crime'' attack~\cite{solms1992perfect} where blackmail is used to
+force the mint to issue anonymous coins also continues to apply in
+principle.  However, as mentioned Taler does faciliate limits on
+withdrawals, which we believe is a better trade-off than the
+problematic escrow systems where the necessary intransparency
+actually facilitates voluntary cooperation between the mint and
+criminals~\cite{sander1999escrow} and where state can selectively
+deanonymize activists to support the deep state's quest for absolute
+security.
+
 \subsection{Offline Payments}
 
 Chaum's original proposals for anonymous digital cash avoided the need
@@ -952,28 +977,22 @@ currency.  A tax auditor can then request the merchant to reveal
 (meaningful) details about the business transaction ($\mathcal{D}$,
 $a$, $p$, $r$), including proof that applicable taxes were paid.
 
-If a merchant is not able to provide theses values, he can be punished
-in relation to the amount transferred by the traditional currency
-transfer.
-
+If a merchant is not able to provide theses values, he can be
+subjected to financial penalties by the state in relation to the
+amount transferred by the traditional currency transfer.
 
-\section{Future Work}
 
-%The legal status of the system needs to be investigated in the various
-%legal systems of the world.  However, given that the system enables
-%taxation and is able to impose withdrawal limits and thus is not
-%suitable for money laundering, we are optimistic that states will find
-%the design desirable.
+\subsection{System Performance}
 
 We performed some initial performance measurements for the various
-operations.  The main conclusion was that the computational and
-bandwidth cost for transactions described in this paper is smaller
-than $10^{-3}$ cent/transaction, and thus dwarfed by the other
-business costs for the mint.  However, this figure excludes the cost
-of currency transfers using traditional banking, which a mint operator
-would ultimately have to interact with.  Here, mint operators should
-be able to reduce their expenses by aggregating multiple transfers to
-the same merchant.
+operations on our mint implementation.  The main conclusion was that
+the computational and bandwidth cost for transactions described in
+this paper is smaller than $10^{-3}$ cent/transaction, and thus
+dwarfed by the other business costs for the mint.  However, this
+figure excludes the cost of currency transfers using traditional
+banking, which a mint operator would ultimately have to interact with.
+Here, mint operators should be able to reduce their expenses by
+aggregating multiple transfers to the same merchant.
 
 
 \section{Conclusion}
-- 
cgit v1.2.3


From 099b283f9c2bcd314f4dbd2761a8abd3ad5d0e72 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Thu, 24 Sep 2015 12:26:08 +0200
Subject: fixing build/ref issues in TeX

---
 doc/paper/taler.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index c504e843f..0bf710543 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -4,7 +4,7 @@
 \usepackage{palatino}
 \usepackage{xspace}
 \usepackage{microtype}
-\usepackage{tikz}
+\usepackage{tikz,eurosym}
 \usepackage{amsmath,amssymb}
 \usepackage{enumitem}
 \usetikzlibrary{shapes,arrows}
@@ -89,7 +89,7 @@ total control of the population, or create weak states with almost
 anarchistic economies.
 
 The Taler protocol is havily based on ideas from
-Chaum~\cite{1983blind} and also follows Chaum's basic architecture of
+Chaum~\cite{chaum1983blind} and also follows Chaum's basic architecture of
 customer, merchant and mint (Figure~\ref{fig:cmm}). The two designs
 share the key first step where the {\em customer} withdraws digital
 {\em coins} from the {\em mint} with unlinkability provided via blind
@@ -175,12 +175,12 @@ believe needs a payment system with the following properties:
     Thus, coins cannot just be issued in the smallest unit of currency,
     and a mechanism to give {\em change} must be provided to ensure
     that customers with sufficient total funds can always spend them.
-    For example, a customer may want to pay \eur{49,99} using a
-    \eur{100,00} coin.  The system must then support giving change in
-    the form of say two fresh \eur{0,01} and \eur{50,00} coins.  Those
+    For example, a customer may want to pay \EUR{49,99} using a
+    \EUR{100,00} coin.  The system must then support giving change in
+    the form of say two fresh \EUR{0,01} and \EUR{50,00} coins.  Those
     coins must be {\em unlinkable}: an adversary should not be able to
     relate transactions with either of the new coins to the original
-    \eur{100,00} coin or transaction or the other change being generated.
+    \EUR{100,00} coin or transaction or the other change being generated.
 \end{description}
 
 Instead of using cryptographic methods like restrictive blind
-- 
cgit v1.2.3


From 7c9d82174ffd24eeae3e4c00b5e5231557b3c03f Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Thu, 24 Sep 2015 15:40:27 +0200
Subject: more misc edits to the paper, also making sure it fits within page
 limits

---
 doc/paper/taler.tex | 230 ++++++++++++++++++++++++++++------------------------
 1 file changed, 126 insertions(+), 104 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 0bf710543..bdc205e1d 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -340,8 +340,8 @@ customers and merchants at the expense of the mint not only creates
 legal risks for the mint (who has to make a statistical argument), but
 also would require the mint to learn about microdonations where the
 merchant did not get upgraded to a macropayment.  Thus, it is unclear
-how much Peppercoin would actually do to reduce the computational
-burden on the mint.
+how Peppercoin would actually reduce the computational burden on the
+mint.
 
 
 \section{Design}
@@ -359,17 +359,19 @@ merchant must agree on the same \emph{mint}, which serves as an
 intermediary for the financial transaction between the two.  The mint
 is responsible for allowing the customer to obtain the anonymous
 digital currency and for enabling the merchant to convert the
-anonymous digital currency back to some traditional currency.
+digital coins back to some traditional currency.  The \emph{auditor}
+assures customers and merchants that the mint operates correctly.
 
 \subsection{Security model}
 
 Taler's security model assumes that cryptographic primitives are
 secure and that each participant is under full control of his system.
 The contact information of the mint is known to both customer and
-merchant from the start.  Furthermore, the merchant is known to the
-customer and we assume that an anonymous, reliable bi-directional
-communication channel can be established by the customer to both the
-mint and the merchant.
+merchant from the start.  Furthermore, the merchant communication's
+authenticity is assured to the customer (for example using X.509
+certificates~\cite{rfc5280}) and we assume that an anonymous, reliable
+bi-directional communication channel can be established by the
+customer to both the mint and the merchant.
 
 The mint is trusted to hold funds of its customers and to forward them
 when receiving the respective deposit instructions from the merchants.
@@ -377,7 +379,9 @@ Customer and merchant can have some assurances about the mint's
 liquidity and operation, as the mint has proven reserves, is subject
 to the law, and can have its business is regularly audited (for
 example, by the government or a trusted third party auditor).
-Audits of the mint's accounts must reveal any possible fraud.
+Regular audits of the mint's accounts must reveal any possible fraud
+before the mint is allowed to destroy the corresponding accumulated
+cryptographic proofs and book its fees as profits.
 %
 The merchant is trusted to deliver the service or goods to the
 customer upon receiving payment.  The customer can seek legal relief
@@ -387,7 +391,6 @@ and that he paid his obligations.
 Neither the merchant nor the customer may have any ability to {\em
   effectively} defraud the mint or the state collecting taxes.  Here,
 ``effectively'' means that the expected return for fraud is negative.
-%
 Note that customers do not need to be trusted in any way, and that in
 particular it is never necessary for anyone to try to recover funds
 from customers using legal means.
@@ -462,12 +465,11 @@ merchant.  In this respect, Taler provides exactly the same scheme for
 unconditional anonymous payments as was proposed by
 Chaum~\cite{chaum1983blind,chaum1990untraceable} over 30 years ago.
 
-While the customer thus has anonymity for his purchase, the mint will
+While the customer thus has anonymity for purchases, the mint will
 always learn the merchant's identity in order to credit the merchant's
-account.  This is also necessary for taxation, as Taler is supposed
+account.  This is simply necessary for taxation, as Taler is supposed
 to make information about funds received by any entity transparent
-to the state.  The merchant has thus no reason to anonymize his
-communication with the mint.
+to the state.
 % Technically, the merchant could still
 %use an anonymous communication channel to communicate with the mint.
 %However, in order to receive the traditional currency the mint will
@@ -489,10 +491,11 @@ communication with the mint.
 
 \subsection{Coins}
 
-A \emph{coin} is a digital token which derives its financial value
-from a signature on the coin's identifier by a mint.  The mint is
-expected to have multiple {\em coin signing key} pairs available for
-signing, each representing a different coin denomination.
+A \emph{coin} in Taler is a public-private key pair which derives its
+financial value from a signature over the coin's public key by a mint.
+The mint is expected to have multiple {\em coin signing key} pairs
+available for signing, each representing a different coin
+denomination.
 
 The coin signing keys have an expiration date (typically measured in
 years), and coins signed with a coin signing key must be spent (or
@@ -513,15 +516,15 @@ To ensure that the mint does not enable deanonymization of users by
 signing each coin with a fresh coin signing key, the mint must
 publicly announce the coin signing keys in advance.  Those
 announcements are expected to be signed with an off-line long-term
-private {\em master signing key} of the mint and possibly the auditor.
+private {\em master signing key} of the mint and the auditor.
 
 Before a customer can withdraw a coin from the mint, he has to pay the
 mint the value of the coin, as well as processing fees.  This is done
-using other means of payments, such as wire transfers~\cite{sepa} or
+using other means of payments, such as wire transfers or
 by having a personal {\em reserve} at the mint (which is equivalent to
 a bank account with a positive balance).  Taler assumes that the
 customer has a {\em withdrawal authorization key} to identify himself
-as authorized to withdraw funds from the reserved.  By signing the
+as authorized to withdraw funds from the reserve.  By signing the
 withdrawal request messages using the withdrawal authorization key,
 the customer can prove to the mint that he is the individual
 authorized to withdraw anonymous digital coins from the reserve.  The
@@ -529,10 +532,11 @@ mint will record the withdrawal messages with the reserve record as
 proof that the anonymous digital coin was created for the correct
 customer.  We note that the specifics of how the customer
 authenticates to the mint are orthogonal to the rest of the system,
-and multiple methods can be supported. To put it differently, unlike
-modern cryptocurrencies like BitCoin, Taler's design simply
-acknowledges that primitive accumulation~\cite{engels1844} predates
-the system and that a secure method to authenticate owners exists.
+and multiple methods can be supported.
+%To put it differently, unlike
+%modern cryptocurrencies like BitCoin, Taler's design simply
+%acknowledges that primitive accumulation~\cite{engels1844} predates
+%the system and that a secure method to authenticate owners exists.
 
 After a coin is minted, the customer is the only entity that knows the
 private key of the coin, making him the \emph{owner} of the coin.  The
@@ -556,46 +560,36 @@ transfer the funds to the merchant using a wire transfer or by
 crediting the merchant's individual account, depending on what is
 appropriate to the domain of the traditional currency.
 
-
-\paragraph{Partial spending.}
-
 To allow exact payments without requiring the customer to keep a large
-amount of ``change'' in stock, the payment systems allows partial
-spending of coins.  Consequently, the mint the must not only store the
-identifiers of spent coins, but also the fraction of the coin that has
-been spent.
-
-\paragraph{Online checks.}
-
-For secure transactions, the merchant is expected to perform an online
-check to detect double-spending.  Thus, the merchant must deposit the
-coin with the mint (and validate the signature from the mint
-confirming the validity of the transaction) before proceeding with its
-business logic.
+amount of ``change'' in stock and possibly perform thousands of
+signatures for larger transactions, the payment systems allows partial
+spending where just a fraction of a coin's total value is transferred.
+Consequently, the mint the must not only store the identifiers of
+spent coins, but also the fraction of the coin that has been spent.
 
 
 \subsection{Refreshing Coins}
 
-In the payment scenarios there are several cases where a customer will
-reveal the public key of a coin to a merchant, but not ultimately sign
-over the full value of the coin.  If the customer then continues to
-use the remainder of the value of the coin in other transactions,
-merchants and the mint could link the various transactions as they all
-share the same public key for the coin.
+In this and other scenarios it is thus possible that a customer has
+revealed the public key of a coin to a merchant, but not ultimately
+signed over the full value of the coin.  If the customer then
+continues to directly use the coin in other transactions, merchants
+and the mint could link the various transactions as they all share the
+same public key for the coin.
 
 Thus, the owner might want to exchange such a {\em dirty} coin for a
 {\em fresh} coin to ensure unlinkability of future transactions with
 the previous operation.  Even if a coin is not dirty, the owner of a
 coin may want to exchange a coin if the respective coin signing key is
 about to expire.  All of these operations are supported with the {\em
-  coin refreshing protocol}, which allows the owner of a coin to
-exchange existing coins (or their remaining value) for fresh coins
-with a new public-private key pairs.  Refreshing does not use the
-ordinary spending operation as the owner of a coin should not have to
-pay taxes on this operation.  Because of this, the refreshing protocol
-must assure that owner stays the same.  After all, the coin refreshing
-protocol must not be usable for transactions, as transactions in Taler
-must be taxable.
+  coin refreshing protocol}, which allows the owner of a coin to {\em
+  melt} existing coins (redeeming their remaining value) for fresh
+coins with a new public-private key pairs.  Refreshing does not use
+the ordinary spending operation as the owner of a coin should not have
+to pay taxes on this operation.  Because of this, the refreshing
+protocol must assure that owner stays the same.  After all, the coin
+refreshing protocol must not be usable for transactions, as
+transactions in Taler must be taxable.
 
 Thus, one main goal of the refreshing protocol is that the mint must
 not be able to link the fresh coin's public key to the public key of
@@ -605,12 +599,13 @@ fresh coin.  This way, refreshing cannot be used to construct a
 transaction --- the owner of the dirty coin remains in control of the
 fresh coin.
 
-As with other operations, the refreshing protocol must also protect
-the mint from double-spending; similarly, the customer has to have
-cryptographic evidence if there is any misbehaviour by the mint.
-Finally, the mint may choose to charge a transaction fee for
-refreshing by reducing the value of the generated fresh coins
-in relation to the value of the melted coins.
+%As with other operations, the refreshing protocol must also protect
+%the mint from double-spending; similarly, the customer has to have
+%cryptographic evidence if there is any misbehaviour by the mint.
+%Finally, the mint may choose to charge a transaction fee for
+%refreshing by reducing the value of the generated fresh coins
+%in relation to the value of the melted coins.
+%
 %Naturally, all such transaction fees should be clearly stated as part
 %of the business contract offered by the mint to customers and
 %merchants.
@@ -969,44 +964,56 @@ if the owner's identity were embedded in coins, it would be leaked to
 the mint as part of the reveal operation in the cut-and-choose
 operation of the refreshing protocol.
 
-\subsection{Merchant Tax Audits}
-
-For a tax audit on the merchant, the mint includes the business
-transaction-specific hash in the transfer of the traditional
-currency.  A tax auditor can then request the merchant to reveal
-(meaningful) details about the business transaction ($\mathcal{D}$,
-$a$, $p$, $r$), including proof that applicable taxes were paid.
-
-If a merchant is not able to provide theses values, he can be
-subjected to financial penalties by the state in relation to the
-amount transferred by the traditional currency transfer.
-
-
-\subsection{System Performance}
-
-We performed some initial performance measurements for the various
-operations on our mint implementation.  The main conclusion was that
-the computational and bandwidth cost for transactions described in
-this paper is smaller than $10^{-3}$ cent/transaction, and thus
-dwarfed by the other business costs for the mint.  However, this
-figure excludes the cost of currency transfers using traditional
-banking, which a mint operator would ultimately have to interact with.
-Here, mint operators should be able to reduce their expenses by
-aggregating multiple transfers to the same merchant.
-
-
-\section{Conclusion}
-
-We have presented an efficient electronic payment system that
-simultaneously addresses the conflicting objectives created by the
-citizen's need for privacy and the state's need for taxation.  The
-coin refreshing protocol makes the design flexible and enables a
-variety of payment methods.  The current balance and profits of the
-mint are also easily determined, thus audits can be used to ensure
-that the mint operates correctly.  The libre implementation and open
-protocol may finally enable modern society to upgrade to proper
-electronic wallets with efficient, secure and privacy-preserving
-transactions.
+%\subsection{Merchant Tax Audits}
+%
+%For a tax audit on the merchant, the mint includes the business
+%transaction-specific hash in the transfer of the traditional
+%currency.  A tax auditor can then request the merchant to reveal
+%(meaningful) details about the business transaction ($\mathcal{D}$,
+%$a$, $p$, $r$), including proof that applicable taxes were paid.
+%
+%If a merchant is not able to provide theses values, he can be
+%subjected to financial penalties by the state in relation to the
+%amount transferred by the traditional currency transfer.
+
+\subsection{Cryptographic proof vs. evidence}
+
+In this paper we have use the term ``proof'' in many places as the
+protocol provides cryptographic proofs of which parties behave
+correctly or incorrectly. However, as~\cite{fc2014murdoch} point out,
+in practice financial systems need to provide evidence that holds up
+in courts.  Taler's implementation is designed to export evidence and
+upholds the core principles described in~\cite{fc2014murdoch}.  In
+particular, in providing the cryptographic proofs as evidence none of
+the participants have to disclose their core secrets, the process is
+covered by standard testing proceedures, and the full trusted
+computing base (TCB) is public and free software.
+
+%\subsection{System Performance}
+%
+%We performed some initial performance measurements for the various
+%operations on our mint implementation.  The main conclusion was that
+%the computational and bandwidth cost for transactions described in
+%this paper is smaller than $10^{-3}$ cent/transaction, and thus
+%dwarfed by the other business costs for the mint.  However, this
+%figure excludes the cost of currency transfers using traditional
+%banking, which a mint operator would ultimately have to interact with.
+%Here, mint operators should be able to reduce their expenses by
+%aggregating multiple transfers to the same merchant.
+
+
+%\section{Conclusion}
+
+%We have presented an efficient electronic payment system that
+%simultaneously addresses the conflicting objectives created by the
+%citizen's need for privacy and the state's need for taxation.  The
+%coin refreshing protocol makes the design flexible and enables a
+%variety of payment methods.  The current balance and profits of the
+%mint are also easily determined, thus audits can be used to ensure
+%that the mint operates correctly.  The libre implementation and open
+%protocol may finally enable modern society to upgrade to proper
+%electronic wallets with efficient, secure and privacy-preserving
+%transactions.
 
 % commented out for anonymized submission
 %\subsection*{Acknowledgements}
@@ -1020,21 +1027,36 @@ transactions.
 
 
 \bibliographystyle{alpha}
-\bibliography{taler}
+\bibliography{taler,rfc}
 
+\newpage
 \appendix
 
 \section{Optional features}
 
 In this appendix we detail various optional features that can
-be added to the basic protocol.
+be added to the basic protocol to reduce transaction costs for
+certain interactions.
 
 However, we note that Taler's transaction costs are expected to be so
-low that these features are not particularly useful, as they are about
-reducing interactions with the mint to reduce costs.  In particular,
-we expect that transactions with amounts below Taler's transaction
-costs to be economically meaningless.  Nevertheless, we document
-various ways how this could be achieved.
+low that these features are likely not particularly useful in
+practice: When we performed some initial performance measurements for
+the various operations on our mint implementation, the main conclusion
+was that the computational and bandwidth cost for transactions
+described in this paper is smaller than $10^{-3}$ cent/transaction,
+and thus dwarfed by the other business costs for the mint.  We note
+that the $10^{-3}$ cent/transaction estimate excludes the cost of wire
+transfers using traditional banking, which a mint operator would
+ultimately have to interact with.  Here, mint operators should be able
+to reduce their expenses by aggregating multiple transfers to the same
+merchant.
+
+As a result of the low cost of the interaction with the mint in Taler
+today, we expect that transactions with amounts below Taler's internal
+transaction costs to be economically meaningless.  Nevertheless, we
+document various ways how such transactions could be achieved within
+Taler.
+
 
 
 \subsection{Incremental spending}
-- 
cgit v1.2.3


From 851a727b6999b39cd31826fe500098ea147542b9 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Thu, 24 Sep 2015 17:32:55 +0200
Subject: more edits on taler paper

---
 doc/paper/taler.tex | 81 +++++++++++++++++++++++++++++++----------------------
 1 file changed, 48 insertions(+), 33 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index bdc205e1d..2425de75b 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -620,9 +620,8 @@ message always first checks that the signature is valid, even though
 this is not explicitly stated below.  Also, whenever a signed message
 is transmitted, it is assumed that the receiver is told the public key
 (or knows it from the context) and that the signature contains
-additional identification as to the purpose of the signature (such
-that it is not possible to use a signature from one protocol step in a
-different context).
+additional identification as to the purpose of the signature, making
+it impossible to use a signature in a different context.
 
 When the mint signs messages (not coins), an {\em online message
   signing key} of the mint is used.  The mint's long-term offline key
@@ -658,9 +657,8 @@ following interaction with the mint:
         \begin{itemize}
            \item withdrawal key $W := (W_s,W_p)$ with private key $W_s$ and public key $W_p$,
            \item coin key $C := (C_s,C_p)$ with private key $C_s$ and public key $C_p$,
-           \item blinding factor $b$,
+           \item blinding factor $b$, and commits $\langle W, C, b \rangle$ to disk.
         \end{itemize}
-        and commits $\langle W, C, b \rangle$ to disk.
   \item The customer transfers an amount of money corresponding to (at least) $K_p$ to the mint, with $W_p$ in the subject line of the transaction.
   \item The mint receives the transaction and credits the $W_p$ reserve with the respective amount in its database.
   \item The customer sends $S_W(E_b(C_p))$ to the mint to request withdrawal of $C$; here, $E_b$ denotes Chaum-style blinding with blinding factor $b$.
@@ -675,21 +673,26 @@ following interaction with the mint:
         \end{enumerate}
         If the guards for the transaction fail, the mint sends a descriptive error back to the customer,
         with proof that it operated correctly (i.e. by showing the transaction history for the reserve).
-  \item The customer computes (and verifies) the unblind signature $S_K(C_p) = D_b(S_K(E_b(C_p)))$.
+  \item The customer computes (and verifies) the unblinded signature $S_K(C_p) = D_b(S_K(E_b(C_p)))$.
         The customer writes $\langle S_K(C_p), C_s \rangle$ to disk (effectively adding the coin to the
         local wallet) for future use.
 \end{enumerate}
+We note that the authorization to create and access a reserve using a
+withdrawal key $W$ is just one way to establish that the customer is
+authorized to withdraw funds.  If a mint has other ways to securely
+authenticate customers and establish that they are authorized to
+withdraw funds, those can also be used with Taler.
 
 
 \subsection{Exact and partial spending}
 
 A customer can spend coins at a merchant, under the condition that the
-merchant trusts the mint that minted the coin.  Merchants are
+merchant trusts the specific mint that minted the coin.  Merchants are
 identified by their public key $M := (M_s, M_p)$, which must be known
 to the customer apriori.
 
 The following steps describe the protocol between customer, merchant and mint
-for a transaction involving a coin $C := (C_s, C_p)$ which is previously signed
+for a transaction involving a coin $C := (C_s, C_p)$, which was previously signed
 by a mint's denomination key $K$, i.e. the customer posses
 $\widetilde{C} := S_K(C_p)$:
 
@@ -701,36 +704,36 @@ $\widetilde{C} := S_K(C_p)$:
   transaction, $a$ is data relevant to the contract indicating which services
   or goods the merchant will deliver to the customer, $f$ is the price of the offer,
   and $p$ is the merchant's payment information (e.g. his IBAN number) and $r$ is
-  an random nounce.  The merchant commits $\langle \mathcal{A}
+  a random nounce.  The merchant commits $\langle \mathcal{A}
   \rangle$ to disk and sends $\mathcal{A}$ it to the customer.
 \item\label{deposit} The customer must possess or acquire a coin minted by a mint that is
   accepted by the merchant, i.e. $K$ should be publicly signed by some $D_i
   \in \{D_1, D_2, \ldots, D_n\}$, and has a value $\geq f$. (The customer
   can of course also use multiple coins where the total value adds up to
   the cost of the transaction and run the following steps for each of
-  the coins. However, for simplicity of the description here we will
+  the coins. However, for simplicity of the exposition here we will
   assume that one coin is sufficient.)
-
+%
   The customer then generates a \emph{deposit-permission} $\mathcal{D} :=
   S_c(\widetilde{C}, m, f, H(a), H(p,r), M_p)$
   and sends $\langle \mathcal{D}, D_i\rangle$ to the merchant,
   where $D_i$ is the mint which signed $K$.
-\item The merchant gives $(\mathcal{D}, p, r)$ to the mint, revealing his
-  payment information.
+\item The merchant gives $(\mathcal{D}, p, r)$ to the mint, revealing $p$
+  only to the mint.
 
 \item The mint validates $\mathcal{D}$ and checks for double spending.
   If the coin has been involved in previous transactions, it sends an error
   with the records from the previous transactions back to the merchant.
-
+%
   If double spending is not found, the mint commits $\langle \mathcal{D} \rangle$ to disk
-  and notifies the merchant that deposit operation was successful.
+  and notifies the merchant that the deposit operation was successful.
 
 \item The merchant commits and forwards the notification from the mint to the
-  customer, confirming the success or failure of the operation.
+  customer, confirming the success (or failure) of the operation.
 \end{enumerate}
 
-Similarly, if a transaction is aborted after Step~\ref{deposit},
-subsequent transactions with the same coin can be linked to the coin,
+If a transaction is aborted after Step~\ref{deposit},
+subsequent transactions with the same coin could be linked to the coin,
 but not directly to the coin's owner.  The same applies to partially
 spent coins (where $f$ is smaller than the actual value of the coin).
 To unlink subsequent transactions from a coin, the customer has to
@@ -771,20 +774,23 @@ execute the coin refreshing protocol with the mint.
 
 \subsection{Refreshing} \label{sec:refreshing}
 
-The following protocol is executed in order to refresh a coin $C'$ of
-denomination $K$ to a fresh coin $\widetilde{C}$ with the same
-denomination. In the protocol, $\kappa \ge 3$ is a security parameter
-and $G$ is the generator of the elliptic curve.
+The following refreshing protocol is executed in order to melt a dirty
+coin $C'$ of denomination $K$ to obtain a fresh coin $\widetilde{C}$
+with the same denomination.  In pratice, Taler uses a natural
+extension where multiple fresh coins are generated a the same time to
+enable giving precise change matching any amount.  In the
+protocol, $\kappa \ge 3$ is a security parameter and $G$ is the
+generator of the elliptic curve.
 
 \begin{enumerate}
   \item For each $i = 1,\ldots,\kappa$, the customer
     \begin{itemize}
       \item randomly generates transfer key $T^{(i)} := \left(t^{(i)}_s,T^{(i)}_p\right)$ where $T^{(i)}_p := t^{(i)}_s G$,
-      \item randomly generates coin key pair $C^{(i)} := \left(c_s^{(i)}, C_p^{(i)}\right)$ where $C^{(i)}_p := c^{(i)}_s G$,
+      \item randomly generates coin key pair \\ $C^{(i)} := \left(c_s^{(i)}, C_p^{(i)}\right)$ where $C^{(i)}_p := c^{(i)}_s G$,
       \item randomly generates blinding factors $b_i$,
       \item computes $E_i := E_{K_i}\left(c_s^{(i)}, b_i\right)$ where $K_i := H(c'_s T_p^{(i)})$. (The encryption key $K_i$ is
             computed by multiplying the private key $c'_s$ of the original coin with the point on the curve
-            that represents the public key $T^{(i)}_p$ of the transfer key $T^{(i)}$.),
+            that represents the public key $T^{(i)}_p$ of the transfer key $T^{(i)}$. This is basically DH between coin and transfer key.),
     \end{itemize}
     and commits $\langle C', \vec{T}, \vec{C}, \vec{b} \rangle$ to disk.
   \item The customer computes $B_i := E_{b_i}(C^{(i)}_p)$  for $i=1,\ldots,\kappa$ and sends a commitment
@@ -800,14 +806,23 @@ and $G$ is the generator of the elliptic curve.
   \item The customer computes $\mathfrak{R} := \left(t_s^{(i)}, C_p^{(i)}, b_i\right)_{i \ne \gamma}$
         and sends $S_{C'}(\mathfrak{R})$ to the mint.
   \item \label{step:refresh-ccheck} The mint checks whether $\mathfrak{R}$ is consistent with the commitments;
-        specifically, it computes for $i \not= \gamma$:
-    \begin{itemize}
-      \item $\overline{K}_i := H(t_s^{(i)} C_p')$,
-      \item $(\overline{c}_s^{(i)}, \overline{b}_i) := D_{\overline{K}_i}(E_i)$,
-      \item $\overline{C}^{(i)}_p := \overline{c}_s^{(i)} G$,
-      \item $\overline{B}_i := E_{b_i}(C_p^{(i)})$,
-      \item $\overline{T}_i := t_s^{(i)} G$,
-    \end{itemize}
+    specifically, it computes for $i \not= \gamma$:
+
+    \vspace{-2ex}
+    \begin{minipage}{5cm}
+    \begin{align*}
+      \overline{K}_i :&= H(t_s^{(i)} C_p'), \\
+      (\overline{c}_s^{(i)}, \overline{b}_i) :&= D_{\overline{K}_i}(E_i), \\
+      \overline{C}^{(i)}_p :&= \overline{c}_s^{(i)} G,
+     \end{align*}
+     \end{minipage}
+    \begin{minipage}{5cm}
+      \begin{align*}
+      \overline{B}_i :&= E_{b_i}(C_p^{(i)}), \\
+      \overline{T}_i :&= t_s^{(i)} G, \\
+      \end{align*}
+    \end{minipage}
+
     and checks if $\overline{C}^{(i)}_p = C^{(i)}_p$ and $H(E_i, \overline{B}_i, \overline{T}^{(i)}_p) = H(E_i, B_i, T^{(i)}_p)$
     and $\overline{T}_i = T_i$.
 
@@ -826,7 +841,7 @@ and $G$ is the generator of the elliptic curve.
 For a coin that was successfully refreshed, the mint responds to a
 request $S_{C'}(\mathtt{link})$ with $(T^{(\gamma)}_p$, $E_{\gamma},
 \widetilde{C})$.
-
+%
 This allows the owner of the old coin to also obtain the private key
 of the new coin, even if the refreshing protocol was illicitly
 executed by another party who learned $C'_s$ from the old owner.  As a
-- 
cgit v1.2.3


From 18d3c5efa546bf91719cc3df04e539bdc6b07292 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Thu, 24 Sep 2015 17:43:20 +0200
Subject: more paper edits and claifications

---
 doc/paper/taler.tex | 27 ++++++++++++++++-----------
 1 file changed, 16 insertions(+), 11 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 2425de75b..5ef1df3c9 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -842,13 +842,14 @@ For a coin that was successfully refreshed, the mint responds to a
 request $S_{C'}(\mathtt{link})$ with $(T^{(\gamma)}_p$, $E_{\gamma},
 \widetilde{C})$.
 %
-This allows the owner of the old coin to also obtain the private key
-of the new coin, even if the refreshing protocol was illicitly
-executed by another party who learned $C'_s$ from the old owner.  As a
-result, linking ensures that access to the new coins minted by the
-refresh protocol is always {\em shared} with the owner of the melted
-coins.  This makes it impossible to abuse the refresh protocol for
-{\em transactions}.
+This allows the owner of the melted coin to also obtain the private
+key of the new coin, even if the refreshing protocol was illicitly
+executed with the help of another party who generated $C'_s$ and only
+provided $\vec{C'_p}$ and other required information to the old owner.
+As a result, linking ensures that access to the new coins minted by
+the refresh protocol is always {\em shared} with the owner of the
+melted coins.  This makes it impossible to abuse the refresh protocol
+for {\em transactions}.
 
 The linking request is not expected to be used at all during ordinary
 operation of Taler.  If the refresh protocol is used by Alice to
@@ -858,8 +859,12 @@ The fundamental reason why the mint must provide the link protocol is
 simply to provide a threat: if Bob were to use the refresh protocol
 for a transaction of funds from Alice to him, Alice may use a link
 request to gain shared access to Bob's coins. Thus, this threat
-prevents Bob from abusing the refresh protocol to evade taxation on
-transactions.
+prevents Alice and Bob from abusing the refresh protocol to evade
+taxation on transactions. If Bob trusts Alice to not execute the link
+protocol, then they can already conspire to evade taxation by simply
+exchanging the original private coin keys.  This is permitted in our
+taxation model as with such trust they are assumed to be the same
+entity.
 
 The auditor can anonymously check if the mint correctly implements the
 link request, thus preventing the mint operator from legally disabling
@@ -879,10 +884,10 @@ location of the missmatch in the case of the reveal step in the
 refresh protocol.  It is also possible that the server may claim that
 the client has been violating the protocol.  In these cases, the
 clients should verify any proofs provided and if they are acceptable,
-notify the user that they are somehow ``faulty''.  Similar, if the
+notify the user that they are somehow faulty.  Similar, if the
 server indicates that the client is violating the protocol, the
 client should record the interaction and enable the user to file a
-bug report with the developer.
+bug report.
 
 The second case is a faulty mint service provider.  Such faults will
 be detected because of protocol violations (for example, by providing
-- 
cgit v1.2.3


From 9ff0c56018366bc49c04521f8d3bcea1c256c014 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Sat, 26 Sep 2015 11:54:03 +0200
Subject: typo

---
 doc/paper/taler.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 5ef1df3c9..a84962dd2 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -510,7 +510,7 @@ existence using the respective coin signing key.  In this case, the
 mint can allow the original set of customers to exchange the coins
 that were signed with the compromised private key, while refusing
 further transactions from merchants if they involve those coins.  As a
-result, the financial damage of loosing a private signing key can be
+result, the financial damage of losing a private signing key can be
 limited to at most twice the amount originally signed with that key.
 To ensure that the mint does not enable deanonymization of users by
 signing each coin with a fresh coin signing key, the mint must
-- 
cgit v1.2.3


From 42aea7d1380a01a9dde48a3bff99857f532afaa2 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Sat, 26 Sep 2015 16:30:04 +0200
Subject: address Fabian Kirsch's comments for more consistent symbol names,
 and adding a 'legend'

---
 doc/paper/taler.tex | 153 +++++++++++++++++++++++++++++++++++++++-------------
 1 file changed, 117 insertions(+), 36 deletions(-)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index a84962dd2..361efadde 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -647,34 +647,35 @@ taxability.
 
 \subsection{Withdrawal}
 
-To withdraw anonymous digital coins, the customer performs the
-following interaction with the mint:
+Let $G$ be the generator of an elliptic curve.  To withdraw anonymous
+digital coins, the customer performs the following interaction with
+the mint:
 
 \begin{enumerate}
   \item The customer identifies a mint with an auditor-approved
         coin signing public-private key pair $K := (K_s, K_p)$
         and randomly generates:
         \begin{itemize}
-           \item withdrawal key $W := (W_s,W_p)$ with private key $W_s$ and public key $W_p$,
-           \item coin key $C := (C_s,C_p)$ with private key $C_s$ and public key $C_p$,
+           \item withdrawal key $W := (w_s,W_p)$ with private key $w_s$ and public key $W_p$,
+           \item coin key $C := (c_s,C_p)$ with private key $c_s$ and public key $C_p := c_s G$,
            \item blinding factor $b$, and commits $\langle W, C, b \rangle$ to disk.
         \end{itemize}
   \item The customer transfers an amount of money corresponding to (at least) $K_p$ to the mint, with $W_p$ in the subject line of the transaction.
   \item The mint receives the transaction and credits the $W_p$ reserve with the respective amount in its database.
-  \item The customer sends $S_W(E_b(C_p))$ to the mint to request withdrawal of $C$; here, $E_b$ denotes Chaum-style blinding with blinding factor $b$.
-  \item The mint checks if the same withdrawal request was issued before; in this case, it sends $S_{K}(E_b(C_p))$ to the customer.\footnote{Here $S_K$
+  \item The customer sends $S_W(B_b(C_p))$ to the mint to request withdrawal of $C$; here, $B_b$ denotes Chaum-style blinding with blinding factor $b$.
+  \item The mint checks if the same withdrawal request was issued before; in this case, it sends $S_{K}(B_b(C_p))$ to the customer.\footnote{Here $S_K$
         denotes a Chaum-style blind signature with private key $K_s$.}
         If this is a fresh withdrawal request, the mint performs the following transaction:
         \begin{enumerate}
            \item checks if the reserve $W_p$ has sufficient funds for a coin of value corresponding to $K_p$
-           \item stores the withdrawal request $\langle S_W(E_b(C_p)), S_K(E_b(C_p)) \rangle$ in its database for future reference,
+           \item stores the withdrawal request and response $\langle S_W(B_b(C_p)), S_K(B_b(C_p)) \rangle$ in its database for future reference,
            \item deducts the amount corresponding to $K_p$ from the reserve,
-           \item and sends $S_{K}(E_b(C_p))$ to the customer.
         \end{enumerate}
+        and then sends $S_{K}(B_b(C_p))$ to the customer.
         If the guards for the transaction fail, the mint sends a descriptive error back to the customer,
         with proof that it operated correctly (i.e. by showing the transaction history for the reserve).
-  \item The customer computes (and verifies) the unblinded signature $S_K(C_p) = D_b(S_K(E_b(C_p)))$.
-        The customer writes $\langle S_K(C_p), C_s \rangle$ to disk (effectively adding the coin to the
+  \item The customer computes (and verifies) the unblinded signature $S_K(C_p) = B^{-1}_b(S_K(B_b(C_p)))$.
+        The customer writes $\langle S_K(C_p), c_s \rangle$ to disk (effectively adding the coin to the
         local wallet) for future use.
 \end{enumerate}
 We note that the authorization to create and access a reserve using a
@@ -688,17 +689,17 @@ withdraw funds, those can also be used with Taler.
 
 A customer can spend coins at a merchant, under the condition that the
 merchant trusts the specific mint that minted the coin.  Merchants are
-identified by their public key $M := (M_s, M_p)$, which must be known
+identified by their public key $M := (m_s, M_p)$, which must be known
 to the customer apriori.
 
 The following steps describe the protocol between customer, merchant and mint
-for a transaction involving a coin $C := (C_s, C_p)$, which was previously signed
+for a transaction involving a coin $C := (c_s, C_p)$, which was previously signed
 by a mint's denomination key $K$, i.e. the customer posses
 $\widetilde{C} := S_K(C_p)$:
 
 \begin{enumerate}
 \item\label{contract} Let $\vec{D} := D_1, \ldots, D_n$ be the list of
-  mints accepted by the merchant where each $D_i$ is a mint's public
+  mints accepted by the merchant where each $D_j$ is a mint's public
   key.  The merchant creates a digitally signed contract $\mathcal{A}
   := S_M(m, f, a, H(p, r), \vec{D})$ where $m$ is an identifier for this
   transaction, $a$ is data relevant to the contract indicating which services
@@ -707,7 +708,7 @@ $\widetilde{C} := S_K(C_p)$:
   a random nounce.  The merchant commits $\langle \mathcal{A}
   \rangle$ to disk and sends $\mathcal{A}$ it to the customer.
 \item\label{deposit} The customer must possess or acquire a coin minted by a mint that is
-  accepted by the merchant, i.e. $K$ should be publicly signed by some $D_i
+  accepted by the merchant, i.e. $K$ should be publicly signed by some $D_j
   \in \{D_1, D_2, \ldots, D_n\}$, and has a value $\geq f$. (The customer
   can of course also use multiple coins where the total value adds up to
   the cost of the transaction and run the following steps for each of
@@ -716,8 +717,8 @@ $\widetilde{C} := S_K(C_p)$:
 %
   The customer then generates a \emph{deposit-permission} $\mathcal{D} :=
   S_c(\widetilde{C}, m, f, H(a), H(p,r), M_p)$
-  and sends $\langle \mathcal{D}, D_i\rangle$ to the merchant,
-  where $D_i$ is the mint which signed $K$.
+  and sends $\langle \mathcal{D}, D_j\rangle$ to the merchant,
+  where $D_j$ is the mint which signed $K$.
 \item The merchant gives $(\mathcal{D}, p, r)$ to the mint, revealing $p$
   only to the mint.
 
@@ -787,15 +788,14 @@ generator of the elliptic curve.
     \begin{itemize}
       \item randomly generates transfer key $T^{(i)} := \left(t^{(i)}_s,T^{(i)}_p\right)$ where $T^{(i)}_p := t^{(i)}_s G$,
       \item randomly generates coin key pair \\ $C^{(i)} := \left(c_s^{(i)}, C_p^{(i)}\right)$ where $C^{(i)}_p := c^{(i)}_s G$,
-      \item randomly generates blinding factors $b_i$,
-      \item computes $E_i := E_{K_i}\left(c_s^{(i)}, b_i\right)$ where $K_i := H(c'_s T_p^{(i)})$. (The encryption key $K_i$ is
+      \item randomly generates blinding factors $b^{(i)}$,
+      \item computes $E^{(i)} := E_{K_i}\left(c_s^{(i)}, b^{(i)}\right)$ where $K_i := H(c'_s T_p^{(i)})$. (The encryption key $K_i$ is
             computed by multiplying the private key $c'_s$ of the original coin with the point on the curve
             that represents the public key $T^{(i)}_p$ of the transfer key $T^{(i)}$. This is basically DH between coin and transfer key.),
     \end{itemize}
     and commits $\langle C', \vec{T}, \vec{C}, \vec{b} \rangle$ to disk.
-  \item The customer computes $B_i := E_{b_i}(C^{(i)}_p)$  for $i=1,\ldots,\kappa$ and sends a commitment
-    $S_{C'}(\vec{E}, \vec{B}, \vec{T_p}))$ to the mint;
-    here $E_{b_i}$ denotes Chaum-style blinding with blinding factor $b_i$.
+  \item The customer computes $B^{(i)} := B_{b^{(i)}}(C^{(i)}_p)$  for $i \in 1,\ldots,\kappa$ and sends a commitment
+    $S_{C'}(\vec{E}, \vec{B}, \vec{T_p}))$ to the mint.
   \item The mint generates a random $\gamma$ with $1 \le \gamma \le \kappa$ and
     marks $C'_p$ as spent by committing
     $\langle C', \gamma, S_{C'}(\vec{E}, \vec{B}, \vec{T}) \rangle$ to disk.
@@ -803,7 +803,7 @@ generator of the elliptic curve.
     possible to use any equivalent mint signing key known to the customer here, as $K$ merely
     serves as proof to the customer that the mint selected this particular $\gamma$.}
   \item The customer commits $\langle C', S_K(C'_p, \gamma) \rangle$ to disk.
-  \item The customer computes $\mathfrak{R} := \left(t_s^{(i)}, C_p^{(i)}, b_i\right)_{i \ne \gamma}$
+  \item The customer computes $\mathfrak{R} := \left(t_s^{(i)}, C_p^{(i)}, b^{(i)}\right)_{i \ne \gamma}$
         and sends $S_{C'}(\mathfrak{R})$ to the mint.
   \item \label{step:refresh-ccheck} The mint checks whether $\mathfrak{R}$ is consistent with the commitments;
     specifically, it computes for $i \not= \gamma$:
@@ -812,23 +812,23 @@ generator of the elliptic curve.
     \begin{minipage}{5cm}
     \begin{align*}
       \overline{K}_i :&= H(t_s^{(i)} C_p'), \\
-      (\overline{c}_s^{(i)}, \overline{b}_i) :&= D_{\overline{K}_i}(E_i), \\
-      \overline{C}^{(i)}_p :&= \overline{c}_s^{(i)} G,
+      (\overline{c}_s^{(i)}, \overline{b}_i) :&= D_{\overline{K}_i}(E^{(i)}), \\
+     \overline{C^{(i)}_p} :&= \overline{c}_s^{(i)} G,
      \end{align*}
      \end{minipage}
     \begin{minipage}{5cm}
       \begin{align*}
-      \overline{B}_i :&= E_{b_i}(C_p^{(i)}), \\
-      \overline{T}_i :&= t_s^{(i)} G, \\
+       \overline{T_p^{(i)}} :&= t_s^{(i)} G, \\ \\
+      \overline{B^{(i)}} :&= B_{b^{(i)}}(\overline{C_p^{(i)}}),
       \end{align*}
     \end{minipage}
 
-    and checks if $\overline{C}^{(i)}_p = C^{(i)}_p$ and $H(E_i, \overline{B}_i, \overline{T}^{(i)}_p) = H(E_i, B_i, T^{(i)}_p)$
-    and $\overline{T}_i = T_i$.
+    and checks if $\overline{B^{(i)}} = B^{(i)}$
+    and $\overline{T^{(i)}_p} = T^{(i)}_p$.
 
   \item \label{step:refresh-done} If the commitments were consistent,
     the mint sends the blind signature $\widetilde{C} :=
-    S_{K}(B_\gamma)$ to the customer.  Otherwise, the mint responds
+    S_{K}(B^{(\gamma)})$ to the customer.  Otherwise, the mint responds
     with an error the value of $C'$.
 \end{enumerate}
 
@@ -839,7 +839,7 @@ generator of the elliptic curve.
 \subsection{Linking}
 
 For a coin that was successfully refreshed, the mint responds to a
-request $S_{C'}(\mathtt{link})$ with $(T^{(\gamma)}_p$, $E_{\gamma},
+request $S_{C'}(\mathtt{link})$ with $(T^{(\gamma)}_p$, $B^{(\gamma)},
 \widetilde{C})$.
 %
 This allows the owner of the melted coin to also obtain the private
@@ -1040,7 +1040,7 @@ computing base (TCB) is public and free software.
 
 %This work was supported by a grant from the Renewable Freedom Foundation.
 % FIXME: ARED?
-%We thank Tanja Lange and Dan Bernstein for feedback on an earlier
+%We thank Tanja Lange, Dan Bernstein and Fabian Kirsch for feedback on an earlier
 %version of this paper, Nicolas Fournier for implementing and running
 %some performance benchmarks, and Richard Stallman, Hellekin Wolf,
 %Jacob Appelbaum for productive discussions and support.
@@ -1105,15 +1105,15 @@ coin first.
 \item\label{offer2} The merchant sends an \emph{offer:} $\langle S_M(m, f),
   \vec{D} \rangle$ containing the price of the offer $f$, a transaction
   ID $m$ and the list of mints $D_1, \ldots, D_n$ accepted by the merchant
-  where each $D_i$ is a mint's public key.
+  where each $D_j$ is a mint's public key.
 \item\label{lock2} The customer must possess or acquire a coin minted by a mint that is
-  accepted by the merchant, i.e. $K$ should be publicly signed by some $D_i
+  accepted by the merchant, i.e. $K$ should be publicly signed by some $D_j
   \in \{D_1, D_2, \ldots, D_n\}$, and has a value $\geq f$.
 
   Customer then generates a \emph{lock-permission} $\mathcal{L} :=
   S_c(\widetilde{C}, t, m, f, M_p)$ where $t$ specifies the time until which the
-  lock is valid and sends $\langle \mathcal{L}, D_i\rangle$ to the merchant,
-  where $D_i$ is the mint which signed $K$.
+  lock is valid and sends $\langle \mathcal{L}, D_j\rangle$ to the merchant,
+  where $D_j$ is the mint which signed $K$.
 \item The merchant asks the mint to apply the lock by sending $\langle
   \mathcal{L} \rangle$ to the mint.
 \item The mint validates $\widetilde{C}$ and detects double spending if there is
@@ -1127,7 +1127,7 @@ coin first.
 \item\label{contract2} The merchant creates a digitally signed contract
   $\mathcal{A} := S_M(m, f, a, H(p, r))$ where $a$ is data relevant to the contract
   indicating which services or goods the merchant will deliver to the customer, and $p$ is the
-  merchant's payment information (e.g. his IBAN number) and $r$ is an random nounce.
+  merchant's payment information (e.g. his IBAN number) and $r$ is an random nonce.
   The merchant commits $\langle \mathcal{A} \rangle$ to disk and sends it to the customer.
 \item The customer creates a
   \emph{deposit-permission} $\mathcal{D} := S_c(\widetilde{C}, f, m, M_p, H(a), H(p, r))$, commits
@@ -1315,4 +1315,85 @@ If an organization detects that it cannot support itself with
 microdonations, it can always choose to switch to the macropayment
 system with slightly higher transaction costs to remain in business.
 
+\newpage
+\section{Notation summary}
+
+The paper uses the subscript $p$ to indicate public keys and $s$ to
+indicate secret (private) keys.  For keys, we also use small letters
+for scalars and capital letters for points on an elliptic curve.  The
+capital letter without the subscript $p$ stands for the key pair.  The
+superscript $(i)$ is used to indicate one of the elements of a vector
+during the cut-and-choose protocol.  Bold-face is used to indicate a
+vector over these elements.  A line above indicates a value computed
+by the verifier during the cut-and-choose operation.  We use $f()$ to
+indicate the application of a function $f$ to one or more arguments.
+
+\begin{description}
+  \item[$K_s$]{Private (RSA) key of the mint used for coin signing}
+  \item[$K_p$]{Public (RSA) key corresponding to $K_s$}
+  \item[$K$]{Public-priate (RSA) coin signing key pair $K := (K_s, K_p)$}
+  \item[$b$]{RSA blinding factor for RSA-style blind signatures}
+  \item[$B_b()$]{RSA blinding over the argument using blinding factor $b$}
+  \item[$B^{-1}_b()$]{RSA unblinding of the argument using blinding factor $b$, inverse of $B_b()$}
+  \item[$S_K()$]{Chaum-style RSA signature, commutes with blinding operation $B_b()$}
+  \item[$w_s$]{Private key from customer for authentication}
+  \item[$W_p$]{Public key corresponding to $w_s$}
+  \item[$W$]{Public-private customer authentication key pair $W := (w_s, W_p)$}
+  \item[$S_W()$]{Signature over the argument(s) involving key $W$}
+  \item[$m_s$]{Private key from merchant for authentication}
+  \item[$M_p$]{Public key corresponding to $m_s$}
+  \item[$M$]{Public-private merchant authentication key pair $M := (m_s, M_p)$}
+  \item[$S_M()$]{Signature over the argument(s) involving key $M$}
+  \item[$G$]{Generator of the elliptic curve}
+  \item[$c_s$]{Secret key corresponding to a coin, scalar on a curve}
+  \item[$C_p$]{Public key corresponding to $c_s$, point on a curve}
+  \item[$C$]{Public-private coin key pair $C := (c_s, C_p)$}
+  \item[$S_{C}()$]{Signature over the argument(s) involving key $C$ (using EdDSA)}
+  \item[$c_s'$]{Private key of a ``dirty'' coin (otherwise like $c_s$)}
+  \item[$C_p'$]{Public key of a ``dirty'' coin (otherwise like $C_p$)}
+  \item[$C'$]{Dirty coin (otherwise like $C$)}
+  \item[$\widetilde{C}$]{Mint signature $S_K(C_p)$ indicating validity of a fresh coin (with key $C$)}
+  \item[$n$]{Number of mints accepted by a merchant}
+  \item[$j$]{Index into a set of accepted mints, $i \in \{1,\ldots,n\}$}
+  \item[$D_j$]{Public key of a mint (not used to sign coins)}
+  \item[$\vec{D}$]{Vector of $D_j$ signifying mints accepted by a merchant}
+  \item[$a$]{Complete text of a contract between customer and merchant}
+  \item[$f$]{Amount a customer agrees to pay to a merchant for a contract}
+  \item[$m$]{Unique transaction identifier chosen by the merchant}
+  \item[$H()$]{Hash function}
+  \item[$p$]{Payment details of a merchant (i.e. wire transfer details for a bank transfer)}
+  \item[$r$]{Random nonce}
+  \item[${\cal A}$]{Complete contract signed by the merchant}
+  \item[${\cal D}$]{Deposit permission, signing over a certain amount of coin to the merchant as payment and to signify acceptance of a particular contract}
+  \item[$\kappa$]{Security parameter $\ge 3$}
+  \item[$i$]{Index over cut-and-choose set, $i \in \{1,\ldots,\kappa\}$}
+  \item[$\gamma$]{Selected index in cut-and-choose protocol, $\gamma \in \{1,\ldots,\kappa\}$}
+  \item[$t^{(i)}_s$]{private transfer key, a scalar}
+  \item[$T^{(i)}_s$]{private transfer key, point on a curve (same curve must be used for $C_p$)}
+  \item[$T^{(i)}$]{public-private transfer key pair $T^{(i)} := (t^{(i)}_s,T^{(i)}_s)$}
+  \item[$\vec{T}$]{Vector of $T^{(i)}$}
+  \item[$c_s^{(i)}$]{Secret key corresponding to a fresh coin, scalar on a curve}
+  \item[$C_p^{(i)}$]{Public key corresponding to $c_s^{(i)}$, point on a curve}
+  \item[$C^{(i)}$]{Public-private coin key pair $C^{(i)} := (c_s^{(i)}, C_p^{(i)})$}
+  \item[$\vec{C}$]{Vector of $C^{(i)}$ (public and private keys)}
+  \item[$b^{(i)}$]{Blinding factor for RSA-style blind signatures}
+  \item[$\vec{b}$]{Vector of $b^{(i)}$}
+  \item[$B^(i)$]{Blinding of $C_p^{(i)}$}
+  \item[$\vec{B}$]{Vector of $B^{(i)}$}
+  \item[$K_i$]{Symmetric encryption key derived from ECDH operation via hashing}
+  \item[$E_{K_i}()$]{Symmetric encryption using key $K_i$}
+  \item[$E^{(i)}$]{$i$-th encryption of the private information $(c_s^{(i)}, b_i)$}
+  \item[$\vec{E}$]{Vector of $E^{(i)}$}
+  \item[$\cal{R}$]{Tuple of revealed vectors in cut-and-choose protocol,
+    where the vectors exclude the selected index $\gamma$}
+  \item[$\overline{K_i}$]{Encryption keys derived by the verifier from DH}
+  \item[$\overline{B^{(i)}}$]{Blinded values derived by the verifier}
+  \item[$\overline{T_p^{(i)}}$]{Public transfer keys derived by the verifier from revealed private keys}
+  \item[$\overline{c_s^{(i)}}$]{Private keys obtained from decryption by the verifier}
+  \item[$\overline{b_s^{(i)}}$]{Blinding factors obtained from decryption by the verifier}
+  \item[$\overline{C^{(i)}_p}$]{Public coin keys computed from $\overline{c_s^{(i)}}$ by the verifier}
+\end{description}
+
+
+
 \end{document}
-- 
cgit v1.2.3


From 1bfba318ec0f3393de2dfc66821dec6165eef90a Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Sat, 26 Sep 2015 16:57:16 +0200
Subject: add reminder

---
 doc/paper/taler.tex | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

(limited to 'doc/paper/taler.tex')

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 361efadde..59a093015 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -1,3 +1,25 @@
+% RMS wrote:
+%The text does not mention GNU anywhere.  This paper is an opportunity
+%to make people aware of GNU, but the current text fails to use the
+%opportunity.
+%
+%It should say that Taler is a GNU package.
+%
+%I suggest using the term "GNU Taler" in the title, once in the
+%abstract, and the first time the name is mentioned in the body text.
+%In the body text, it can have a footnote with more information
+%including a reference to http://gnu.org/gnu/the-gnu-project.html.
+%
+%At the top of page 3, where it says "a free software implementation",
+%it should add "(free as in freedom)", with a reference to
+%http://gnu.org/philosophy/free-sw.html and
+%http://gnu.org/philosophy/free-software-even-more-important.html.
+%
+%Would you please include these things in every article or posting?
+%
+% CG adds:
+% We SHOULD do this for the FINAL paper, not for the anon submission.
+
 \documentclass{llncs}
 %\usepackage[margin=1in,a4paper]{geometry}
 \usepackage[T1]{fontenc}
-- 
cgit v1.2.3

