[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: first comments
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: first comments |
Date: |
Fri, 17 Feb 2023 15:17:10 +0100 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new e26178d first comments
e26178d is described below
commit e26178d09d1cea5a56530b3d2033aaeeadc593c3
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Feb 17 15:17:07 2023 +0100
first comments
---
design-documents/037-wallet-transactions-lifecycle.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/design-documents/037-wallet-transactions-lifecycle.rst
b/design-documents/037-wallet-transactions-lifecycle.rst
index d383f56..5280342 100644
--- a/design-documents/037-wallet-transactions-lifecycle.rst
+++ b/design-documents/037-wallet-transactions-lifecycle.rst
@@ -474,6 +474,8 @@ TODO: Also specify variant where account reserve needs to
be created / funded fi
* ``[action:abort] => aborted``: At this stage, it's safe to just abort.
+ CG: is this not 'suspend' (safe to resume!). Also, deletion transitions
are missing.
+
* ``pending(wait-deposit)``
We're waiting for the other party to pay into the pre-merged purse.
@@ -518,7 +520,7 @@ Transaction Type: Peer Pull Debit
* ``[processed-success] => done``
* ``[action:abort] => aborting(refresh)``: Wallet tries to refresh coins
that were not already deposited. XXX Do we really always refresh even if
no deposit
- attempt has been made yet?
+ attempt has been made yet? CG: only every refresh those coins that are
dirty.
* ``aborting(refresh)``
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.