diff options
author | Christian Grothoff <christian@grothoff.org> | 2020-07-22 23:56:52 +0200 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2020-07-22 23:56:52 +0200 |
commit | 0e808b648a56e3e4e17d6e03ce776b0b7a422f25 (patch) | |
tree | 59720c0b409f30fc6520526ba7170b0ba60c255c /doc/paper/taler_FC2017.txt | |
parent | c8a370d9111cee69b6d9b6edc177dcc58eec976a (diff) | |
download | exchange-0e808b648a56e3e4e17d6e03ce776b0b7a422f25.tar.xz |
fix misc typos
Diffstat (limited to 'doc/paper/taler_FC2017.txt')
-rw-r--r-- | doc/paper/taler_FC2017.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/paper/taler_FC2017.txt b/doc/paper/taler_FC2017.txt index 66f8560ad..f66530c68 100644 --- a/doc/paper/taler_FC2017.txt +++ b/doc/paper/taler_FC2017.txt @@ -220,11 +220,11 @@ wanting this features is that it enables refunds from a merchant that later can be refreshed into "clean" coins that are unlinkable to the refunded coins. The protocol is based on what appears to be a standard cut-and-choose approach, which does not appear to be particularly -novel. On the postive side, the problem appears a natural and if it +novel. On the positive side, the problem appears a natural and if it hasn't been done before certainly useful. On the negative side, since the paper does not contain any formal definitions, or even semi-formal specifications of the desiderata, it is very hard to understand what -actually is acheived. Furthermore, no proofs of security are given, +actually is achieved. Furthermore, no proofs of security are given, and even the protocol is hard to fully understand. As such, I would suggest the authors to first formalize their approach and resubmitting. |