gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: clarify Q/A


From: gnunet
Subject: [taler-docs] branch master updated: clarify Q/A
Date: Mon, 19 Apr 2021 14:56:54 +0200

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new f29c845  clarify Q/A
f29c845 is described below

commit f29c8456f2d75673523a72682af5c8b877167721
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Apr 19 14:56:47 2021 +0200

    clarify Q/A
---
 design-documents/013-peer-to-peer-payments.rst | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/design-documents/013-peer-to-peer-payments.rst 
b/design-documents/013-peer-to-peer-payments.rst
index 1724605..6c87df9 100644
--- a/design-documents/013-peer-to-peer-payments.rst
+++ b/design-documents/013-peer-to-peer-payments.rst
@@ -400,9 +400,11 @@ Q / A
 
 * Q: Why do merchant payments not use purses?
 
-  * A: Refunds aren't possible with purses, the customer can't prove that
-    they own the contract terms (contract terms claiming isn't interactive).
+  * Refunds aren't possible with purses after they're closed
+  * Partial refunds aren't possible
+  * the customer can't prove that they own the contract terms (contract terms 
claiming isn't interactive)
+  * the merchant can't cover deposit fees
+  * (All of these could be addressed, but the resulting protocol isn't 
necessarily simpler
+    than what we currently have.)
 
-    * All these issues could be addressed though.  But that
-      would be a major "Taler 2.0 / 3.0" protocol change
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]