[GNUnet-SVN] [taler-exchange] branch master updated: clarify withdraw existing response lookup

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository exchange.

The following commit(s) were added to refs/heads/master by this push:
     new e53a736  clarify withdraw existing response lookup
e53a736 is described below

commit e53a736dcaccea4de2f5adcd5c332f0016c7d3a5
Author: Florian Dold <address@hidden>
AuthorDate: Wed May 17 16:53:36 2017 +0200

    clarify withdraw existing response lookup
---
 doc/paper/taler.tex        | 9 ++++-----
 doc/paper/taler_FC2017.txt | 3 +++
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index ba1536f..80d8310 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -838,10 +838,9 @@ interaction with the exchange:
     the exchange to request withdrawal of $C$; here, $B_b$ denotes
     Chaum-style blinding with blinding factor $b$.
   \item
-    The exchange checks if the same withdrawal request was issued before;
-    in this case, it sends a Chaum-style blind signature $S_K(B)$ with
-    private key $K_s$ to the customer. \\
-    If this is a fresh withdrawal request, the exchange performs the following 
transaction:
+    The exchange checks its database if there is an existing withdraw record 
$\langle S_W(B), x \rangle$
+    with existing withdraw response $x$; in this case it sends back $x$.\\
+    Otherwise if this is a fresh withdrawal request, the exchange performs the 
following transaction:
     \begin{enumerate}
       \item checks if the reserve $W_p$ has sufficient funds
             for a coin of value corresponding to $K$,
@@ -850,7 +849,7 @@ interaction with the exchange:
             for future reference,
       \item deducts the amount corresponding to $K$ from the reserve,
     \end{enumerate}
-    and then sends $S_K(B)$ to the customer.
+    and then sends Chaum-style blind signature $S_K(B)$ to the customer.
     If the guards for the transaction fail, the exchange sends a descriptive
     error back to the customer, with proof that it operated correctly.
     Assuming the signature was valid, this would involve showing the 
transaction
diff --git a/doc/paper/taler_FC2017.txt b/doc/paper/taler_FC2017.txt
index daf1313..06fe468 100644
--- a/doc/paper/taler_FC2017.txt
+++ b/doc/paper/taler_FC2017.txt
@@ -150,6 +150,9 @@ Specific comments:
   point: 2nd line also reads as “if the same withdrawal request was issued 
before
   the exchange will send S_K(B)”
 
+> We added some clarification that the exchange looks up if the request
+> already exists in their database.
+
 - Section 4.2, it seems that a customer can use a coin of value say $10 to
   multiple transactions of <= $10 in total. I.e. it can first a pay a merchant
   M1 $2 and then a merchant M2 another $5 dollars. In that case the exchange 
can

-- 
To stop receiving notification emails like this one, please contact
address@hidden