[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] 02/02: -dce
From: |
Admin |
Subject: |
[taler-docs] 02/02: -dce |
Date: |
Thu, 05 Jun 2025 11:45:28 +0200 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository taler-docs.
commit cf5724cad59da5b30c4003db125a77fb5f7cd8cb
Author: Florian Dold <florian@dold.me>
AuthorDate: Thu Jun 5 11:45:23 2025 +0200
-dce
---
design-documents/064-kyc-operation-algo.rst | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/design-documents/064-kyc-operation-algo.rst
b/design-documents/064-kyc-operation-algo.rst
index 94f5bde3..7f66b299 100644
--- a/design-documents/064-kyc-operation-algo.rst
+++ b/design-documents/064-kyc-operation-algo.rst
@@ -26,7 +26,7 @@ Proposed Solution
Steps for processing operation of type ``op`` and amount ``amt``:
-0. Initialize ``last_check_success := null``, ``last_op_attempt := null``,
``last_rule_gen := null``
+0. Initialize ``last_op_attempt := null``, ``last_rule_gen := null``
1. Check if a zero limit for ``op`` is applicable.
@@ -47,7 +47,7 @@ Steps for processing operation of type ``op`` and amount
``amt``:
* If the request returns ``200 Ok`` or a ``202 Accepted``:
* Set ``last_rule_gen := response.rule_gen``
- * If the exposed limits do not deny ``op``, set ``last_check_success :=
now()`` and proceed with step 2.
+ * If the exposed limits do not deny ``op``, proceed with step 2.
* Proceed with the next step 4.
@@ -57,8 +57,7 @@ Steps for processing operation of type ``op`` and amount
``amt``:
* If the request returns ``200 Ok`` or a ``202 Accepted``:
* Set ``last_rule_gen := response.rule_gen``
- * If the exposed limits
- do not deny ``op``, set ``last_check_success := now()`` and proceed
with step 2.
+ * If the exposed limits do not deny ``op``, proceed with step 2.
* If if the ``last_op_attempt`` is ``null`` or is more than 10 minutes in
the past,
proceed with step 2. (See Note 1)
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.