gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [taler-exchange] branch master updated: fix typos


From: gnunet
Subject: [GNUnet-SVN] [taler-exchange] branch master updated: fix typos
Date: Fri, 19 May 2017 14:25:53 +0200

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 6c51e40  fix typos
6c51e40 is described below

commit 6c51e40bdf2cb8030e68f887177afe8c2373ff76
Author: Florian Dold <address@hidden>
AuthorDate: Fri May 19 14:25:45 2017 +0200

    fix typos
---
 doc/paper/taler.tex | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 8698719..6c80927 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -1354,17 +1354,17 @@ other users.
 
 We will now consider the impact of the refresh operation.
 For the sake of the argument, we will first consider an earlier
-encryption-based version of the protocol in which a refresh operated
+encryption-based version of the protocol in which a refresh operation
 consisted of $\kappa$ normal coin withdrawals and the commitment
 consisted of the blinding factors and private keys of the fresh coins
 encrypted using the secret $t^{(i)} C_s$ where $C_s = c_s G$ of the
 dirty coin $C$ being refreshed and $T^{(i)} = t^{(i)} G$ is the
 transfer key.
 %
-In Taler, we replaced this encryption-based schem with the current
-KDF-based scheme as it required slightly more storage space, the
-additional, encryption primitive, and exposed more random number
-generator output from the wallet.
+In Taler, we replaced this encryption-based scheme with the current KDF-based
+scheme, as the earlier scheme required slightly more storage space, an
+additional encryption primitive, and exposed more random number generator
+output from the wallet.
 
 \begin{proposition}
 Assuming the encryption used is semantically (IND-CPA) secure, and

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]