exchange

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

commit 3f0a0c8f714ad9e8abd49c9fb0e56a97022a758d
parent bf8b9d1435a196c9b7c3293904da2a3baba7210a
Author: Christian Grothoff <christian@grothoff.org>
Date:   Mon, 28 Sep 2015 08:53:01 +0200

attempt to clarify double spending

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

diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex @@ -745,7 +745,8 @@ $\widetilde{C} := S_K(C_p)$: only to the mint. \item The mint validates $\mathcal{D}$ and checks for double spending. - If the coin has been involved in previous transactions, it sends an error + If the coin has been involved in previous transactions and the new + one would exceed its remaining value, it sends an error with the records from the previous transactions back to the merchant. % If double spending is not found, the mint commits $\langle \mathcal{D} \rangle$ to disk @@ -1113,7 +1114,8 @@ an exclusive right to redeem deposit permissions for the coin for a limited duration. The merchant uses the lock permission to determine if the coin has already been spent and to ensure that it cannot be spent by another merchant for the {\em duration} of the lock as -specified in the lock permission. If the coin has been spent or is +specified in the lock permission. If the coin has insufficient funds +because too much has been spent or is already locked, the mint provides the owner's deposit or locking request and signature to prove the attempted fraud by the customer. Otherwise, the mint locks the coin for the expected duration of the