summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeffrey Burdges <burdges@gnunet.org>2017-08-21 17:54:01 +0200
committerJeffrey Burdges <burdges@gnunet.org>2017-08-21 17:54:01 +0200
commitf39d250242a649ff1f53a58a978f6b90a950619a (patch)
tree1a9dba401f355ff01b64c0f897e8e68d92335310
parent757227f8877f1356c2fdfd9b6208c8b78f966a50 (diff)
downloadpapers-f39d250242a649ff1f53a58a978f6b90a950619a.tar.gz
papers-f39d250242a649ff1f53a58a978f6b90a950619a.tar.bz2
papers-f39d250242a649ff1f53a58a978f6b90a950619a.zip
Change
-rw-r--r--comparison/comparison.tex5
1 files changed, 3 insertions, 2 deletions
diff --git a/comparison/comparison.tex b/comparison/comparison.tex
index ae2920d..df6c4b5 100644
--- a/comparison/comparison.tex
+++ b/comparison/comparison.tex
@@ -176,8 +176,9 @@ Taler
storage requirements, and the divisible schemes depend upon trusted setup
for their anonymity properties.
\item \textbf{Change/Divisibility.}
- Is there partial spending? If so, is it handled by giving change
- online (ON) or by divisible coins that support offline operation (OFF)?
+ Can customers pay without possessing exact change? If so, is it handled
+ by giving change online (ON) or by divisible coins that support offline
+ operation (OFF)?
\item \textbf{Receipts \& Refunds.}
The customer either can prove that they payed for
a contract, or they can get their (unlinkable) money back,