taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit e26178d09d1cea5a56530b3d2033aaeeadc593c3
parent 0658090683706b2f80fdf1f808e4514c52850278
Author: Christian Grothoff <christian@grothoff.org>
Date:   Fri, 17 Feb 2023 15:17:07 +0100

first comments

Diffstat:
Mdesign-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 @@ -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)``