taler-docs

commit 12544b755247c068b8d0c66ce2b530f77f32916a
parent e0e69811d2f49683dc18e1231715e3ee23fc8f2a
Author: Özgür Kesim <oec-taler@kesim.org>
Date:   Mon, 31 Jul 2023 08:28:23 +0200

DD45: explain changes to DB

Diffstat:
M
design-documents/045-kyc-inheritance.rst
 | 
19
++++++++++++++-----

1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/design-documents/045-kyc-inheritance.rst b/design-documents/045-kyc-inheritance.rst
@@ -57,6 +57,15 @@ number of attestations that a (KYC'ed) reserve can provide for other reserves.
    MAXIMUM_ATTESTATIONS = [number]
 
 
+The database schema needs to be ajdusted to incorporate
+
+* a boolean field ``inherited`` in the table ``kyc_attributes`` to indicate the
+  inheritance status
+
+* a integer field ``attestations`` in the table ``reserves`` to count the
+  number of attestations performed by a reserve.
+
+
 On the exchange we propose the following new endpoint:
 
 
@@ -165,12 +174,12 @@ Discussion / Q&A
 
 The proposed solution makes the principle of subsidiarty for age-restrictions
 (i.e parents are responsible for setting the age-restriction) explicit in the
-code. However, the proposed solution does not exclude the possibility for other
-ways to set age-restriction in the wallet.  For example, parents who do _not_
-have a Taler wallet, must still be able to assist their children with the 
-settings of age-restriction during the withdraw process.
-
+code.
 
 It also simplifies the KYC process for many situations for customers: Families
 members and partners benefit from it.
 
+However, the proposed solution still allows for other ways to set
+age-restriction in the wallet.  For example, parents who do **not** have a
+Taler wallet, are still able to assist their children with the settings of
+age-restriction during the withdraw process.