exchange

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

commit cf15aaae1817c0e2f2c8230e120489b790f138c2
parent 247e795904fc4bd75e174faf4abe6227ba3017ef
Author: Jeff Burdges <burdges@gnunet.org>
Date:   Mon,  7 Nov 2016 17:57:52 +0100

FIXMEs on 3.2 being long winded

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

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex @@ -399,11 +399,15 @@ who is performing the authentication to authorize the withdrawal. Preventing the owner of the reserve from deliberately authorizing someone else to withdraw electronic coins would require extreme measures, including preventing them from communicating with anyone but -the exchange terminal during withdrawal. As such measures would be +the exchange terminal during withdrawal. +% FIXME: Oddly phrased: + As such measures would be totally impractical for a minor loophole, we are not concerned with enabling the state to strongly identify the recipient of coins from a withdrawal operation. +% FIXME: Seems to kinda duplicate the previous paragraph, albeit doing +% a better job. We view ownership of a coin's private key as a ``capability'' to spend the funds. A taxable transaction occurs when a merchant entity gains control over the funds while at the same time a customer entity looses