path: root/doc/paper/taler.tex
diff options
authorChristian Grothoff <>2017-05-19 23:26:29 +0200
committerChristian Grothoff <>2017-05-19 23:26:29 +0200
commit37a5a41480bd69c665fd6fc6861d21476f01012e (patch)
tree1f0715338ac60b6945d73b14dbbe89a9e83e99d7 /doc/paper/taler.tex
parenta40d605d7cf2f9a654ced8b6a8d818b46fae9d6a (diff)
address fixmes, add bridge sentence back
Diffstat (limited to 'doc/paper/taler.tex')
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 68b26913..76bceca2 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -799,7 +799,7 @@ the refresh protocol from being used to transfer ownership.
-% In this section, we describe the protocols for Taler in detail.
+In this section, we describe the protocols for Taler in detail.
For the sake of brevity we omit explicitly saying each time that a
recipient of a signed message always first checks that the signature
@@ -903,12 +903,11 @@ following interaction with the exchange:
\subsection{Exact and partial spending}
A customer can spend coins at a merchant, under the condition that the
-merchant trusts the exchange that issued the coin.
-% FIXME: Auditor here?
+merchant trusts the exchange that issued the coin, usually because
+the exchange is audited by an auditor that is trusted by the merchant.
Merchants are identified by their public key $M_p$ which the
customer's wallet learns through the merchant's Web page, which itself
should be authenticated with X.509c.
-% FIXME: Is this correct?
We now describe the protocol between the customer, merchant, and exchange
for a transaction in which the customer spends a coin $C := (c_s, C_p)$