diff options
| author | Christian Grothoff <christian@grothoff.org> | 2022-09-18 00:03:13 +0200 |
|---|---|---|
| committer | Christian Grothoff <christian@grothoff.org> | 2022-09-18 00:03:13 +0200 |
| commit | 3f7927f435da3ff89b126f6837b5fb0016025a23 (patch) | |
| tree | 0a50da9b67f00934e800cfa05d08380a7c129436 /design-documents | |
| parent | be69b01fcc7b5cfc3e2575b50211b2d74e47f83d (diff) | |
| download | docs-3f7927f435da3ff89b126f6837b5fb0016025a23.tar.gz docs-3f7927f435da3ff89b126f6837b5fb0016025a23.tar.bz2 docs-3f7927f435da3ff89b126f6837b5fb0016025a23.zip | |
work on reserve control API design
Diffstat (limited to 'design-documents')
| -rw-r--r-- | design-documents/031-invoicing.rst | 25 |
1 files changed, 24 insertions, 1 deletions
diff --git a/design-documents/031-invoicing.rst b/design-documents/031-invoicing.rst index 4e2ebc5f..24c64d79 100644 --- a/design-documents/031-invoicing.rst +++ b/design-documents/031-invoicing.rst @@ -36,6 +36,25 @@ Requirements * Reasonable UX and overall design impact. +Unclear in the current proposal are: + + * How to pay for the opening. Do we support the use of + coins, or should we require the user to have a + sufficient balance in the reserve, or do we allow + both? Probably best to only support one. As + reserves are typically instant-drained by the + wallet, might be best to require coins? + + * Here (and in other places!), the payment of the KYC + fee remains, eh, obscure. This should probably be + part of the KYC endpoints, and not for each + KYC-trigger. + + * Proposed table structure does not properly capture + if user paid extra for more purses (I could open + for 3 years, then pay for 5x purses in year 1, but + should not automatically get 5x purses in years 2/3). + Proposed Solution ================= @@ -55,18 +74,22 @@ reserve after tips are no longer issued. The solution needs three new tables for: * account creation data: + - serial - timestamp - signature affirming desire to create account - KYC requirement row * account creation payment data: + - serial (for replication) - coin signature (affirming payment) - amount contributed - account creation link (serial row ID) * reserve closure request data: + + - serial (for replication) - timestamp - reserve signature - target account payto:// URI @@ -100,7 +123,7 @@ Reserve Attestation * This new endpoint ``/reserve/$RID/attest`` allows the user to obtain exchange-signed KYC information about themselves. - This will basically be a list of (standardized) attributes + This will basically be a list of (GANA standardized) attributes and exchange signatures. The user can then choose which of these attributes to include when invoicing. The available set of attributes may differ depending on the KYC providers |