exchange

Base system with REST service to issue digital coins, run by the payment service provider
Log | Files | Refs | Submodules | README | LICENSE

commit 152396f1aa57fecd2bc2fee4f0c3b8679e6e259b
parent 8dfb3b87b47ca2d25f6bdcbdfa2acc517fbe6ae2
Author: Jeff Burdges <burdges@gnunet.org>
Date:   Sat, 21 May 2016 21:44:05 +0200

Oops, I hadn't quite finished some edits there

Diffstat:
Mdoc/paper/taler.tex | 11+++++------
1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex @@ -319,12 +319,11 @@ Taler avoids include: detection of double-spending, requires the exchange to attempt to recover funds from delinquent customers via the legal system. Any system like this that fails to be self-enforcing creates a major - business risk for the exchange. In 1983, there were merchants without - network connectivity - need to have - been a necessary feature. - However, today requiring network connectivity is feasible and avoids the business - risks associated with deferred fraud detection. + business risk for the exchange and merchants. + In 1983, there were merchants without network connectivity, making that + feature relevant, but today network connectivity should be feasible for + merchants, and saves both the exchange and merchants the business risks + associated with deferred fraud detection. \item % In addition to the risk of legal disputes with fraudulent % merchants and customers, Chaum's published design does not clearly