taler-docs

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

commit 8f8839e0cdcb2e281d9f8a2de5155fc9ddca6414
parent 4c425700990de8b1321b1bff78537ff3e902c54f
Author: Florian Dold <florian@dold.me>
Date:   Thu,  5 Jun 2025 11:50:14 +0200

-formatting

Diffstat:
Mdesign-documents/064-kyc-operation-algo.rst | 14+++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/design-documents/064-kyc-operation-algo.rst b/design-documents/064-kyc-operation-algo.rst @@ -66,16 +66,16 @@ Steps for processing operation of type ``op`` and amount ``amt``: Notes: - * Note 1: In practice, this might not be necessary, but - there could be a non-exposed rule that the client needs - to trigger to proceed. - * Note 2: We must long-poll for the next rule generation here, - since we can assume that the current set of rules contains non-exposed - rule that prevents the current operation. +* Note 1: In practice, this might not be necessary, but + there could be a non-exposed rule that the client needs + to trigger to proceed. +* Note 2: We must long-poll for the next rule generation here, + since we can assume that the current set of rules contains non-exposed + rule that prevents the current operation. Open questions: - * What should the `lpt` parameter be in step 4? +* What should the `lpt` parameter be in step 4? Definition of Done ==================